Repository navigation
StateFrame 0.4.36
StateFrame 0.4.36: the request-path randomness check passes again.
Changes
- Tests: the check that every random call on the request path is reviewed now covers the random calls used to build a measurement identity key. Those values never reach request bytes. A planted control proves that a new, unreviewed random call still fails the check.
No change to runtime behavior.
Known issues (fixes planned)
- In-place runs and exported patches can change the line endings or byte-order mark of untouched text files in the edit scope (see KNOWN_LIMITATIONS). A fix is being tested now.
- Linux: checks that run Go or Node programs fail under StateFrame's check memory limit. macOS is not affected.
- The first request of a run can differ between runs in one optional orientation section, depending on local cache state.
- On endpoints without an exact tokenizer, very dense content can be underestimated and push a request past the context limit.