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
SaplingSyncLoopHandle keeps sending sync status after main sync process is finished which results to error like
7 10:57:53, common::log:305] DEBUG z_rpc:679] No one seems interested in SyncStatus: send failed because channel is full
We need to figure out a method to stop sending updates after the main/first synchronization process. One way to achieve this is by introducing a new field called main_sync_state_finished to the SaplingSyncLoopHandle. This field would act as a marker to signal when the main synchronization is completed. Before sending any new updates, we can check the value of main_sync_state_finished to ensure that the main synchronization has indeed finished.
The text was updated successfully, but these errors were encountered:
borngraced
changed the title
stop sending sync status after first/main sync finished status
stop sending sync status after first/main sync status is finished
Dec 7, 2023
komodo-defi-framework/mm2src/coins/z_coin/z_rpc.rs
Lines 743 to 753 in 84be059
SaplingSyncLoopHandle
keeps sending sync status after main sync process is finished which results to error likeWe need to figure out a method to stop sending updates after the main/first synchronization process. One way to achieve this is by introducing a new field called
main_sync_state_finished
to theSaplingSyncLoopHandle
. This field would act as a marker to signal when the main synchronization is completed. Before sending any new updates, we can check the value ofmain_sync_state_finished
to ensure that the main synchronization has indeed finished.same issue goes for
komodo-defi-framework/mm2src/coins/utxo.rs
Lines 457 to 490 in 84be059
cc @shamardy
The text was updated successfully, but these errors were encountered: