-
Notifications
You must be signed in to change notification settings - Fork 864
fix: provide actionable error message for Drive mount credential failures #5805
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
abdulwahabahmedkhanyusufzai
wants to merge
3
commits into
googlecolab:main
Choose a base branch
from
abdulwahabahmedkhanyusufzai:fix/drive-mount-error
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from 1 commit
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
e2334f9
fix: improve error messaging for Drive mount credential failures (#5798)
abdulwahabahmedkhanyusufzai 0a3e40f
fix: generalize Drive mount error message and fix dead link
abdulwahabahmedkhanyusufzai 98a3794
fix: improve error message for credential propagation issues during D…
abdulwahabahmedkhanyusufzai File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This link is dead for me.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for the feedback and technical context, @fischman! I've updated the PR to:
Generalize the error message: Added 'Advanced Protection' as a potential cause for the propagation failure.
Update documentation link: Replaced the dead link with the active Colab FAQ section.
Since Ami is no longer with the team, tagging @blois and @colaboratory-team to take a look and potentially trigger the Security Scan. This fix helps clarify a common friction point for Brave and Safari users reported in #5798
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did you forget to push an updated commit to the PR?
At any rate, although my opinion carries no weight anymore, IMO this PR is misguided.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @fischman, thank you for the feedback. The updated commit is now visible—apologies for the delay in the push.
I understand that providing browser-specific troubleshooting might seem like a 'band-aid' rather than a deep architectural fix. My intent was to provide immediate, actionable guidance for users (specifically on Brave/Safari) who are currently facing silent failures, as seen in #5798.
If the team feels this text is too specific for the core library, I am happy to generalize it further. Otherwise, I hope this serves as a helpful stop-gap to reduce user friction while the underlying credential propagation logic is reviewed