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
In state sync a state part is generally identified by:
A shard id
A sync hash
A part id
In various places we use types such as tuple (ShardId, CryptoHash, u64) without named members, and the order in which the fields are presented is inconsistent between places. We should improve the consistency and consider a proper struct with named members for better maintainability.
The text was updated successfully, but these errors were encountered:
In state sync a state part is generally identified by:
In various places we use types such as tuple
(ShardId, CryptoHash, u64)
without named members, and the order in which the fields are presented is inconsistent between places. We should improve the consistency and consider a proper struct with named members for better maintainability.The text was updated successfully, but these errors were encountered: