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.

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

Thrown DelayedError from Sandbox processor causes 'Missing lock for job 2. failed' #2566

Closed
imperfect-circuits opened this issue May 16, 2024 · 0 comments · Fixed by #2567
Closed
Labels
bug Something isn't working

Comments

@imperfect-circuits
Copy link
Contributor

err.message == 'DelayedError' ||

Becaused Sandboxed Processors create new errors (rather than just rethrowing what was made

const err = new Error();
), and the check is done on 'message' rather than name, a thrown DelayedError is not read properly, causing the 'Missing lock for job' error.

I used the Process Step Jobs process (and delayed a job but with a timeout (yes, the timeout I used was not of a timestamp, but just the seconds), and I got the aforementioned error.

await job.moveToDelayed(500, token); throw new DelayedError(The error occured);`

@manast manast added the bug Something isn't working label May 17, 2024
github-actions bot pushed a commit that referenced this issue May 21, 2024
## [5.7.10](v5.7.9...v5.7.10) (2024-05-21)

### Bug Fixes

* **sandboxed:** ensure DelayedError is checked in Sandboxed processors ([#2567](#2567)) fixes [#2566](#2566) ([8158fa1](8158fa1))
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants