fix: stop spurious 'drivemount failed' on OAuth waits over 10s#11
Merged
Conversation
The drivefs handshake blocks the kernel on input_request while the user OAuths in their browser. jupyter_kernel_client's default 10s wall-clock timeout fires during this silent stretch, raising TimeoutError mid-flow even though the mount has actually succeeded server-side. Add an optional timeout= parameter to ColabRuntime.execute_code that is forwarded to both execute() and execute_interactive(). Pass timeout=600 (10 min) from the human-in-the-loop subcommands -- colab drivemount and colab auth -- via a shared INTERACTIVE_AUTOMATION_TIMEOUT_SEC constant. Non-interactive paths keep the upstream default since their continuous iopub traffic never trips the practical inactivity ceiling.
sethtroisi
approved these changes
May 13, 2026
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
2 participants
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 drivefs handshake blocks the kernel on input_request while the user OAuths in their browser. jupyter_kernel_client's default 10s wall-clock timeout fires during this silent stretch, raising TimeoutError mid-flow even though the mount has actually succeeded server-side.
Add an optional timeout= parameter to ColabRuntime.execute_code that is forwarded to both execute() and execute_interactive(). Pass timeout=600 (10 min) from the human-in-the-loop subcommands -- colab drivemount and colab auth -- via a shared INTERACTIVE_AUTOMATION_TIMEOUT_SEC constant. Non-interactive paths keep the upstream default since their continuous iopub traffic never trips the practical inactivity ceiling.