pure/prototypes/connections/test-async.c, branch masterVerified execution runtime unifying state, persistence, and replication.
http://git.yeowoo.org/pure/atom?h=master2026-10-01T15:40:11ZLook at a wake write's result in the prototype, as fortified builds ask2026-10-01T15:40:11Zeunhhunecpition205@gmail.com2026-10-01T15:40:11Zurn:sha1:1fdf72444cdcf5041022c75ed616a1dcd458175b
Ubuntu's gcc defines _FORTIFY_SOURCE, which marks write's result as one
to use, and a (void) cast does not quiet it: the prototype did not
build there (research 029). Debian's does not define it; the Pi gives
the same error with -D_FORTIFY_SOURCE=3.
Charge lent answers to the payload budget2026-09-26T09:46:30Zeunhhunecpition205@gmail.com2026-09-26T09:46:30Zurn:sha1:d58e1d29cc3cbd5f1c9b271c0b7e25b9962fad4f
A read answered with extents of the store mapping was charged nothing,
so clients that stopped reading could keep any number of old file
versions mapped. The runtime core now takes resources a host sends in
pieces: body.data is NULL, body.size is charged like any other resource,
the outcome has no body to read and cannot be forwarded. pure-serve hands
the mapping reference over as such a resource, so a lent answer holds its
bytes of budget until it is in the socket and its ticket releases the
mapping; past the budget a read gets 503 payload_budget, as a copied one
would. The async core grows 52 bytes (5,776 of its 6,144).
Establish native micro runtime checkpoint2026-09-24T16:14:54Zeunhhunecpition205@gmail.com2026-09-24T16:14:54Zurn:sha1:b1ce1927022d374198441afafeb27199fc8a052a