Skip to content

fix: download Drive9 companion from GitHub for install and update - #63

Open
qiffang wants to merge 1 commit into
tidbcloud:mainfrom
qiffang:fix/drive9-downloads-via-github
Open

qiffang wants to merge 1 commit into
tidbcloud:mainfrom
qiffang:fix/drive9-downloads-via-github

Conversation

@qiffang

@qiffang qiffang commented Sep 27, 2026

Copy link
Copy Markdown
Collaborator

The released shell installer can fail to download the Drive9 companion from releases.drive9.ai in Daytona sandboxes with curl: (35) Recv failure: Connection reset by peer. The GitHub-hosted companion installs successfully in the same sandbox under the same network policy.

This change points the shell installer, PowerShell installer, and ti update to https://raw.githubusercontent.com/mem9-ai/drive9-fe/main/site/releases. All three use that directory’s checksums.txt and retain SHA-256 verification and companion compatibility checks. The ti archive continues to come from tidbcloud/ti-cli GitHub Releases. The README, product principles, and installer fixture now match the download source.

Validation:

  • make test and make e2e passed; cloud lifecycle tests remain opt-in.
  • sh -n scripts/install.sh, Go formatting, and git diff --check passed.
  • Ran the exact patched installer with sh /tmp/install-ti-pr.sh --yes in a fresh Linux amd64 Daytona sandbox (daytonaio/sandbox:0.8.0). It installed ti 0.2.7 and Drive9 60b63d6 successfully with checksum and compatibility verification. ti --version, ti-drive9 version, and ti fs mount-file-system --help worked.
  • In that same sandbox, probes of both the CDN binary and SHA256SUMS failed with curl exit 35. An explicit domain allow-list update was rejected by Daytona’s organization-level network policy, so the successful GitHub installation used the original network restrictions. The temporary sandbox was deleted and its absence verified.

The live check validates installation and command availability, not an authenticated filesystem mount. Windows runtime execution was not tested. This change does not establish the cause of the CDN TLS resets; the published Daytona allow list already includes *.drive9.ai.

This branch has not been deployed

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

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant