| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Look at a wake write's result in the prototype, as fortified builds ask | eunhhu | 2026-10-01 | 1 | -1/+1 |
| | | | | | | | | 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 budget | eunhhu | 2026-09-26 | 1 | -1/+36 |
| | | | | | | | | | | | | | | 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 checkpoint | eunhhu | 2026-09-24 | 1 | -0/+330 |
 |
index : pure | |
| Verified execution runtime unifying state, persistence, and replication. | Yeowoo Labs |
| aboutsummaryrefslogtreecommitdiffstats |