You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to contribute on this. I saw the issue with datetime.utcfromtimestamp() giving the wrong time. I think switching it to datetime.fromtimestamp() could fix it and return the correct local time.
This bit of code has existed in the repo for 10 years now. The case where this would produce unexpected results is when this section of code is used on a system which has its time set to a non-UTC timezone.
I'm not saying this shouldn't be addressed, but we should be careful to think through what impact this could have if changes to either handle UTC or to handle local tz.
datetime.utcfromtimestamp()
is used in the source code, which convertstime.time()
orself.now
parameter value to the wrong datetime instance.luigi/luigi/tools/range.py
Line 219 in 829fc0c
It should be:
The text was updated successfully, but these errors were encountered: