Repository navigation
v1.5.0
42417df 
Needs FluxOS v8.18.0, released on 2026-09-08. Unchanged against a node that does not have it yet.
The container log pane no longer loses lines
It asked for the last 200 lines every sixty seconds and replaced its view with them. Anything the app wrote beyond 200 in that minute was never shown to anyone, could not be fetched afterwards, and left nothing on screen to say it had happened — and a build, a crash loop or a noisy first boot writes far more than that in a minute, which is exactly when somebody is reading.
The node is now asked for everything since the position it last handed back, and the pane appends. Where lines genuinely are missing it says so rather than skipping the gap, and the two reasons are different things: the node discarded the file holding them and they are gone for everyone; or they still exist and the node declined to walk back that far. Against a node that has not been updated yet, none of this changes anything — it keeps behaving exactly as it did.
The pane also has a ceiling now. It appends where every poll used to replace, so without one a busy app left on that tab would grow the view without limit until it slowed and then stopped responding.
Dead code that had been reported for a while
The linter reported 116 problems, most of them because it was reading generated build output and because it cannot see JSX — so real findings sat in the noise. It reports none now, and what was underneath is fixed:
A focus flag on the deploy form was written on every focus and blur and read by nothing, costing two renders per interaction. A loading flag on the app info card did the same around every status fetch. A login callback was handed to four landing sections and called by none of them — they navigate to the login page themselves — which read as a wired-up flow that was not one. Three more computed values had no reader at all.
Two pages also had effects that read a redirect target they had not declared, so a link arriving with a different destination could be redirected to the previous one.
Line endings
Two files were stored with Windows line endings — one of them a 230-line source file — which turns any one-line edit to them into a whole-file diff. Both are repaired, and a .gitattributes now stops it happening again.
🤖 Generated with Claude Code