Bound incremental RESP parsing and deadlines - #12
Merged
Merged
Conversation
nicodes
added this pull request to stack #13
September 13, 2026 07:40
nicodes
force-pushed
the
issue-150-resp-bounds
branch
from
September 13, 2026 07:41
ece2625 to
9759eca
Compare
nicodes
force-pushed
the
issue-150-resp-bounds
branch
from
September 13, 2026 07:42
9759eca to
1c021f4
Compare
Merged
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.
A10 L1 — bounded incremental RESP I/O
Behavior layer for https://github.com/aviorstudio/fieldsofrevik/issues/150. Gate PR #11 merged as
84261d956c414dac0f390a6c5a611f4328e6b404; native stack sync replayed this layer trivially onto that exact merge.Self-verification evidence (Team No Review)
aviorstudio/gd-redis,issue-150-resp-bounds, exact replay head1c021f40ba741cfb09622d48cf6e242219c1dc4f; baselinedea4b076055080faac2aa90aa4bd252c4e70b754.request/poll_io/take_result/cancel; synchronous wrappers retained; bounded fixture cleanup.FLUSHDBremains disabled by default.godot-api->redis:3113on its private Compose network, pinned Redis 7 with 64 MiB maxmemory and no published port/TLS/AUTH. No game code changed.4.7.2.stable.official.ed1daf0bf; Docker 29.1.3; GNU timeout 9.9; Redis digestff02b58...28eadf.4/4.1/1; four malicious ZIP forms rejected; restored nine-file manifest and packaged editor lifecycle passed.3cb4c398186e401da6d04c6ea25550e6571318728b1ea00d7ff24c8567e620bf; installed tree9c79c79ce9f17798f1ce57d540b8efe470333b894ea53a0e59331c21d562a60d.tools/effect_endurance.py --stacks 1000PASS at Revik sourcea5ffb90f1beb3ef84ec3331ada1157d5e317c891, clean core/client diff SHA-256e3b0c442...b855; fixture SHA-2567aaf1705...a9b0; driver SHA-2562e165386...0c09. Status completed, requested/trigger/hero-power counts each 1,000. Fresh 1,000-stack JSON UTF-8 size is 64,829 bytes versus 8,388,608 bytes (8,323,779 bytes headroom; 129.40x). Evidence report SHA-256bab89cae...753f, identityaed284d0...e23b, loga730caf8...88e6. This is functional serialized-payload evidence, not performance certification; historical timings are not reused.timeout --signal=TERM --kill-after=5 660s env PATH=/tmp/opencode/godot-4.7.2:$PATH python3 tools/effect_endurance.py --stacks 1000 --evidence /tmp/opencode/a10-effect-endurance-a5ffb90-20260913-r2.1c021f40ba741cfb09622d48cf6e242219c1dc4f. Pre-sync run 34745800901 passed only obsolete headece2625....Correction (fieldsofrevik#150): Earlier evidence incorrectly said no identifiable 1,000-stack fixture existed. The caller identified the authoritative versioned fixture; the fresh run and identities above replace that statement.