Skip to content

Fix configuration HTTP deadlines across stalled frames - #10

Merged
nicodes merged 1 commit into
mainfrom
fix/monotonic-http-deadlines
Sep 6, 2026
Merged

nicodes merged 1 commit into
mainfrom
fix/monotonic-http-deadlines

Conversation

@nicodes

@nicodes nicodes commented Sep 6, 2026 •

Copy link
Copy Markdown
Member

A configuration request started after a long frame could immediately time out: Godot 4.7.2 charged the preceding frame to its new HTTPRequest timer. Measure the deadline from monotonic request-start time instead. Use nonblocking polling so cancelling a request whose peer withholds its response cannot block waiting for a native HTTP thread.

Preserve existing result/error contracts and add transport result metadata. Complete callbacks once, release the owned request, and validate deadlines. Prepare v0.0.2.

Validation: all four Godot test scripts pass, including real loopback HTTP after a 1.2-second frame, successful cleanup, silent-peer timeout at time scale zero, owner cleanup and disabled/invalid deadlines. CI/release use a checksum-verified Godot 4.7.2 binary and the same bounded runner, rejecting runtime errors and missing PASS markers.


View with [code]smith Autofix with [code]smith
Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.

@nicodes
nicodes merged commit e129c17 into main Sep 6, 2026
3 checks passed
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