Open KyleSmith0905 opened 4 months ago
This started happening a month ago when running our test suite which is too big for me to isolate the problem but I believe it is due to the exec command for us:
firebase emulators:exec \"npm run test:app\" --project demo-local --only firestore,storage,auth
I only had the commands:
firebase emulators:start --import=.sparrow-design/emulator-temporary
firebase emulators:export .sparrow-design/emulator-export
I also run a lot of fs commands to overwrite (and save) the emulator folder every minute. So that is a likely root for me. However, all of my emulator data is accessible in those files despite the crash occurring.
This sometimes happens to me even though i am not importing the data i am just running a new instance
[REQUIRED] Environment info
firebase-tools: 13.3.1 (latest)
Platform: Windows 11
[REQUIRED] Test case
This has happened 3 times for seemingly random reasons.
I cannot reproduce it reliably.
[REQUIRED] Steps to reproduce
For context I have done the following in my code, I made a script that:
firebase emulators:export .sparrow-design/emulator-export
Directly prior to the bug I was receiving this error from Firebase: #5888 (Though I have a feeling that this is not the cause).
I have a feeling the cause might be from me closing the command prompt while I'm exporting some folder or something.
[REQUIRED] Expected behavior
I wanted to find a solution on my own but I could not see any Java code in this repository (so I don't know where I'd look).
[REQUIRED] Actual behavior