Skip to content

Fix extraction completion logic failing due to undefined job#197

Open
alexculealt wants to merge 2 commits intomainfrom
fix/completion-failing-undefined-job
Open

Fix extraction completion logic failing due to undefined job#197
alexculealt wants to merge 2 commits intomainfrom
fix/completion-failing-undefined-job

Conversation

@alexculealt
Copy link
Collaborator

BullMQ can return entries of jobs with undefined data, skip processing those.

@rsaksida
Copy link
Member

@alexculealt Weird. Do we know what those jobs are?

@alexculealt
Copy link
Collaborator Author

@alexculealt Weird. Do we know what those jobs are?

@rsaksida, those were seen only once in my local environment which lead to an extraction staying at 100%, in progress instead of complete. I didn't follow up on which jobs they were but I am not surprised as my environment has been fairly unstable (restarting Postgress, Redis & workers - probably even while the jobs were being enqueued). The idea of the fix is to not crash if such a condition was to occur - but I'd be happy to keep the original code if we think a visible fail would be more useful to lead us to a potential root cause.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants