-
Notifications
You must be signed in to change notification settings - Fork 391
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
Timestamp handling #138
Comments
Anyone? |
Running into this as well. Have you tried uncommenting? |
uncommenting will work. However I open a thread here so as to discuss the intention of this regression, or if it a feature rather than a regression. |
Is @manast still hiding? |
I am a bit confused too why these are out commented, should work to uncommented AFAICS. |
@manast - Do you want a pull request for un-commenting out those two lines of code? |
Closed
manast
pushed a commit
that referenced
this issue
Mar 3, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In bullmqv4, Job.fromJSON () method, job.timestamp is not recovered (in fact commented out).
This creates a problem for UI when trying to read jobs from IDs. The timestamp will always be set to Date.now () in the constructor, regardless of the timestamp stashed in RedisLayer.
Sounds like a bug?
The text was updated successfully, but these errors were encountered: