fix: say why runtime lock acquire refuses an absent store - #441
Merged
Conversation
agmsg_runtime_lock_acquire returned 1 without a word when the runtime db was missing. Print one stderr line with the db path before returning; the status stays 1. The line avoids the words actas-lock.sh classifies as transient, so its retry decision is unchanged (both classify as unknown). Closes #424 Refs #407 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01XTcYRimavoero895uewFR6
kappaseijin4claude
deleted the
fix/issue-424-runtime-lock-db-missing
branch
September 13, 2026 05:55
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
2 participants
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 #424:
agmsg_runtime_lock_acquireがruntime DB不在時に無音でreturn 1していた問題を修正。Closes #424、Refs #407
実装
agmsg_runtime_lock_acquireのDB不在分岐のみ変更。returnの直前にstderrへ1行出力する。戻り値は1のまま。stdoutには何も出さない。他の関数（owner/verify/release）とDBがある場合の経路は変更していない。
呼び出し元への影響確認
scripts/lib/actas-lock.shは試行ごとのstderr生テキストを_actas_lock_gate_classify_errorで分類し再試行を判断する。新しい行はunknownに分類され、修正前の空文字列もunknownだったため再試行判断は変わらない。対照としてError: database is lockedを与えるとtransientを返すことを確認し、分類そのものが機能していることを確認した。codex-bridge-launcher.shは2>/dev/nullで呼んでいるため影響なし。受入条件
test_storage.bats36/36、test_actas_lock.bats41/41、test_actas_integration.bats20/20 全PASS変異試験
追加したprintfを削除→KILLED（FAIL）。main修正前の実装に新試験を当てると無音の失敗を再現（FAIL）。DB在りのケースはいずれもpass。
README への影響
無。
🤖 Generated with Claude Code
https://claude.ai/code/session_01QCtgi8wVJDRaMwXHZmkHqT