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
Either move the GSM logic into the ChainDB and keep the GSM arguments as part of the ChainDB arguments (which would be encapsulated inside of openChainDB) or remove the argument from the ChainDB arguments and keep it as a NodeKernel-level thing.
move the anti-thundering herd delay into the Diffusion Layer, between the two states CaughtUp and OnlyBootstrap
regression tests (code review and ad-hoc manual testing has already evidenced that they're currently correct):
realMarkerFileView regression tests
initializationLedgerJudgement regression tests
realDurationUntilTooOld regression tests
The ChainSync client should signal idle exactly when and only when the MsgAwaitReply is processed.
The ChainSync client subsequently should signal no-longer-idle exactly when and only when the next message is received.
Either move the GSM logic into the ChainDB and keep the GSM arguments as part of the ChainDB arguments (which would be encapsulated inside of openChainDB) or remove the argument from the ChainDB arguments and keep it as a NodeKernel-level thing.
Taken from #808 (comment), upon clicking the "Merge when ready" button.
realMarkerFileView
regression testsinitializationLedgerJudgement
regression testsrealDurationUntilTooOld
regression testsMsgAwaitReply
is processed.quickcheck-dynamic
and/or upstream theio-sim
-based QSM module #1149ArbitraryLedgerStateJudgement
fromouroboros-network:sim-tests-lib
The text was updated successfully, but these errors were encountered: