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

Not finding time for CET with millisecond and time with nanosecond #123

Open
sundarv85 opened this issue Mar 10, 2021 · 0 comments · May be fixed by #159
Open

Not finding time for CET with millisecond and time with nanosecond #123

sundarv85 opened this issue Mar 10, 2021 · 0 comments · May be fixed by #159

Comments

@sundarv85
Copy link

Hello,

I'm using

t, err := dateparse.ParseAny(v)

I'm trying the following input, and I'm getting

Parsing: 2017-04-03 22:32:14.322 CET  => 2017-04-03 22:32:14.322 +0000 UTC => failure
Parsing: 2017-04-03 22:32:14 CET  => 2017-04-03 21:32:14 +0000 UTC => success
Parsing: Mon Dec 26 16:22:08 2016  => 2016-12-26 16:22:08 +0000 UTC => success
Parsing: Mon Dec 26 16:15:55.103786 2016  => Error : parsing time "Dec 26 16:15:55.103786 2016": month out of range => failure

The first and the last seems to fail, while the second and third work...

Any thoughts on how to get it working?
klondikedragon added a commit to itlightning/dateparse that referenced this issue Dec 12, 2023
@klondikedragon
Add extensive format validation, bugfixes
1b1e0b3 
* Don't just assume we were given one of the valid formats.
* Also consolidate the parsing states that occur after timePeriod.
* Add subtests to make it easier to see what fails.
* Additional tests for 4-char timezone names.
* Fix araddon#117
* Fix araddon#150
* Fix araddon#157
* Fix araddon#145
* Fix araddon#108
* Fix araddon#137
* Fix araddon#130
* Fix araddon#123
* Fix araddon#109
* Fix araddon#98
* Addresses bug in araddon#100 (comment)

Adds test cases to verify the following are already fixed:
* araddon#94
@klondikedragon klondikedragon linked a pull request Dec 21, 2023 that will close this issue
Open
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
1 participant
@sundarv85