Mitigate Supabase Edge cache crashes in the SDK fixture - #511
Merged
Merged
Conversation
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
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.
Why
Main's Supabase fixture intermittently exits 135 before producing a bundle. Native
crash dumps and a no-SDK CommonJS reproduction identify a Supabase/Deno SQLite
cache-initialization race, not SDK bloat. Reported upstream as
supabase/edge-runtime#746.
Changes
fixture-only mitigation; the pinned runtime and published packages are unchanged.
native-dependency rejection, raw/compressed size budgets, real HTTP execution,
HMAC verification, crash evidence and cleanup. No retries or warm/shared caches.
The diagnostic-only
edge-crashbranch is not included and must never be merged.No Changeset, release, deployment, new dependency or normal CI workflow change.
Validation
passed with the isolated tmpfs. This is mitigation evidence, not an upstream fix.
Node 28,025,947 raw / 2,454,583 upload bytes; legacy 28,025,764 / 2,459,280 bytes.
paths (47.6 MB raw / 10.2 MB compressed), with the mitigation enabled.
assertion. The old test misses the deliberately misplaced image; the corrected
test rejects that mutant and passes with the valid invocation restored.
yarn checkand post-reviewyarn verify:fullpass.on final head
a04cb6fa2e9aa547b0a813887cc93d75a9f41b5c, including the real x64Edge fixture, packed Next browser tests, release dry run, and Node 20/22/24.
The preceding run 35828672200
also passed in full before the documentation-only evidence commit.
Fixes #510.