Local EnsureProjectOpencode failure is logged at Debug, remote at Warn #531
Labels
No labels
backend
bug
chore
duplication
effort:complex
effort:medium
effort:trivial
enhancement
follow-up
frontend
fullstack
priority:high
ready-for-agent
refactor
security
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
dries/ocman#531
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?
Found during review of PR #523 (fix: relaunch a killed opencode on local create).
In the create-session handler, a failed local ensure is logged at
Debugwhile the equivalent remote-path failure logsWarn. A host that should be able to launch opencode but can't (e.g. tmux missing, port bind failure) fails silently under default log levels — the user just sees a session that never comes up, with nothing in the logs.Fix: log local ensure failures at
Warnto match the remote path (or justify the asymmetry with a comment). One-line change plus, if practical, a log-level assertion in the existing handler test.Validated against main @
2d661364: fixed / moot. The Debug-logging local pre-ensure no longer exists on main — handleCreateSession only pre-ensures on the remote path (internal/server/handlers.go:482), and that failure logs Warn (handlers.go:489-492). No Debug-level ensure-failure log remains anywhere. If PR #523 lands and reintroduces a local pre-ensure, re-check the log level in that review instead. Closing.