Skip to content

StateFrame 0.4.32

Choose a tag to compare

View all tags
@FarsideResearch FarsideResearch released this 06 Nov 01:15
v0.4.32
a49efef
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.32: fix for runs stopping with "serialized continuation limits were removed or changed".

Fixes

  • A run with a turn limit (the default is 32 turns) could stop with "serialized continuation limits were removed or changed". This happened when a request had to be rebuilt after a turn had already been counted but before the request was sent: the rebuilt request reused the original's identity, so StateFrame's pre-send check compared it against out-of-date limits and refused it. The rebuilt request now gets its own identity, so the check compares it against the right limits. The check itself is as strict as before.
  • Verified with 20 requests on a hosted OpenAI-compatible endpoint with no errors.

Requests sent to the model are otherwise 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