Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Fix invalid RFC 3339 in TimeTagToAny (unreleased new feature) #540

Merged
merged 1 commit into from
May 26, 2024
Merged

Fix invalid RFC 3339 in TimeTagToAny (unreleased new feature) #540

merged 1 commit into from
May 26, 2024

Commits on May 23, 2024

  1. Don't produce invalid RFC 3339 using TimeTagToAny. 

    TimeTagToAny can produce strings that are not valid RFC 3339 timestamps through its use
of (time.Time).Format, whose signature does not allow it to return errors.

Signed-off-by: Ben Luddy <bluddy@redhat.com>
    @benluddy
    benluddy committed May 23, 2024
    Configuration menu
    Copy the full SHA
    77c571a View commit details
    Browse the repository at this point in the history