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

[BUG] Task get stuck in in-progress list when Payload has a large number as a value #166

Closed
hibiken opened this issue Jun 10, 2020 · 0 comments · Fixed by #169
Closed

[BUG] Task get stuck in in-progress list when Payload has a large number as a value #166

hibiken opened this issue Jun 10, 2020 · 0 comments · Fixed by #169
Assignees
@hibiken
Labels
bug Something isn't working

Comments

@hibiken
Copy link
Owner

hibiken commented Jun 10, 2020 •
edited
Loading

Describe the bug
When task get processes successfully, it should be removed from asynq:in_progress list in Redis. However the operation to removed the task fails when you have a large number in the payload (caused by JSON number overflowing the target type).

You'll see an error message like this when this happens.
WARN: Could not remove task id=brgdeqquof2o9md7qoq0 type="test2" from "asynq:in_progress": NOT FOUND; Will retry syncing
@hibiken hibiken added the bug Something isn't working label Jun 10, 2020
@hibiken hibiken self-assigned this Jun 10, 2020
@hibiken hibiken changed the title [BUG] Task get stuck in in-progress list [BUG] Task get stuck in in-progress list with Payload with large number as value Jun 10, 2020
@hibiken hibiken changed the title [BUG] Task get stuck in in-progress list with Payload with large number as value [BUG] Task get stuck in in-progress list when Payload has a large number as a value Jun 10, 2020
@hibiken hibiken mentioned this issue Jun 12, 2020
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@hibiken hibiken

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix JSON number ovewflow issue hibiken/asynq
1 participant
@hibiken