-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
user_script:70: too many results to unpack #2764
Closed
matt-moven opened this issue
Aug 27, 2024
· 1 comment
· Fixed by #2765 or enjin/indexer#1326 · May be fixed by AlexanderSCK/Microservice-Ticketing-App#114, AlexanderSCK/Microservice-Ticketing-App#129 or AlexanderSCK/Microservice-Ticketing-App#137
Closed
user_script:70: too many results to unpack #2764
matt-moven opened this issue
Aug 27, 2024
· 1 comment
· Fixed by #2765 or enjin/indexer#1326 · May be fixed by AlexanderSCK/Microservice-Ticketing-App#114, AlexanderSCK/Microservice-Ticketing-App#129 or AlexanderSCK/Microservice-Ticketing-App#137
Labels
Comments
roggervalf
added a commit
that referenced
this issue
Aug 28, 2024
🎉 This issue has been resolved in version 4.16.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
This was referenced Sep 26, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
See #2709 for reference
We also ran into this bug and traced it down to the
collectMetrics
function in "moveToFinished-9.lua". We setmetrics.maxDataPoints
to 1. InmoveToFinished
,collectMetrics
tries to add the current metric and also fill in zero values for all the missed seconds, and then trims that list down tomaxDataPoints
. If a queue sees no jobs for enough time, and then processes a job and tries to update its metrics, theunpack()
with one metric and many zeros fails with error "too many results to unpack".bull/lib/commands/moveToFinished-9.lua
Line 70 in 886d764
Since the metric
prevTS
is not updated, all following jobs in the queue also throw the error.Bull version
4.16.0
The text was updated successfully, but these errors were encountered: