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
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
We also ran into this bug and traced it down to the collectMetrics function in "moveToFinished-9.lua". We set metrics.maxDataPoints to 1. In moveToFinished, collectMetrics tries to add the current metric and also fill in zero values for all the missed seconds, and then trims that list down to maxDataPoints. If a queue sees no jobs for enough time, and then processes a job and tries to update its metrics, the unpack() with one metric and many zeros fails with error "too many results to unpack".
Description
my job queue processor some time can complete and no throw the unpack error. after few time the job will return the unpack error.
Minimal, Working Test code to reproduce the issue.
(An easy to reproduce test case will dramatically decrease the resolution time.)
Bull version
v4.10.4
Additional information
my redis have 19 queues
some queues will have repeat job
how to solve the problem
The text was updated successfully, but these errors were encountered: