Repository navigation
Release v0.5.2
v0.5.2
Released: 2026-10-24 · Branch: main · Previous: v0.5.1 (2026-10-24).
A patch so people can sign in to lake.live with Google: lake refused any request whose headers
passed about 4 KiB with 431 header_too_large, which a browser signed in through Clerk reaches after
an OAuth round trip (#1108). Everything else is v0.5.1.
Changes
| PR | Change |
|---|---|
| #1109 | Request headers up to 1 MiB in all (LAKE_HTTP_MAX_HEADER_BYTES, 8 KiB to 16 MiB). boost::http's defaults were 8 KiB in all and 4 KiB a field, and its parser applies the field limit to the whole header block, so every request's headers were capped near 4 KiB; lake now sets both to the limit. An idle connection costs about 49 KiB of resident memory (was about 25 KiB) (../serving/http.md) |
| #1106 | How a person gets an account on lake.live (docs) |
| #1105 | v0.5.1's notes name its image digest (docs) |
Before it rolls
- Nothing new: no schema change, no new required setting. orama-operator v0.9.2 or later, as for
v0.5.1. - At lake's default 4096 connections, idle connections can take about 200 MiB; lake.live's pods are
limited to 512 MiB.
Known issues
Those of v0.5.1, and:
- The apex
lake.liveanswers/llms.txtwith the region picker, not the agent text
(#1110). - lake.live's published price list has only the model-token rates (lake#755).
Verification
HttpConnections.ABrowsersClerkCookiesFitLakesHeaderLimits: a 12 KiB Cookie with 20 KiB of headers
is answered; past 1 MiB, one field or many, it is still431.HttpConnections.AnIdleConnectionCostsLittleMemory, now with lake's own limits: 49 KiB per idle
connection, under its 256 KiB bound.- All 216 HTTP tests pass (
ctest -R Http, macOS, against zetta v0.5.0). The full suite was not
rerun for this patch (launch day; Steve: "cut the new version of lake").