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

Date parsing fails when "time/large-dates" feature is enabled #34

Open
morganava opened this issue Sep 22, 2024 · 1 comment · May be fixed by #35
Open

Date parsing fails when "time/large-dates" feature is enabled #34

morganava opened this issue Sep 22, 2024 · 1 comment · May be fixed by #35

Comments

@morganava
Copy link

When the "time/large-dates" feature is enabled, the format_description strings used to parse ASN.1 GeneralizedTime and ASN1.UTCTime becomes ambiguous. The parser will greedily consume the month digits for the leading year.

Arguably a deficiency in the upstream time crate, not seemingly allowing anyway to specify how many digits are expected in a year.
morganava added a commit to morganava/simple_asn1 that referenced this issue Sep 22, 2024
@morganava
Resolve date parsing ambiguity when parsing dates when "time/large-da…
fa7816f 
…tes" feature is enabled

- add explicit delimitter between year and month in date parsing format string
- enable "time/large-dates" feature to dev-dependencies

resolves acw#34
This was referenced Sep 22, 2024
Open
Closed
@morganava
Copy link
Author

Upstream issue: time-rs/time#683

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Resolve date parsing ambiguity when parsing dates when "time/large-da… morganava/simple_asn1
1 participant
@morganava