ctime is in schema and model but verify scanner populates it correctly #13

Closed
opened 2026-02-08 17:16:26 +01:00 by clawbot · 1 comment
Collaborator

The schema has ctime INTEGER NOT NULL and the File model has CTime time.Time. However, the scanner should be verified to actually populate ctime correctly on all platforms. On macOS, ctime is birth time; on Linux it is inode change time. This difference should be documented.

Also verify that the exported snapshot database includes ctime and that restore sets it where possible.

Ref: parent issue #1

The schema has `ctime INTEGER NOT NULL` and the `File` model has `CTime time.Time`. However, the scanner should be verified to actually populate ctime correctly on all platforms. On macOS, ctime is birth time; on Linux it is inode change time. This difference should be documented. Also verify that the exported snapshot database includes ctime and that restore sets it where possible. Ref: parent issue #1
clawbot self-assigned this 2026-02-20 09:29:06 +01:00
clawbot added the needs-review label 2026-02-20 09:29:07 +01:00
Author
Collaborator

Closing: sneak decided to remove ctime entirely rather than fix its population. New issue will track ctime removal from schema, model, and scanner.

Closing: sneak decided to remove ctime entirely rather than fix its population. New issue will track ctime removal from schema, model, and scanner.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sneak/vaultik#13