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

Firebase emulator fails because Functions not completing its work in the time allotted #7673

Open
cmjordan42 opened this issue Sep 17, 2024 · 3 comments

Comments

@cmjordan42
Copy link

[REQUIRED] Environment info

Hi, I've already extensively documented this on StackOverflow and believe I've found the root of the problem after figuring out how your emulators interoperate.

https://stackoverflow.com/questions/78983940/firebase-functions-cannot-determine-backend-specification

Please consider improving the resiliency of the firebase-tools and firebase-functions packages as I mention in the answer. A very low-cost improvement would be bumping the timeout and putting in better logging around what this cryptic error message actually is talking about which is more like "failed to receive a response from functions subsystem within 10s timeout".

@google-oss-bot
Copy link
Contributor

This issue does not seem to follow the issue template. Make sure you provide all the required information.

@aalej
Copy link
Contributor

aalej commented Sep 18, 2024

Hey @cmjordan42, thanks for reaching out. I think starting firebase-tools v13.10.0, you can set the value of FUNCTIONS_DISCOVERY_TIMEOUT(see PR #7176) to increase the timeout. Could you give this a try?

Also, let me check with our team to see if we can update the error message to provide a clearer description of what caused the error.

@cmjordan42
Copy link
Author

Hi @aalej , I appreciate your consideration. I wish I had known about that flag, but I'm happy to just run it on the "local" WSL file system now realizing how much data it is reviewing each time I'm starting the emulator. Mentioning that flag in updated error messages may be worthwhile.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants