bun run lint:css hangs forever (lasertag check never returns) #2
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Symptom
bun run lint:css(lasertag check "src/**/*.module.css") never terminates. It prints the command echo and then produces no further output and no exit — observed running past 5 minutes with zero output on three separate invocations:It has to be killed manually.
lasertagis pinned at^0.5.2(resolved 0.5.2) in the rootdevDependencies.Why it matters
lint:cssis one of only three quality gates this repo has (check,lint:css, and the module'stsc). A gate that never returns is a gate nobody can run, so CSS violations accumulate unseen. It is also not wired into.forgejo/workflows/release.yml, so nothing catches this in CI either.Scope
Not a regression from the
@celilo/capabilities@^2.0.0bump (PR #1). That change touches onlycelilo-module/;lint:cssreadssrc/**/*.module.css, which the bump does not modify, and the hang reproduces the same way independent of it.Worth noting the invocation loses its quoting under zsh — the process shows as
lasertag check src/**/*.module.csswith the glob already expanded by the shell rather than passed through to lasertag. That may or may not be related to the hang, but it means lasertag is receiving a file list instead of the pattern it expects.Suggested next steps
bunx lasertag check src/<one>.module.css) to see whether it is the glob handling or the check itself.lint:cssscript needs the pattern protected from the shell.release.ymlso it is actually enforced.Filed while upgrading the celilo module (PR #1); the hang is pre-existing and outside that change's scope.