-
Notifications
You must be signed in to change notification settings - Fork 14.6k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
fix: year 54714 is out of range issue with async queries #21656
Conversation
Codecov Report
@@ Coverage Diff @@
## master #21656 +/- ##
=======================================
Coverage 66.82% 66.82%
=======================================
Files 1798 1798
Lines 68827 68827
Branches 7333 7333
=======================================
Hits 45997 45997
Misses 20951 20951
Partials 1879 1879
Flags with carried forward coverage won't be shown. Click here to find out more.
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
why frontend change cause this issue? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @hughhhh, you should check out the query.star_time
from logging.
start_dttm = datetime.fromtimestamp(query.start_time)
ValueError: year 54714 is out of range
@EugeneTorap i spent the majority of the week trying to figure out the issue, and actually update the logic. With no luck I was hoping to revert this code since it's actually blocking all async queries execution then we can revisit the issue from your PR. The main thing is that master is broken because of this PR and is blocking our release of superset. @exherb @zhaoyongjie for some reason with the conversion of the component the client is sending milliseconds instead of seconds, the weird thing is the code isn't touching anything with |
/testenv up |
@yousoph Ephemeral environment creation failed. Please check the Actions logs for details. |
@hughhhh I found the root cause of this bug. Please see the PR #21667 cc: @EugeneTorap |
This is great news, we don't need to revert my PR! |
Ephemeral environment shutdown and build artifacts deleted. |
SUMMARY
Reverting PR causing issues with async queries
Whenever a user enables async queries, all results are throwing the following error:
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
TESTING INSTRUCTIONS
ADDITIONAL INFORMATION