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

Invalid local date time: <no zone> #299

Closed
tribut opened this issue Jan 7, 2023 · 0 comments
Closed

Invalid local date time: <no zone> #299

tribut opened this issue Jan 7, 2023 · 0 comments
Labels
Milestone

Comments

@tribut
Copy link

tribut commented Jan 7, 2023

Just noticed the following warning:

[warning] "WDateTime: Invalid local date time: <no zone>"                     
[info] - [DB UPDATER] Scheduling next scan                                    
[info] - [DB UPDATER] Using scan settings version 3                           
[info] - [DB UPDATER] Scheduling next scan at Sat Jan  7 16:35:35 2023        
[warning] "WDateTime: Invalid local date time: <no zone>"                     
[info] - [UI] New scan started!                                               

Not sure if it has any consequences, but when bind-mounting /etc/timezone into to the container it goes away.
I'm running epoupon/lms:latest from docker hub, which is currently at 3.34.0.

Thanks for the great app ❤️

@epoupon epoupon added the bug label Jan 7, 2023
@epoupon epoupon added this to the v3.36.0 milestone Jan 7, 2023
@epoupon epoupon closed this as completed Feb 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants