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

[Bug]: SandboxedJob interface missing the queueName prop #2439

Closed
1 task done
Matthew-John-Emerson opened this issue Feb 21, 2024 · 0 comments · Fixed by #2446
Closed
1 task done

[Bug]: SandboxedJob interface missing the queueName prop #2439

Matthew-John-Emerson opened this issue Feb 21, 2024 · 0 comments · Fixed by #2446
Labels
bug Something isn't working

Comments

@Matthew-John-Emerson
Copy link

Version

5.3.0

Platform

NodeJS

What happened?

The SandboxedJob interface is missing the queueName prop. However, it is already a part of the actual sandboxedJob object. This is even enforced by typescript as JobJsonSandbox has both queueName and prefix as additional data. This is happening because SandboxedJob is defined in terms of JobJson instead of JobJsonSandbox.

How to reproduce.

import { SandboxedJob } from 'bullmq'
export default async (sandboxedJob: SandboxedJob) => {
    await job.log('Working on job from', sandboxedJob.queueName)
}

Relevant log output

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct
@Matthew-John-Emerson Matthew-John-Emerson added the bug Something isn't working label Feb 21, 2024
@Matthew-John-Emerson Matthew-John-Emerson changed the title [Bug]: [Bug]: SandboxedJob interface missing the queueName prop Feb 21, 2024
github-actions bot pushed a commit that referenced this issue Feb 24, 2024
## [5.3.2](v5.3.1...v5.3.2) (2024-02-24)

### Bug Fixes

* **sandbox:** extend SandboxedJob from JobJsonSandbox ([#2446](#2446)) fixes [#2439](#2439) ([7606e36](7606e36))
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.

1 participant