fix(watchdog): refuse unreachable Drive roots - #132
Merged
Conversation
Assisted-by: GPT-5-Codex Co-authored-by: GPT-5-Codex <noreply@openai.com>
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.
The watchdog treated a surviving Drive container as sufficient even when the destination's actual Drive root had moved. It then retried the resulting permanent permission failure and reduced the useful diagnosis to a crash/timeout.
This makes destination-root readiness part of the pre-check and classifies destination permission failures as terminal, destination-specific refusals.
Closes #131
#131 — The mount check passes on a Drive root whose My Drive has moved, and the run crashes three times: 4 of 4 criteria delivered, nothing beyond the brief.
Tests:
npm test(390 passed);npm run lint;npm run format:check.Assisted-by: GPT-5-Codex
Co-authored-by: GPT-5-Codex noreply@openai.com