fix: grpc client call panic

[quanbisen]

I used Cursor to fix a bug in the gRPC client call that occasionally triggered panics. After the fix, it has been running stably for 3 days without any issues. Before the fix, the program would panic within a day. While this fix resolved the gRPC panic issue, I'm unsure if the changes might affect other functionalities – though my current tests show no problems.

[linux-foundation-easycla]

• ❌ - login: @quanbisen / name: superlollipop . The commit (d5a7a17) is not authorized under a signed CLA. Please click here to be authorized. For further assistance with EasyCLA, please submit a support request ticket.

[RonFed]

I'm not sure I understand the rationale for this fix. It seems like this changes some local variables to be stored on storage maps but these maps are accessed within the same function - so I'm not sure how that helps.

[quanbisen]

I'm not sure I understand the rationale for this fix. It seems like this changes some local variables to be stored on storage maps but these maps are accessed within the same function - so I'm not sure how that helps.

but it work for me now, I'm sure it fix grpc call panic.