-
Notifications
You must be signed in to change notification settings - Fork 902
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 Tools broken on Intel Ice Lake (Assertion failed: new_time >= loop->time) #1772
Comments
@Yonom thanks for all the details and related issues! I won't pretend to understand the root cause here. Is there something you think we could do in the Firebase CLI to prevent or mitigate this? |
I am just a user of your product, I do not understand the core issue either, so sadly I cannot help much. |
Some quick snooping pulls up this libuv issue where the dev explains that this is a symptom of your system clock drifting in an unexpected way (I assume libuv relies on some form of constant tick which it's not getting). This library is used as part of the core Node.js runtime, so it's very unlikely there's anything we can possibly do to resolve this, it's either an issue with your system or an upstream (way upstream) issue in Node. |
same error here |
Was having same error, only to realize it was as a result of multiple apps in the project. I needed to specify which app I was deploying to firebase deploy --only hosting:theAppName |
@abeisgoat I'm curious, have you contacted the libuv and/or Intel people about this? As more and more 10th gen Intel procs are on the market, more people (like me!) are having this issue with random products using node.js. |
I had this exact problem also, it was fixed as follows: I don't understand neither the root cause of the problem, nor, why exactly it was fixed. but this what happend and firebase login worked after this. |
A fix was made in libuv, updating nodejs will probably use the patched version which solved the issue. @appdevworx |
I tried all the solutions here and other found in other sites, and none of them works. Therefore, I should use WSL, install node and firebase on it, and finally I was able to run the firebase commands. Hope this will be helpful for someone! |
(FIXED) |
Thanks for everyone chiming in, as I suspected it's a bug in Node so seems like general solution is to update / reinstall Node and try again. |
This solved my issue. Cheers! |
Thanks you , this solved the problem for me |
didn't work for me :( |
Environment info
7.6.2
Platform: Windows 10 Home 1903 Build 18362.356
Processor: i7-1065G7
Node Version: 10.16.3 LTS / 12.13.0 LTS
Test case
Problem only affects Intel Ice Lake processors on Windows.
No setup needed.
Steps to reproduce
Run any command. Example:
firebase login
Expected behavior
The command should work.
Actual behavior
Before any user input can be entered, firebase cli crashes.
See also
libuv/libuv#1633
Problem reported on Sept 13th. No acknowledgement from the libuv team yet.
Similar projects affected:
Heroku heroku/cli#1354
Github Actions virtual environments actions/runner-images#67
The text was updated successfully, but these errors were encountered: