Keep HTTP responsive during owned blocking processing #15
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/owned-blocking-work"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Finite CPU and synchronous I/O work now use separate bounded admission and cancellation-safe ownership in wuast-common. Aborted callers transfer their handles to supervised cleanup, and permits remain held until the real join. Development UI assets use asynchronous filesystem reads. Existing public contracts stay compatible. Validation: full just gate passed, including real single-worker HTTP responses with occupied CPU/I/O capacity, cancellation, committed results, panic and interrupted cleanup.