The following leaks were detected:@@any-promise/REGISTRATION
See original GitHub issueIssue Description
The following leaks were detected:@@any-promise/REGISTRATION
└─┬ sequelize@5.21.3
└─┬ retry-as-promised@3.2.0
└── any-promise@1.3.0
What do you expect to happen?
No any leaks =)
Environment
- Sequelize version: 5.21.3
- Node.js version: v12.14.1
- Operating System: macOS 10.15.3
Issue Template Checklist
How does this problem relate to dialects?
- I think this problem happens regardless of the dialect.
- I think this problem happens only for the following dialect(s):
- I don’t know, I was using PUT-YOUR-DIALECT-HERE, with connector library version XXX and database version XXX
Would you be willing to resolve this issue by submitting a Pull Request?
- Yes, I have the time and I know how to start.
- Yes, I have the time but I don’t know how to start, I would need guidance.
- No, I don’t have the time, although I believe I could do it if I had the time…
- No, I don’t have the time and I wouldn’t even know how to start.
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
The following leaks were detected:@@any-promise ... - GitHub
My story start when I wanted to complete a job test using Hapi.js instead of express... The job is long behind me. Also,...
Read more >Hapi Lab The following leaks were detected:lr - Stack Overflow
In this new question why I get The following leaks were detected:lr even if there is no global var in the code. Running...
Read more >hapijs/hapi - Gitter
Does anyone know how to get details for @hapi/lab error: "The following leaks were detected:globalThis"? There doesn't seem to be any other output...
Read more >Memory leaks detected - Build Environment - CircleCI Discuss
... circleci all tests pass and my test suite (Lab, from Hapi) is reporting that The following leaks were detected:__core-js_shared__, cor…
Read more >lab v25.0.1 - hapi.dev
This is an alias of ids array property in .labrc file. -I , --ignore - ignore a list of globals for the leak...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I have been seeing in my tests from this morning… Since I am playing around with Hapi.js
@hapi/lab
, I have been thinking the error was from that new library to me.Seeing this issue, I tried
yarn lab --dry
and (1) it skips all my tests (2) but the error is still poisoning my tests exist status - not good for Continuous Deployment.Now, I don’t know how you connected this to sequelize b/c I just removed every direct and transitive call to anything-sequelize from my tests and I still have the error.
Here’s what else I have
package.json
$ yarn why any-promise
[UPDATE]
This issue has been automatically marked as stale because it has been open for 14 days without activity. It will be closed if no further activity occurs within the next 14 days. If this is still an issue, just leave a comment or remove the “stale” label. 🙂