fix: use systemd-run RuntimeMaxSec instead of timeout command #42
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.
The external timeout command was timing out systemd-run itself, not the bbolt check process inside the scope. Use systemd-run's built-in -p RuntimeMaxSec=6s to properly enforce the timeout on the process running within the scope.
🤖 Generated with Claude Code
Note
Replace external
timeoutwith systemdRuntimeMaxSec=6sto enforce the bbolt check timeout within thesystemd-runscope.Written by Cursor Bugbot for commit 6310281. This will update automatically on new commits. Configure here.