Summary
SnapshotFile::time is a jiff::Zoned, and its default Display includes the RFC 9557 timezone annotation suffix:
2026-05-01T10:45:42.7376742+02:00[+02:00]
The [+02:00] at the end is technically correct (RFC 9557) but unusual for end-user output. Most CLIs that show snapshot timestamps don't carry it.
Why it matters
Anything that displays snapshot time in a human-facing context (CLI listings, dashboards, log lines) ends up either accepting the noisy suffix or re-parsing+reformatting the Zoned value. The latter forces a jiff dependency on the consumer (see related issue: jiff leaked-dependency).
Suggestion
One of:
- Add a helper, e.g.
SnapshotFile::time_display(&self) -> String, returning a cleaner format like 2026-05-01 10:45:42 +02:00.
- Document
Display behavior with an explicit note ("includes RFC 9557 IANA tz annotation; use time.strftime(...) to drop it").
- Leave formatting up to callers — but then ideally re-export
jiff::Zoned (separate issue).
Workaround
Re-format on the consumer side. Not blocking.
Summary
SnapshotFile::timeis ajiff::Zoned, and its defaultDisplayincludes the RFC 9557 timezone annotation suffix:The
[+02:00]at the end is technically correct (RFC 9557) but unusual for end-user output. Most CLIs that show snapshot timestamps don't carry it.Why it matters
Anything that displays snapshot time in a human-facing context (CLI listings, dashboards, log lines) ends up either accepting the noisy suffix or re-parsing+reformatting the
Zonedvalue. The latter forces ajiffdependency on the consumer (see related issue: jiff leaked-dependency).Suggestion
One of:
SnapshotFile::time_display(&self) -> String, returning a cleaner format like2026-05-01 10:45:42 +02:00.Displaybehavior with an explicit note ("includes RFC 9557 IANA tz annotation; usetime.strftime(...)to drop it").jiff::Zoned(separate issue).Workaround
Re-format on the consumer side. Not blocking.