You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Commit 38da1ed#diff-a9e69238f436ea544a4f20f1652a3257084e784a8733386c49c1a6a777dfa5b5L171 renamed cleanup_without_recv_blocks to cleanup_without_recv_full_blocks in cluster-endpoints/src/grpc_multiplex.rs (fn create_grpc_multiplex_blocks_subscription()), but it also removed cleanup_without_recv_blocks = 0; from the processed_block_reciever, so now every minute the multiplexer is being restarted. I don't think this is intended behavior.
Proposed solution
Add cleanup_without_recv_full_blocks = 0; to the beginning of processed_block_reciever
The text was updated successfully, but these errors were encountered:
I'm still the same and I don't know how to solve it, I have everything updated absolutely everything.
2024-03-23T00:31:50.291861Z ERROR lite_rpc::rpc_tester: RPC seems down
2024-03-23T00:32:00.274130Z ERROR solana_lite_rpc_cluster_endpoints::grpc_multiplex: block or block info geyser stream stopped - restarting multiplexer (13-13-13)
2024-03-23T00:32:45.309465Z ERROR lite_rpc::rpc_tester: RPC seems down
2024-03-23T00:33:06.777954Z ERROR solana_lite_rpc_cluster_endpoints::grpc_multiplex: block or block info geyser stream stopped - restarting multiplexer (13-13-13)
Issue
Commit 38da1ed#diff-a9e69238f436ea544a4f20f1652a3257084e784a8733386c49c1a6a777dfa5b5L171 renamed
cleanup_without_recv_blocks
tocleanup_without_recv_full_blocks
incluster-endpoints/src/grpc_multiplex.rs
(fn create_grpc_multiplex_blocks_subscription()
), but it also removedcleanup_without_recv_blocks = 0;
from theprocessed_block_reciever
, so now every minute the multiplexer is being restarted. I don't think this is intended behavior.Proposed solution
Add
cleanup_without_recv_full_blocks = 0;
to the beginning ofprocessed_block_reciever
The text was updated successfully, but these errors were encountered: