Catch Caprine resume recovery operation failures - #31477
Merged
woahwhattheheck merged 3 commits intoOct 5, 2026
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 Caprine PR2384 source packet handled rejected connectivity checks but could still reject its unawaited callback if an Electron operation such as reload failed. Add an outer catch that cancels that recovery attempt, keeping manual reload available and preventing a reload retry loop.
The same three packet paths stay aligned: complete candidate, minimal upstream-head patch and guide. The existing main-frame-load noninterference policy is intentional; this does not assert eventual reload or Messenger draft preservation. Full preimages, sole-parent commit chain and all three complete pinned texts were checked. No build, lint, tests, Electron execution or external publication was performed.