feat(kernel-store): support absolute database paths #821
+13
−1
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.
Modify
getDBFilenameto detect and pass through absolute paths unchanged, instead of always joining them with the base directory. This enables the daemon to store its database at a fixed location outside the default relative path (e.g.~/.ocap/kernel.db).Note
Low Risk
Small, well-tested path-handling change limited to database filename resolution; main risk is unexpected directory creation/permission failures for absolute paths.
Overview
Enables configuring SQLite storage using an absolute
dbFilenameby updatinggetDBFilenameto detect absolute paths,mkdirthe parent directory, and return the path unchanged.Adds a focused unit test to assert the absolute-path behavior (including ensuring the parent directory is created) while preserving existing in-memory (
:...) and tmpdir-relative path handling.Written by Cursor Bugbot for commit 0cae785. This will update automatically on new commits. Configure here.