Fix/5193 stackerdb decoherence #5197
Merged
Commits on Sep 16, 2024
-
-
-
fix: report pinned connections so the pruner won't disconnect nakamot…
…o inv sync peers
-
-
fix: don't prune connections the inv state machines and stackerdb sta…
…te machine are using
-
chore: keep stackerdb replicas pinned across restarts, and only unpin…
… on irrecoverable error
-
chore: enhance stackerdb test to force the network pruner to run, so …
…as to verify that connection pinning prevents decoherence
-
-
Commits on Sep 17, 2024
Commits on Sep 19, 2024
-
Do not count received valid signatures towards threshold weight when …
…ignore flag set Signed-off-by: Jacinta Ferrant <[email protected]>
-
Do not assume every signers signature makes it before miner quits wai…
…ting for unnecessary signatures Signed-off-by: Jacinta Ferrant <[email protected]>
-
test: move the 2.5 and 3.0 activation heights earlier for this test
This allows us to avoid hitting block 240, which is when the stackers get unstacked and the chain stalls, making `partial_tenure_fork` less flaky
Commits on Sep 20, 2024
Commits on Sep 23, 2024
-
-
Co-authored-by: Brice Dobry <[email protected]>
-
-
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.