-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Warn: Keccak bindings fail on first install #1584
Comments
I tried to install Truffle 5.0.0 and got the same issue. |
@wbt Looks like npm will not install a different major version when using |
Thank you for raising this issue! It has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. If you would like to keep this issue open, please respond with information about the current state of this problem. |
@stalebot is getting a little too aggressive here. The issue still exists and I think could still be more of a turn-off for new users. A duplicate was reported just 11 days ago; should we really as general practice be opening duplicates and letting earlier reports autoclose as "stale" when an issue persists? (I would recommend against adopting that.) |
Thanks for your response! This issue is no longer considered stale and someone from the Truffle team will try to respond as soon as they can. |
@wbt We recently made stalebot way less aggressive (180 days I believe instead of 60 or 90), but it seems like it might require further tweaking. I agree with your thoughts about duplicates. Happy to continue to evaluate stalebot practices and adjust accordingly. |
@gnidan Can you have a comment on or reference to an item reset the timer? This was definitely not a 180 day timer. |
Yeah keccak bindings compilation are failing on my end too...
|
I can reproduce as well: Node Version: v12.3.1 It works on node v11.10.1. |
keccak@1.4.0 installation succeed on node@10.7.0, failed on v8.15.0 && 12.4.0 |
We need to get rid of all transitive dependencies to The current dependency tree as defined by
We can see that Latest What is strange is that I don't see |
This is the output of
|
So one of the reasons is coming from
The |
I think this may also be due to the way keccak is implemented with supporting streams. I know that this is not limited to trufflesuite, as I have seen this issue for a while come up sporadically. It can also arise from the use of |
Reproduced just now with the following Dockerfile:
Very off-putting. I understand how hard it can be to get a particular version removed completely from the dependency tree! In my case, after running the above and examining |
This issue is quite old, can anyone confirm that this is still an issue with the latest version of Truffle? |
I vaguely recall seeing it recently, but don't recall if that was with the latest version. |
I just started a new docker container (to ensure I was working from a clean environment) and installed
Hopefully this is helpful. Godspeed. |
So it may have disappeared due to dependency updates or something similar. I'll leave this here for a bit longer and if no one else can confirm that this still exists I'll go ahead and close this. Thanks again everyone! |
Closing this issue as no one has confirmed that this still exists since @eggplantzzz comment above. Please leave a comment or open a new issue, dear future reader, if you find that this is still an issue for you! <3 |
Issue
Installing the new Truffle 5 per instructions produces a one-time error about keccak bindings compilation failing.
Steps to Reproduce
First, I had a previous version of Truffle installed, and after reading the blog post etc., I decided to try the newer version. I ran
npm update -g truffle
which got me the response+ truffle@4.1.15
updated 5 packages in 5.098s
I then ran
npm install truffle -g
as instructed.Expected Results
+ truffle@5.0.0
updated 1 packages in 1.234s
or something like that. Numbers other than the 5 might have been higher/different.
Actual Results
Running the same command again gave the Expected Results.
Therefore, this issue may be difficult to reproduce, but maybe reading the error message triggers a recollection for somebody of a missed step (e.g. including a dependency on a particular version or later of keccak?)
This issue would seem most likely to be encountered by new users.
Environment
node --version
): 9.3.0npm --version
): 6.5.0The text was updated successfully, but these errors were encountered: