Skip to content

Never build from a language server start, lock installs, refuse shim links - #3

Merged
S42yt merged 1 commit into
masterfrom
fix/safety
Sep 30, 2026
Merged

S42yt merged 1 commit into
masterfrom
fix/safety

Conversation

@S42yt

@S42yt S42yt commented Sep 30, 2026

Copy link
Copy Markdown
Contributor

This fixes the burnup paths that can exhaust a machine:

  • No builds when an editor starts the server. Before, when burn lsp / burn-lsp ran in a project pinned to a missing version, it started an optimized source build of Burn (several GB of RAM). If the editor restarted the server, several builds ran at once. Now the server uses the default version and prints which version to install.
  • Install lock. A second install of the same version stops with "another burnup is installing …" instead of building in parallel. A lock older than an hour counts as stale.
  • No self-referencing links. burnup link refuses a folder whose bin/burn is a burnup shim, because burnup would then run itself forever.

The end-to-end tests cover all three, and pass.

🤖 Generated with Claude Code

https://claude.ai/code/session_01PCXUjgpGnka9y7AHKfnN3w


Generated by Claude Code

… to link a shim

A missing pinned version no longer starts a source build from burn lsp; the
server uses the default version and says what to install. Installs of the same
version cannot run at the same time. burnup link rejects a folder whose burn is
a burnup shim, which would make burnup run itself forever.
@S42yt
S42yt merged commit 812b430 into master Sep 30, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant