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

fix(sandboxed): fix detecting special errors by sending default messages #2967

Merged
merged 1 commit into from
Dec 18, 2024

Conversation

roggervalf
Copy link
Collaborator

fixes #2962

@@ -13,7 +13,7 @@ module.exports = function (job) {
throw new Error('Not yet!');
}
if (job.attemptsMade < 2) {
throw new UnrecoverableError('Unrecoverable');
throw new UnrecoverableError();
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Will this still work if the user passes a different message?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes, it will

@roggervalf roggervalf force-pushed the fix-default-message-for-errors branch from b55b28e to 2293b95 Compare December 17, 2024 03:58
@roggervalf roggervalf force-pushed the fix-default-message-for-errors branch from 2293b95 to c0c6dae Compare December 18, 2024 04:33
@roggervalf roggervalf merged commit 52b0e34 into master Dec 18, 2024
11 of 12 checks passed
@roggervalf roggervalf deleted the fix-default-message-for-errors branch December 18, 2024 12:14
github-actions bot pushed a commit that referenced this pull request Dec 18, 2024
## [5.34.3](v5.34.2...v5.34.3) (2024-12-18)

### Bug Fixes

* **sandboxed:** fix detecting special errors by sending default messages ([#2967](#2967)) fixes [#2962](#2962) ([52b0e34](52b0e34))
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.

[Bug]: DelayError throwing in Child Processor breaks without Message
2 participants