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
Browser version: NA (Related to Jest tests, so jsdom)
Firebase SDK version: 8.6.2
Firebase Product: firestore
[REQUIRED] Describe the problem
This may not be a firebase problem (although it very well could be), but it is tied to firebase, so I thought I'd leave this for your team's awareness/investigation.
Jest 27.0.1 does not exit tests cleanly in that it complains of pending asynchronous operations. The pending asynchronous operation when running --detectOpenHandles comes from the grpc client used by Firestore, it does not seem to close its socket, either in time, or it hangs. This may be due to its interaction with jsdom.
One thing to note is that Jest 25.5.4 does exit tests cleanly.
Hi @inf3rnus, thanks for the report. This is a duplicate of #4884. The logs when running jest with --detectOpenHandles option will help in the investigation. Thanks for the report, we appreciate it.
[REQUIRED] Describe your environment
[REQUIRED] Describe the problem
This may not be a firebase problem (although it very well could be), but it is tied to firebase, so I thought I'd leave this for your team's awareness/investigation.
Jest 27.0.1 does not exit tests cleanly in that it complains of pending asynchronous operations. The pending asynchronous operation when running --detectOpenHandles comes from the grpc client used by Firestore, it does not seem to close its socket, either in time, or it hangs. This may be due to its interaction with jsdom.
One thing to note is that Jest 25.5.4 does exit tests cleanly.
I've alerted the Jest team to this issue here: jestjs/jest#11464
Steps to reproduce:
Relevant Code:
https://github.com/inf3rnus/firebase-jest-pending-grpc-connection
Here's are some pictures showing what's happening:
Normal jest run:
Jest with --detectOpenHandles:
The text was updated successfully, but these errors were encountered: