Open antonio0 opened 5 years ago
That's no good - let's get to the bottom of this! First question, are you running bull or bee-queue (and which version of those are you running)?
I'm running bull v3.4.3
May have been introduced by #126 cc @gcox
I'm guessing the id
is undefined somehow. That would have blown up the code prior to #126 as well, though we would have gotten a better error message.
Doesn't seem like there's a valid reason for id
not to be a string by the time we're passing it to the hashId
helper. Is there?
What's the easiest way to debug this? I would like to see the full payload of the job causing the issue. Is there a debug mode?
I've put a console.log to print the "jobs" array right before the render method for that, and it showed that one of the items in the array was null. Like
[
{ normal job stuff },
null,
{ normal job stuff }
]
not sure if this is a problem on the Bull side or Arena.. I was looking at the "active" state. I could make a PR to filter out null values so it won't crash, but it's probably worth investigating how to solve the root cause?
Same issue. I tried deleted a stuck job that won't go away from the "Active" tab by manually running:
127.0.0.1:6379: del bull:file:123456
Now the /file/active end point will not load at all:
Internal Server Error
In the logs, the error is TypeError: Data mus be a string or a buffer
Receiving this issue as well, utilizing Redis max-memory policy results in the web ui spitting this error when navigating to page with a list that would contain a job that was evicted from Redis.
same error on 2.6.3, any news about it?
bump — seeing this issue as well
There's on job in my queue that I suspect might be in a corrupted state or simply in a state that Arena is having trouble reading. In the UI we just get the message "Internal Server Error". I'm running version 2.5.2