Skip to content

Orca driver: when GitHub refuses an upload, mint.sh reports a closed runtime connection #4

Description

@asabirov

Original request

None. An orchestrating agent found this while uploading a batch of PR screenshots on 2026-09-24.

Problem

After about 96 uploads to one repository in roughly an hour with the Orca driver, every later mint.sh call failed like this:

orca: The Orca runtime closed the connection before responding. Restart Orca and try again.
exit 3

Each call ran for about 84 s. The Orca runtime was healthy: orca status reported ready, and tab create plus a 90 000-character eval in a GitHub tab both succeeded in 2–3 s. A manual paste of a 1×1 PNG into /issues/new in the same browser left <!-- Failed to upload "probe.png" --> in the textarea within 5 s, and it stayed there for 60 s. So GitHub was refusing the upload, probably because of a rate limit. The script kept polling for a URL until the eval died, then reported a runtime failure. That points at restarting Orca, which does not help.

Three staging keys (github-attachment-transfer-*, about 740 000 characters in total) were also left in github.com localStorage from the failed runs.

Acceptance criteria

  • When GitHub writes its Failed to upload marker, mint.sh stops polling and exits with its own code and a message that says GitHub refused the upload.
  • Failed runs leave no staging keys behind.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

triage:P2Worth doing, no deadline pressuretriage:SAbout half a day

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions