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

[DEP0174] DeprecationWarning: Calling promisify on a function that returns a Promise is likely a mistake. #2784

Open
kingfishx23 opened this issue Nov 25, 2024 · 4 comments

Comments

@kingfishx23
Copy link

(node:25) [DEP0174] DeprecationWarning: Calling promisify on a function that returns a Promise is likely a mistake.
DeprecationWarning: Calling promisify on a function that returns a Promise is likely a mistake.
at node:internal/util:434:17
at new Promise ()
at bound (node:internal/util:419:12)
at Queue.processJob (/app/node_modules/.pnpm/[email protected]/node_modules/bull/lib/queue.js:1210:22)
at process.processTicksAndRejections (node:internal/process/task_queues:105:5)

Description

I get this error when running in Node docker environment v22

Minimal, Working Test code to reproduce the issue.

just create a normal queue

(An easy to reproduce test case will dramatically decrease the resolution time.)

Bull version

4.16.4

Additional information

@timuster
Copy link

timuster commented Dec 7, 2024

Running into the same problem (i.e., the deprecation warning) on [email protected] and Node v22.12.0.

@simenflatby
Copy link

simenflatby commented Dec 13, 2024

Same thing here with same stack trace as @kingfishx23 for Node.js v22.9.0 and bull v4.16.4.

@manast
Copy link
Member

manast commented Dec 13, 2024

Any chance you upgrade to BullMQ? as Bull codebase ages, it is not unexpected that there will come this kind of warnings with newer versions of NodeJS. Thanksfully is just a warning though, the code should work the same.

@simenflatby
Copy link

Any chance you upgrade to BullMQ? as Bull codebase ages, it is not unexpected that there will come this kind of warnings with newer versions of NodeJS. Thanksfully is just a warning though, the code should work the same.

@manast Absolutely the correct think to do👍 We have had a task for that in or back-log for ages that I hope we get to soon! We have quiet extensive usage across a lot of apps, so it's not done quickly.

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

No branches or pull requests

4 participants