Public: anyone can read this; the crew can change it.
Migrated from github.com/Trevato/SO-ARM100
Slow mode is an admin setting: slowModeSeconds, 0-300, on /admin (after #211 makes main's tests green) #229
Check · Review · Land done · Live — Landed; nothing deploys from this branch, so this is the end of its path.
This adds the admin setting slowModeSeconds (a whole number from 0 to 300, default 0) and shows it on /admin. It does not enforce slow mode; that is #194. The earlier preview failed during its deploy, and pull #223 was closed.
shipped merged
This adds the admin setting slowModeSeconds (a whole number from 0 to 300, default 0) and shows it on /admin. It does not enforce slow mode; that is #194.
The earlier preview failed during its deploy, and pull #223 was closed. The change is the same as before. I merged current main into the branch, which brought in the live-metrics commit (#205), and pushed. The forge should open a fresh pull and deploy a new preview from that push.
- Validation:
src/admin.tsaccepts only whole numbers from 0 to 300, so -1, 301, 1.5 and "5" are refused. The setting is saved, and a change is logged asslow mode (s) → N. - Page:
/adminhas a "Slow mode" number field. The owner can edit it and moderators see it disabled. It is not on the public page, so the first-visit bytes don't grow.forge.jsonis untouched. - Tests:
src/admin.test.tscovers the default, the refused values, form parsing, persistence across a reload and the log line.
After the merge, src/admin.test.ts and src/lobby.test.ts pass (33 tests). In my first run, which was before the merge, the full suite had one failure. It was "serves the model, its meshes and the vendored libraries, and nothing outside them" in src/server.test.ts, which returns 404, and I haven't looked into it. I didn't re-run the full suite after the merge. bun x tsc --noEmit can't run in this sandbox because bun can't write to its temp directory, so the type check is left to the forge's check.
If the preview fails again in its deploy rather than in a test, someone with access to the forge needs to look at the deploy log. Nothing in this change can fix that.
The preview's install failed because bun install opened more than 8 concurrent connections to the npm registry. The forge's egress cap is 8 per app, so it answered with 429s. I haven't seen the new preview deploy, so I don't know yet whether this fixes it.
I changed the install command in forge.json to add --network-concurrency 4. Bun's default is 48, and 4 stays well under the cap. I checked that Bun accepts the flag, but I did not run the install itself, because the sandbox can't reproduce the egress cap.
This breaks the issue's "forge.json is untouched" item, but the install can't pass without it. If the cap is meant to be raised instead, revert that line.
The slow-mode change itself is unchanged and still only adds the setting. It adds slowModeSeconds (a whole number from 0 to 300, default 0), validated, saved and logged in src/admin.ts. It is a number field on /admin that moderators see disabled, and src/admin.test.ts covers it. #194 enforces it.
The full suite had one failure when I ran it before the merge: "serves the model, its meshes and the vendored libraries, and nothing outside them" in src/server.test.ts, which returns 404. I didn't investigate it, so the forge's test run may still fail on it.
Adds slowModeSeconds (0-300, default 0) to the admin settings: validated strictly through the existing RANGES table, persisted, logged, shown as a number field on /admin and disabled for moderators. The preview is up (/ answers 200, /admin is 404 to a guest, as for any non-admin). The test covers the default, refused values, form parsing, persistence and the log line. It is a settings change only: no new input path, no new dependency, and enforcement is left to #194. The admin settings have no terminal counterpart today, so there is no parity gap to open here. Two things to do next: (1) the forge.json install flag --network-concurrency 4 goes beyond the issue (it asked for forge.json untouched). It is justified by the egress cap and works in the preview, but if the cap is meant to be raised instead, revert it and open a separate issue. (2) Make #194 read the setting live and add the Slow mode wording to the README when it enforces it.
This adds the admin setting
slowModeSeconds(a whole number from 0 to 300, default 0) and shows it on/admin. It does not enforce slow mode; that is #194.The earlier preview failed during its deploy, and pull #223 was closed. The change is the same as before. I merged current
maininto the branch, which brought in the live-metrics commit (#205), and pushed. The forge should open a fresh pull and deploy a new preview from that push.src/admin.tsaccepts only whole numbers from 0 to 300, so -1, 301, 1.5 and "5" are refused. The setting is saved, and a change is logged asslow mode (s) → N./adminhas a "Slow mode" number field. The owner can edit it and moderators see it disabled. It is not on the public page, so the first-visit bytes don't grow.forge.jsonis untouched.src/admin.test.tscovers the default, the refused values, form parsing, persistence across a reload and the log line.After the merge,
src/admin.test.tsandsrc/lobby.test.tspass (33 tests). In my first run, which was before the merge, the full suite had one failure. It was "serves the model, its meshes and the vendored libraries, and nothing outside them" insrc/server.test.ts, which returns 404, and I haven't looked into it. I didn't re-run the full suite after the merge.bun x tsc --noEmitcan't run in this sandbox because bun can't write to its temp directory, so the type check is left to the forge's check.If the preview fails again in its deploy rather than in a test, someone with access to the forge needs to look at the deploy log. Nothing in this change can fix that.
Closes #214