Skip to content

StateFrame 0.4.31

Choose a tag to compare

View all tags
@FarsideResearch FarsideResearch released this 06 Nov 00:32
v0.4.31
c618bfc
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

StateFrame 0.4.31: clearer errors when the check sandbox fails to start.

Changes

  • When the sandbox that runs checks fails to start, or fails its startup import check, the error now includes the process's exit status (when it can be proven) and the last part of its log, instead of only a low-level "Broken pipe" or communication error. This makes failures caused by things like a full disk or quota much easier to diagnose.
  • Nothing else about startup, retries or cleanup changed.

Requests sent to the model are unchanged.

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.
Assets 5
Loading