Skip to content

corrective/intend: known-answer tests for the custom timestamp.rs #15

Open

Description

@hyperpolymath

Type: corrective · Priority: intend

The hermetic SHA-256 (src/hash.rs) already pins NIST KATs, but the dependency-free RFC-3339 src/timestamp.rs (Hinnant civil-date algorithm) has no equivalent. Add round-trip + leap-year/boundary vectors so a calendar bug can't silently corrupt the event log.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething is broken or behaves incorrectlypriority:p2Normal - queue itscope:repoConfined to this repositorystatus:readyFully specified and ready to be picked up

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions