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

Cannot parse "Jan 20 21:17:01" #79

Open
jftuga opened this issue Jan 24, 2019 · 4 comments · May be fixed by #80
Open

Cannot parse "Jan 20 21:17:01" #79

jftuga opened this issue Jan 24, 2019 · 4 comments · May be fixed by #80

Comments

@jftuga
Copy link

jftuga commented Jan 24, 2019

Fatal Error: parsing time "Jan 20 21:17:01": month out of range

This format is used in Debian's auth.log

Could you please add this format?

@araddon
Copy link
Owner

araddon commented Jan 24, 2019

So if i am reading this correctly, there is no year in this, we just assume current year?

@jftuga
Copy link
Author

jftuga commented Jan 24, 2019

Yes, assume current year.

@jftuga jftuga changed the title Cannot parse " Cannot parse "Jan 20 21:17:01" Jan 24, 2019
@araddon araddon linked a pull request Jan 25, 2019 that will close this issue
@araddon
Copy link
Owner

araddon commented Jan 25, 2019

I am struggling to decide if i want to support this format. It seems to have some magic "assume this year" given it is prone to be wrong by the time it gets parsed. I have a pr that fulfills it but am leaning against it at the moment.
#80

@jftuga
Copy link
Author

jftuga commented Jan 26, 2019

Yes, upon further thought, I think that is the right choice. The only other suggestion I can think of is to somehow make it optional.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants