You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit d72e237
Browse filesBrowse the repository at this point in the historyBrowse files
fix(opencode): keep the timestamp scan inside the message's own time object
Two findings from a CodeRabbit review of this branch.
`extract_message_timestamp` searched for the first `"time"` anywhere in the
payload and then for `"created":` without a bound, so a `time` object
belonging to something else could contribute the number. A failed scan is
harmless — the caller falls back to a full parse — but a wrong one silently
drops an in-range entry. Require the canonical `"time":` key, require the
object to open right after it, and keep the `created` search inside that
object. Checked against 1037 real records (600 database rows, 437 message
files): still agrees with a full parse on every one, with no fallbacks.
`has_json_file` judged entries with `path.is_dir()`, which follows
symlinks, while the collection pass it feeds uses `file_type()` and skips
them. Detection could therefore claim files that would never be read, and
a symlinked cycle would recurse until the stack gave out. Match
`collect_files_with_extension` instead.
0 commit comments