fix(installer): download Drive9 companion from GitHub - #61
Merged
guangleibao merged 2 commits intoSep 27, 2026
Merged
Conversation
|
|
Downloading the companion via `https://raw.githubusercontent.com/mem9-ai/drive9-fe/...` worked around the Netlify reset seen in Daytona sandboxes but hard-codes a GitHub raw URL that has its own rate limits, cache behavior, and availability profile — not intended as a distribution channel. Route the shell installer to `https://releases.drive9.ai/latest/` instead. This is the S3 + CloudFront release channel now published by the drive9 release-cli workflow (mem9-ai/drive9#1003). It: - Reproduces cleanly in Daytona sandboxes where drive9.ai (Netlify) resets and github.com raw is sometimes throttled. - Serves the same `drive9-<os>-<arch>` binaries and a SHA256SUMS file in the identical `<sha256> <name>` format, so the installer's existing `awk '$2 == name'` verification is unchanged. - Is CDN-fronted (global edge cache) and controlled by us, so we can invalidate/rotate as needed. Updates the installer regression fixture to expect the new host, and adjusts README/product principles to describe the new source. PowerShell installer and `ti update` continue to use Drive9's origin release endpoint (unchanged in this PR). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
guangleibao
approved these changes
Sep 27, 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 macOS/Linux installer can download
tifrom GitHub in a Daytona sandbox, but fails when it reaches the Drive9 companion ondrive9.ai(curl: (35) Recv failure: Connection reset by peer). Download the companion binary andchecksums.txtfrom the existing publicmem9-ai/drive9-fe/main/site/releasesdirectory on GitHub instead.Both companion requests now share one base URL. Existing SHA-256 verification, companion command compatibility checks, platform selection and installation paths remain in place. The installer fixture now rejects companion downloads from the old host, and the README/product principles describe the new source. This change covers
install.sh; PowerShell installation andti updateretain their current source.Validation:
sh -n scripts/install.sh,git diff --check,make testandmake e2epassed.ussandbox (daytonaio/sandbox:0.8.0, Linux/amd64). In the same sandbox the old checksum URL still failed with curl 35, while installation from GitHub succeeded, including checksum and compatibility validation. Installed versions:ti 0.2.6and Drive9d17f0da. The test sandbox was deleted and its absence verified.The observed reset does not establish Netlify as the root cause. This PR addresses installer downloads; filesystem API connectivity and FUSE lifecycle behavior are separate from this change.