Skip to content

Harden bootstrapper: resolve releases via redirect, not the rate-limited API - #333

Merged
jp-spotter merged 1 commit into
thoughtspot:devfrom
jp-spotter:fix/bootstrapper-install-reliability
Jul 24, 2026
Merged

Harden bootstrapper: resolve releases via redirect, not the rate-limited API#333
jp-spotter merged 1 commit into
thoughtspot:devfrom
jp-spotter:fix/bootstrapper-install-reliability

Conversation

@jp-spotter

Copy link
Copy Markdown
Collaborator

The bootstrapper resolved the latest release by calling api.github.com/releases/latest, which is rate-limited to 60 requests/hour per IP when unauthenticated. Shared CI and corporate egress IPs exhaust that quota and get HTTP 403, so installs and self update fail intermittently.

It now resolves the latest tag via the github.com/releases/latest web redirect instead, which is not subject to that quota and needs no token. All HTTP GETs also gain a small retry with backoff.

Verified against all three callers (install, self update, and the version-check notification): the return still carries tag_name and published_at, so nothing downstream breaks. The change stays standard-library-only and Python 3.9+, per the bootstrapper's constraints.

@jp-spotter
jp-spotter requested a review from a team as a code owner July 24, 2026 05:49
@jp-spotter
jp-spotter merged commit ae3b1f4 into thoughtspot:dev Jul 24, 2026
3 checks passed
@jp-spotter
jp-spotter deleted the fix/bootstrapper-install-reliability branch July 24, 2026 05:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant