Repository navigation
Conversation
octobocto
force-pushed
the
2026-09-05-mainchain-task-recovery
branch
2 times, most recently
from
September 5, 2026 06:26
452779f to
3484928
Compare
octobocto
force-pushed
the
2026-09-05-mainchain-task-recovery
branch
from
September 27, 2026 14:26
3484928 to
c8b7fc2
Compare
octobocto
changed the title
octobocto
force-pushed
the
2026-09-05-mainchain-task-recovery
branch
2 times, most recently
from
September 27, 2026 15:43
2c51203 to
6cc7813
Compare
octobocto
changed the title
octobocto
force-pushed
the
2026-09-05-mainchain-task-recovery
branch
from
September 27, 2026 16:22
6cc7813 to
ebad83e
Compare
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
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.
Four faults each left the node without a mainchain connection, and it accepted no peer until a restart. The disconnect handler read the removed block as its own parent, so a mainchain reorg killed the task with
InvalidMainchainParent;MainchainTask::runended for good when the gRPC event stream closed, and the net task died with the request channel;mainchain_ancestors_revread a height frommain_block_hash_to_height, which an archive from before 7abd8ae holds one too big; and a peer connection ended while the mainchain tip was unset, becauseis_main_descendantasked for the height of the all-zeros hash.App::newstill returnsVerifyMainchainServicesat start, becausemain.rsopens the GUI on that error on purpose.