-
Notifications
You must be signed in to change notification settings - Fork 77
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
uuid1() fails in Erlang 19.3 but not in Erlang 20 #18
Comments
this also fails again in erl 21 |
Sorry for not having time looking into this until now. Is this related to #19 ? What environment is used? (OS, Erlang from source or package manager etc?) |
RE #19 , it could be (see below*), but my original hunch was that it was related to the Erlang timestamp changes, because UUID4 works fine, and UUID1 is the method that uses the timestamp. This is running in the standard Erlang Docker release. This issue does not happen on my personal MAC*, but only happens when I use the more recent versions of Erlang in Docker which are Unix (alpine? Ubuntu?). Because of this the host OS is different, see here: https://hub.docker.com/_/erlang/) |
I've tried OTP 19, 20, and 21; and also tried the docker images for said What version of erlang-uuid do you use? If you aren't using v0.5.2 can What Docker network driver are you using? I.e. do you have a proper |
Right now I wasn't pinning a particular version, I have in my rebar.config:
In Docker Erlang 19 this is blowing up with
The calling line is
Note uuid 4 works fine, e.g.,
has no problem. That's why I suspect it's related to the timezone changes? EDIT: this fails for me on v0.5.2 as well. |
The same line:
Fails in Erlang 19.3, but works in 20. In 19.3 it bombs with the error:
However,
works in both. I'm not an expert in Erlang, HOWEVER my guess is it has something to do with
os.timestamp
here: https://github.com/avtobiff/erlang-uuid/blob/master/src/uuid.erl#L101This is just a guess of where the problem is because I recall that Erlang changed the behavior of this at some point.
The text was updated successfully, but these errors were encountered: