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
On one node (beta.3) I noticed that successful paranet sync process could be logged twice in the log, like this. You can see with a difference of 2 seconds it reported that the same paranet successfully finished sync process.
[2024-11-07 00:05:16] INFO: {Operation ID: 35c8f844-595e-4072-927f-519922e802fd} [paranetSyncCommand] (Command ID: f07cdd6c-9352-46b1-b2eb-2d526a11bd5f) Paranet sync: Successful new assets syncs: 9142; Failed new assets syncs: 0 for paranet: did:dkg:base:84532/0xb8B904c73D2fB4D8c173298A51c27Fab70222c32/7406675 (0x2d70485133a4a24d3178dc01b2ec24b4ce7a62d96393fb6de57c50bc396becd2), operation ID: 053e2167-32fa-4f8e-bc37-11018f5b6a98!
[2024-11-07 00:05:18] INFO: {Operation ID: 35c8f844-595e-4072-927f-519922e802fd} [paranetSyncCommand] (Command ID: f07cdd6c-9352-46b1-b2eb-2d526a11bd5f) Paranet sync: Successful new assets syncs: 9142; Failed new assets syncs: 0 for paranet: did:dkg:base:84532/0xb8B904c73D2fB4D8c173298A51c27Fab70222c32/7406675 (0x2d70485133a4a24d3178dc01b2ec24b4ce7a62d96393fb6de57c50bc396becd2), operation ID: 231a34eb-86b0-49f5-bc80-0b0a20825215!
And in the event table in MySQL it's the same thing. For some reason one paranet was reported as being synced twice at the same time.
It's not a unique example, I checked other nodes and found similar cases.
The text was updated successfully, but these errors were encountered:
On one node (beta.3) I noticed that successful paranet sync process could be logged twice in the log, like this. You can see with a difference of 2 seconds it reported that the same paranet successfully finished sync process.
[2024-11-07 00:05:16] INFO: {Operation ID: 35c8f844-595e-4072-927f-519922e802fd} [paranetSyncCommand] (Command ID: f07cdd6c-9352-46b1-b2eb-2d526a11bd5f) Paranet sync: Successful new assets syncs: 9142; Failed new assets syncs: 0 for paranet: did:dkg:base:84532/0xb8B904c73D2fB4D8c173298A51c27Fab70222c32/7406675 (0x2d70485133a4a24d3178dc01b2ec24b4ce7a62d96393fb6de57c50bc396becd2), operation ID: 053e2167-32fa-4f8e-bc37-11018f5b6a98!
[2024-11-07 00:05:18] INFO: {Operation ID: 35c8f844-595e-4072-927f-519922e802fd} [paranetSyncCommand] (Command ID: f07cdd6c-9352-46b1-b2eb-2d526a11bd5f) Paranet sync: Successful new assets syncs: 9142; Failed new assets syncs: 0 for paranet: did:dkg:base:84532/0xb8B904c73D2fB4D8c173298A51c27Fab70222c32/7406675 (0x2d70485133a4a24d3178dc01b2ec24b4ce7a62d96393fb6de57c50bc396becd2), operation ID: 231a34eb-86b0-49f5-bc80-0b0a20825215!
And in the
event
table in MySQL it's the same thing. For some reason one paranet was reported as being synced twice at the same time.It's not a unique example, I checked other nodes and found similar cases.
The text was updated successfully, but these errors were encountered: