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.

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

Errors parsing dates #52

Open
radu-matei opened this issue Mar 23, 2022 · 1 comment
Open

Errors parsing dates #52

radu-matei opened this issue Mar 23, 2022 · 1 comment
Labels
bug Something isn't working

Comments

@radu-matei
Copy link
Member

We've had a few distinct errors parsing the date field in the page header:

  • for date = "2022-03-14":
TOML parsing error: input is not enough for unique date and time for key `date` at line 3 column 8
  • for date = "2022-03-14T00:22:56Z" (on Windows, not exactly sure what the issue is here, the error is very NOT helpful):
`Error rendering "content_top" line 30, col 54: date_format helper: Couldn't convert parameter date to type DateTime < Utc >. It's Null as JSON. Got these params: [PathAndJson { relative_path: None, value: Constant(String("%Y-%m-%dT%H:%M:%SZ")) }, PathAndJson { relative_path: Some("page.head.date"), value: Context(Null, ["page", "head", "date"]) }]`
@radu-matei radu-matei added the bug Something isn't working label Mar 23, 2022
@technosophos
Copy link
Collaborator

the date parser is very strict. So it MUST be a full ISO 8601 date.

I have no idea what the problem with the second date is. I'm not even sure how there can be an error on Windows that doesn't appear on other OSes. AFAIK, the date parser does not use any host OS features.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants