fix: two things a fresh install trips over - #3
Merged
Merged
Conversation
The committed lockfile still recorded packages/flow at 0.1.0, so `bun install` on a fresh clone rewrote it and left every new checkout with a dirty tree — and `bun install --frozen-lockfile` failed outright. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Stopping a previous run is documented as a port problem, but a second opencode engine — another clone, or one a previous launcher left behind — shares the one database in the opencode data directory without necessarily holding either port. The engine then dies with `database is locked`, which looks nothing like a port conflict and is not fixed by freeing them. Document the symptom and a stop-by-process recipe for PowerShell and POSIX shells, in the English README and the 21 translations. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue for this PR
Closes #
Type of change
What does this PR do?
Two things a fresh install trips over, found by wiping OpenFlow off a Windows machine and reinstalling strictly from the README.
1. Stale
bun.lock. The lockfile recordedpackages/flowat0.1.0;packages/flow/package.jsonsays1.1.0. The lock was last committed atd0b63fca2(v1.0.0) and the version bump never regenerated it. Sobun installon a clean clone rewrites it — every new checkout is dirty before you touch anything — andbun install --frozen-lockfilefails. Regenerating the lock is the whole fix; the diff is one line.2.
database is lockedis undocumented. "Stop anything already running" treats a leftover run as a port problem. It is not always one. Every opencode engine opens the same database in the opencode data directory, and a second engine — another clone, or one a previous launcher left behind — can hold that database without holding either port. The engine then dies withFreeing 4096/5174 does not help, because the offending engine may not be on them. The section now names the symptom and stops the engine by what it is running instead of by port, with a PowerShell and a
pkill -frecipe. Added to the English README and the 21 translations.How did you verify your code works?
bun install --frozen-lockfileexits 0 on the regenerated lock (it failed before), andgit statusis clean after a freshbun install.bun openflow.ts), the engine, and the vite child. Matching all three matters — killing only the engine lets the launcher respawn it, which is how the original failure kept coming back.bun install,bun openflow.ts, engine on 4096, canvas on 5174, provider catalog loads.Screenshots / recordings
Not a UI change.
Checklist