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

Time Parse Bug in V2.3.2 #823

Closed
ZengYueWei opened this issue Apr 20, 2021 · 2 comments
Closed

Time Parse Bug in V2.3.2 #823

ZengYueWei opened this issue Apr 20, 2021 · 2 comments

Comments

@ZengYueWei
Copy link

I was using v2.3.2.
File Input like '4/16/2021 11:59:00 PM'.
Previous version(v2.3.0)would parse that into '4/16/2021 23:59', but on v2.3.2 it would be parsed into '4/16/2021 11:59'.
@ZengYueWei
Copy link
Author

Looking forward the solution, since there're some OOM issue on v2.3.0 occasionally, which i cannot reproduce and so difficult to locate it. And that's also the reason why i updated.

@xuri xuri closed this as completed in 725cc66 Apr 20, 2021
xuri added a commit that referenced this issue Apr 20, 2021
@xuri
Fixed #823, 12/24 hours time format parsing error
f5a20fa
@xuri
Copy link
Member

xuri commented Apr 20, 2021

Thanks for your feedback, I have fixed it, please try to use the master branch code.

jenbonzhang pushed a commit to jenbonzhang/excelize that referenced this issue Oct 22, 2023
@xuri
Fixed qax-os#823, 12/24 hours time format parsing error
cf27c77
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

No branches or pull requests
2 participants
@xuri @ZengYueWei