Fork detection script #1968
Draft
Fork detection script #1968
+1,069
−4
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ImplOfAnImpl
force-pushed
the
fork_detection_script
branch
from
f420821 to
48ca968
Compare
ImplOfAnImpl
changed the base branch from
difficulty_plot_helpers
to
fork_detection_script_deps
ImplOfAnImpl
force-pushed
the
fork_detection_script
branch
from
48ca968 to
305fbe6
Compare
Rename network type to chain type in detector.py
…eate a flag for each received stale block; handle the situation when the node can't receive new blocks.
ImplOfAnImpl
force-pushed
the
fork_detection_script
branch
from
305fbe6 to
998cf39
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The PR is a draft because I'm still polishing the script, but it's already usable.
Improvement suggestions are welcome.
Also:1) The node now has the option to disable checkpoints.2)last_tip_block_timeis now included in the peer info returned by the corresponding node RPC call.3) In p2p, peer id is now logged automatically via atracingspan, so its explicit logging is no longer needed and was removed.Also, tracing spans are now propagated when subsystem calls are made. This way when p2p calls the chainstate and something happens, we'll know the peer id that caused it.These changes have been moved to #1972