Repository navigation
Use response-bounded handler ABI validation for fixed frontend release - #742
Merged
Merged
Conversation
…ntries Co-Authored-By: Codex <noreply@openai.com>
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.
Read-only evidence isolates the fixed frontend release stop to an unsupported 32-handler count limit: existing named exports have valid handler arrays and identifiers but exceed that count. Use the already enforced 512 KiB response budget to derive a conservative finite entry bound, preserving full export/handler equality before activation.
The actual publisher first reproduced the rejection offline with 33 valid unchanged handlers. Regression coverage now accepts that ABI and still stops additions, removals, changed/invalid handlers, unknown fields and an oversized valid metadata response. Existing authentication, bindings/runtime checks, no-retry policy, fixed backend, rollback and default deploy behavior are retained. No Worker activation is claimed by these offline tests.