| Name |
Last commit
|
Last update |
|---|---|---|
| .. | ||
| engine | ||
| packs | ||
| research | ||
| tests | ||
| ui | ||
| .gitignore | ||
| PHASE2_LOOPFINDER.md | ||
| README.md | ||
| TODO.md | ||
| autotune.py | ||
| beatocc.py | ||
| demos.json | ||
| foundry.py | ||
| kitgate.py | ||
| kitindex.py | ||
| restage.py | ||
| server.py |
66318b6e's comment and test docstring both claimed PLN heard the polled-loop stutter. He did not. The Foundry server was not running: port 8765 was another project's http.server, established two steps after the fix landed. The bug is real and of exactly the reported shape, and it stays fixed - but attributing a fix to a symptom it did not cause is how a wrong diagnosis becomes documentation, which is this morning's -inf-faders mistake again. Both places now say where it came from. The commit message is history and is left alone. And check-mix's --arm table called an unarmed `Mix` route "not recorded, by choice" while --mix blocks on precisely that. Two modes of one tool must not disagree about the same route.
| Name |
Last commit
|
Last update |
|---|---|---|
| .. | ||
| engine | Loading commit data... | |
| packs | Loading commit data... | |
| research | Loading commit data... | |
| tests | Loading commit data... | |
| ui | Loading commit data... | |
| .gitignore | Loading commit data... | |
| PHASE2_LOOPFINDER.md | Loading commit data... | |
| README.md | Loading commit data... | |
| TODO.md | Loading commit data... | |
| autotune.py | Loading commit data... | |
| beatocc.py | Loading commit data... | |
| demos.json | Loading commit data... | |
| foundry.py | Loading commit data... | |
| kitgate.py | Loading commit data... | |
| kitindex.py | Loading commit data... | |
| restage.py | Loading commit data... | |
| server.py | Loading commit data... |