You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is not my best issue report, since ATM I don't have time to put up the proper minimal repro.
But, when running jest --detectLeaks --detectOpenHandles (I guess only --detectOpenHandles is relevant here) it often prints this:
Test Suites: 1 failed, 11 passed, 12 total
Tests: 1 todo, 17 passed, 18 total
Snapshots: 0 total
Time: 10.615s
Jest has detected the following 1 open handle potentially keeping Jest from exiting:
● DNSCHANNEL
> 1 | import got from 'got'
| ^
2 |
3 | const detectLeaks = process.argv.some(a => a.includes('detectLeaks'))
4 |
at new CacheableLookup (node_modules/cacheable-lookup/source/index.js:62:14)
at Object.<anonymous> (node_modules/got/dist/source/index.js:60:19)
at Object.<anonymous> (src/jestOffline.util.test.ts:1:1)
I'll just leave this issue there until I have more information, or someone else comes with a better reproduction..
got@11 is used here
The text was updated successfully, but these errors were encountered:
constgot=require('got');/*test('test',*/(async()=>{constdata=awaitgot('https://www.google.com');// expect(typeof data).toBe('object');// data.destroy(); // The same problem occurs without this code.})();
If you run this code you can clearly see that the process exits. So it's not Got's neither CacheableLookup's fault. @CatsMiaow already made a comment on Jest repo with simplest reproducible code.
This is not my best issue report, since ATM I don't have time to put up the proper minimal repro.
But, when running
jest --detectLeaks --detectOpenHandles
(I guess only--detectOpenHandles
is relevant here) it often prints this:I'll just leave this issue there until I have more information, or someone else comes with a better reproduction..
got@11
is used hereThe text was updated successfully, but these errors were encountered: