-
Notifications
You must be signed in to change notification settings - Fork 107
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
Weird behavior when computing the hash of a module #1277
Comments
@CryptoPascal31 Thank you for reporting this issue. I'm not able to reproduce your example on master. Can you please provide more system information? |
Ubuntu 22.04 But I've also tried with my self compiled version of Pact : b160c26.: just 1 commit before HEAD. And I have exactly the same result for both versions when I launch I attach the file. I've renamed it with a "txt" extension, since looks like GH does not allow files with a ".repl" extension. |
A new crazy element, I've just found out. When I change the name of the REPL file, it changes the results of the |
Indeed, this is an interesting observation. It turns out that running: We will investigate this further. Thanks for bringing this up! |
I confirm your observations. It seems to be ok in "interactive" mode, but fails when loading the file. I'm glad you managed to reproduce it. => I've done my job ;-) |
@CryptoPascal31 fixed by #1278 |
Thank you, I'll try to compile it tonight. |
I confirm: now it works perfectly as intended. Whatever I'm trying to do, I get always the same and reproducible result:
|
I see that the fix has been merged => Close |
Issue description
Just had a weird behavior of
(hash)
when computing the hash of module. The hash is not reproducible and looks like it is disturbed by the state of the REPL.Maybe this is related to: #1273
Steps to reproduce
In REPL:
gives:
Let's try again with a slight change (just add an empty printed line between the 2 prints)
gives:
Expected Behavior
I expect the hash function to be reproducible and all the hashes shouldn't depend on externals factors.
This is not only a theoretical case. Marmalade uses as a token ID, the hash of a structure containing modrefs and may suffer from the same issue.
The text was updated successfully, but these errors were encountered: