-
Notifications
You must be signed in to change notification settings - Fork 985
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
Solve intermittent node_modules/web3/dist/web3.min.js (No such file or directory) #2937
Comments
Current balance: 0.000000 ETH |
This was solved by #2877 |
Ah, gahd damn. Have just funded it as well... OK then, will work to undo it manually, thanks @v2nek |
@v2nek This is not a solution, it's a hack to get around the root of the problem. See the additional information section in the issue. @andytudhope Leave it be, please. |
@oskarth |
@stephengroat This can happen locally too though, so not just a Jenkins config issue. But I'm all for checking return codes. One can just wrap shell command in it and check return code I think. Here are some docs https://jenkins.io/doc/pipeline/steps/workflow-durable-task-step/#code-sh-code-shell-script |
even though Jenkins sets the since |
Already fixed: #4974 |
User Story
As a developer, I want to have a reliable build process so I can focus on gettin work done.
Description
Type: Bug
Summary: Fix build scripts and instructions so that
node_modules/web3/dist/web3.min.js
is always present.Expected behavior
node_modules/web3/dist/web3.min.js
(and more broadly,node_modules/web3/
) should always be present when runningnpm install
or equivalent.Actual behavior
Reproduction
lein prod-build
sometimes results inCaused by: java.io.FileNotFoundException: node_modules/web3/dist/web3.min.js (No such file or directory)
andweb3
isn't installed.Additional information
This bug leads to hacks like https://github.com/status-im/status-react/blob/develop/Jenkinsfile.nightly#L8-L17, as well as countless questions and time wasted for people on Riot / core contributors.
Possible leads: web3/web3.js#1041 as well as moving to yarn.
The text was updated successfully, but these errors were encountered: