You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When trying to install a package with haxelib install I get the following exception: Error: std@date_set_day.
$ haxelib install lime
Downloading lime-8,0,2.zip...
Download complete: 0.24KB in 1s (0.2KB/s)
Download complete: 125.28MB in 5.2s (23775.2KB/s)
Error: std@date_set_day
If I change my timezone from AST (UTC-04) to GMT (UTC+00) the previous command works as expected.
This same scenario occurs when also running a program. I can reproduce this issue only on a system running Pop!_OS 20.04 (and Pop!_OS 22.04 on a virtual machine). I have not run into that issue on other systems; I tested that on Manjaro and NixOS.
haxelib version is 4.1.0
Expected result
Use haxelib commands without needing to change my system time/date.
This issue was also reported by #513 , the user reportedly solved that by also changing their system time/date.
The text was updated successfully, but these errors were encountered:
SocratesDz
changed the title
haxelib throws an exception when installing any library or running a programhaxelib throws an exception when installing any library
Sep 22, 2023
Problem description
When trying to install a package with
haxelib install
I get the following exception:Error: std@date_set_day
.If I change my timezone from AST (UTC-04) to GMT (UTC+00) the previous command works as expected.
This same scenario occurs when also running a program. I can reproduce this issue only on a system running Pop!_OS 20.04 (and Pop!_OS 22.04 on a virtual machine). I have not run into that issue on other systems; I tested that on Manjaro and NixOS.
haxelib version
is4.1.0
Expected result
Use
haxelib
commands without needing to change my system time/date.This issue was also reported by #513 , the user reportedly solved that by also changing their system time/date.
The text was updated successfully, but these errors were encountered: