fix: handle keyring fallback as success #7177
Merged
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.
Summary
Relates to #6607
set_secret/delete_secret returned error when keyring unavailable despite file write succeeding. Treat FallbackToFileStorage as success since operation completed.
GitHub Copilot OAuth failed in WSL/environments without keyring:
set_secretanddelete_secretnow treatFallbackToFileStorageas success (file already written).Type of Change
AI Assistance
Test
I don't have GitHub Copilot access to verify the fix.
github_copilot should complete without "Failed to save token" error
change is straightforward: file write succeeds → return success.