-
Notifications
You must be signed in to change notification settings - Fork 918
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 emulators:start
not working on WLS on Windows 10
#1458
Comments
Reading this page: It says:
Then it goes on to say:
So this is something that is new in WSL2 but also going to change before WSL2 is finalized, meaning that I don't think we should do anything within Thanks for reporting this @FezVrasta ! |
I'm not using WSL 2 tho, AFAIK I'm using version 1 |
@FezVrasta oh that's interesting, thanks for sharing! Assigning to @abeisgoat since he has a Windows setup and I don't. |
Hi, any update on this? Running into the same problem. |
cc @Karasuni |
I'm seeing this issue on Windows 10 Build 18362 running WSL 1, not WSL 2. Also the issue I reported is with firebase-tools 7.1.0 but does not occur with 7.0.2. |
I've reproduced the same issue with Win 10 1903 (build 18362.239), WSL 1, firebase-tools 7.1.0 and 7.1.1. For now downgrading to 7.0.2 is fine as a workaround. |
I have a new theory. In 7.1.0 we introduced a dependency on "chokidar" for
file watching which is a native module. Native modules can cause
os-specific issues. It's possible that is why 7.1.0+ stopped working on
WSL.
…On Mon, Jul 22, 2019, 6:29 PM Rory Dungan ***@***.***> wrote:
I've reproduced the same issue with Win 10 1903 (build 18362.239), WSL 1,
firebase-tools 7.1.0 and 7.1.1. For now downgrading to 7.0.2 is fine as a
workaround.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#1458?email_source=notifications&email_token=ACATB2V6AL7TXI23VUBFEFTQAZNHVA5CNFSM4H43MOYKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2RUMAI#issuecomment-514016769>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACATB2UATJUGV3HCDY6MLO3QAZNHVANCNFSM4H43MOYA>
.
|
I was able to reproduce this bug at home on my personal machine (we don't have Windows at work) so it's definitely real! I didn't have time to start debugging but I will try that next. |
Just a clue. So it only terminates if firebase-tools are installed locally. My |
Issue persists with firebase-tools 7.3.0 on WSL 1.
WSL version: 1 |
Can confirm the issue persists on 7.4.0 as well. |
Emulator is unusable on WSL due to this issue. Doesn't work on actual Windows either! firebase/functions-samples#572 |
Ok version |
Thanks Sam. Working great for me now. |
[REQUIRED] Environment info
firebase-tools:
7.0.2
Platform:
WSL on Windows 10
[REQUIRED] Test case
An empty project with the auto-generated Cloud Functions boilerplate is enough to reproduce it.
[REQUIRED] Steps to reproduce
Run
firebase emulators:start
[REQUIRED] Expected behavior
I should be able to use the local environment.
[REQUIRED] Actual behavior
It starts the local server at port 5001, if I open it in Chrome I get a
{ "status": "alive" }
response, but after 30 seconds it shuts down by itself because of a "timeout".The project works fine when deployed to Google Cloud. I tried to run it with
sudo
also.If I visit the demo "hello world" endpoint I get an error saying the endpoint is not available.
I tried to run it with
--debug
but no additional information is displayed during the shutdown/timeoutThe text was updated successfully, but these errors were encountered: