colab_drive_auth fails after 5s (cli_timeout) on a fresh VM; automation still busy #10
Labels
No labels
area/backup
area/cli
area/docs
area/dsh
area/forgejo
area/host
area/mcp
area/plugin
area/security
area/ux
needs-operator
priority/later
priority/next
priority/now
type/bug
type/research
type/task
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
dsh-plugins/dsh-colab#10
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Tool:
colab_drive_auth(session="hijack", project="hijack", timeout_s=300)on a brand-new T4 session(cliVersion
0.7.5, plugin configproject=colab,driveRoot=/content/drive/MyDrive).Observed
Immediate failure after ~5 s:
colab_session_statusright after:status: BUSY (automation(drivemount)),last_execution: automation:drivemount. So the Colab-side automation was still running while the tool had already given up and killed its child.Expected
timeout_s=300should be the consent wait budget; the tool should wait for the automation / operator, not fail after 5 s.data.url(or streamed) so the operator can open it from another machine.auth_pending+ URL, without killing the automation (or kill it cleanly), rather thancli_timeoutafter 5 s.Likely cause
A hardcoded 5 s child/exec timeout (or
cli execwrapper default) instead of the tool'stimeout_s; the drivemount automation needs tens of seconds just to start.Suggestions
timeout_s(bounded 1–3600) for the whole handoff, and a separate startup grace of >=60 s for spawningcolab drivemount.drive_auth_neededevents (they carry the fulluri) —colab log -s <session>has it; surface that URL even while waiting.colab ls /content/drive/MyDrive/<project>as the success signal (as designed) instead of waiting for the child to exit.Impact
Blocks the only interactive step; workaround is the manual
colab drivemount -s <session>+ Enter (as before the plugin).Fixed in 0.1.3 (
9ce6715, tagv0.1.3; Forgejo registry + release page are live).Root cause was exactly the suspected 5 s cap, but it was self-inflicted:
colab_drive_authpolledcolab lsevery 250 ms while thedrivemountautomation held the kernel. The kernel serializes work, so the listing queued behind the automation, hit the hardcoded 5 s CLI budget and aborted the whole handoff withcli_timeout.What changed:
drivemountchild to exit (fulltimeout_sbudget) and only then verifies the mount withls— no listing while the automation runs;listTimeoutMs(default 60 s) instead of 5 s;ls+ a 4 s list budget → the handoff still succeeds.Upgrade and retest:
dsh plugin --profile web add --registry https://git.pvlb.dev/api/packages/dsh-plugins/npm/ dsh-colab@0.1.3, then restart the profile. The URL is still returned indata.urlonauth_pending; if the VM is left withBUSY (automation(drivemount))after a timeout,colab_session_restartclears the wedged kernel before retrying.