cli: heroku-cli broken for Win64 on Intel Ice Lake
There appears to a bug associated with libuv when running under Windows 10 on Intel Ice Lake processors. Although this is not a native heroku-cli bug, it appears to affect users on the most recent Intel processor family (e.g. Intel Core i-7 10xxx chips).
What is the current behavior?
Attempting to run any interactive commands (login, update, etc) returns the following error. It appears to be an acknowledged bug in libuv, but the maintainers there are dismissing it as a simple time sync problem (hint: it’s not). Note that I’m not running this in the WSL, but rather in the git-shell for Windows (also attempted in Powershell, same error).
$ heroku login
Assertion failed: new_time >= loop->time, file c:\ws\deps\uv\src\win\core.c, line 309
What is the expected behavior?
I would expect a prompt for my credentials.
$ heroku --version
heroku/7.33.3 win32-x64 node-v11.14.0
Windows 10 Home Version 1903 OS build 18362.267
About this issue
- Original URL
- State: open
- Created 5 years ago
- Reactions: 5
- Comments: 31
@rejhgadellaa I’m on a Surface Laptop 3 i7 UEFI 28.25.140.0 and the issue cleared up for me sometime in Dec-Jan when others started having success. I didn’t manually install a firmware update or anything. Good luck!
UPDATE: This bug is no longer an issue with the Surface 3 Laptop
Dell released a firmware update for the XPS that I believe updates the timing for Icelake. For other XPS users I suggest checking that you are running the latest BIOS.