Repository navigation
Docs: beta findings from the 29 Oct diagnostics pull - #1039
Merged
Merged
Conversation
New finding 77 (UI freezes while playing on 9b7e0eb3); new occurrences of 72 and 71; 69's BUSY cause confirmed in the field; 76 fixed in the field. Closed rows 24, 26 and 30 shrunk to stubs to keep the plan under its old size. Dated record in docs/verification/. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
github-actions
Bot
added
the
documentation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Records the 29 Oct diagnostics pull (shared records up to 28 Oct 20:05 UTC) in the beta findings log and in a dated record,
docs/verification/2026-10-29-beta-diagnostics.md. No tester is named; only technical facts.9b7e0eb3(a MKII, about 6.5 min into the first boot after the update): the UI tick stood still 5.4-9.1 s while audio frames ran, CPU 100 %, playing at 150 BPM, 11 modules, no module machine on a track. STOP/PLAY after FX page edits; the site link had dropped 90 s before (against finding 75's two-windows guess). First freeze on a current base. Next step on the dev unit noted.c1ae2ee9): DSPs stopped for six self-tests until a power cycle, stall reason 1 next start. 72 is its own bug, not 74.903f8ed6(15-module restore,hotat +61 s while stopped with no key pressed, stall at the next start).903f8ed6,2ba936b9), before Fix: the Octatrack power-on restore tries a BUSY refusal again before leaving a module out #1026's retry, which has not yet run in the field with Ring SC.9b7e0eb3(issue Octatrack base: frame guard skips stock FLEX tracks while FM Synth is installed #999, fixed in Octatrack beta base: more DSP room (receiver in the shared window), FX2 swaps keep their block, with the fix/base-oct28 bundle and the Python firmware codec #1017); one unit at 90-100 % CPU for ~25 min with no shed/stall/freeze is noted as a watch.stalefailures (fix in its own PR) and a stall at the moment of a USB base update on two units but not a third.The plan is over the 32 KB cap, so closed rows 24, 26 and 30 are cut to stubs (details stay in Git history), as #950 did: the plan shrinks from 105,138 to 101,659 bytes.
Checks
vitest run --maxWorkers=1 scripts/docs.test.mjs src/catalog/docs-links.test.ts(10 passed) andcheckDocsagainstorigin/main(no growth, record name valid).Guides
Nothing lacking or wrong.
🤖 Generated with Claude Code