branch builds consistently failing
This has been happening for a while so maybe we need to update a version or something, but every branch we open, our railway integration to build the branch in a container instantly fails. This is the error I see in the logs
ERROR: failed to solve: process "/bin/bash -ol pipefail -c yarn run build" did not complete successfully: exit code: 1
Any ideas how to resolve?
33 Replies
Project ID:
0ee68194-4729-4be6-abc5-38998747b9d5full build logs please?
project id: 0ee68194-4729-4be6-abc5-38998747b9d5
How do I show you the full build logs?put them in a .txt file and send them here
I do not have anything to open rtf, please use a plaintext .txt file
wait hold on
pdf should work
bruh
that's the first time I've ever seen someone give their logs in pdf format, can I just ask what was so hard about a .txt file?
textEdit on mac doesnt export to .txt
You likely have out of date packages.
Stack Overflow
Error message "error:0308010C:digital envelope routines::unsupported"
I created the default IntelliJ IDEA React project and got this:
Error: error:0308010C:digital envelope routines::unsupported
at new Hash (node:internal/crypto/hash:67:19)
at Object.createHa...
Are you using node 17 by chance? 🤔
node 16 actually
do I need to update anything on the railway side?
It’s an issue with the package.json and lock file.
@Brody by default is railway using 16 or 18? 🤔
aside from the dependency conflicts you are likely using an outdated webpack version (or an outdated package that is using an outdated webpack version) that depends on deprecated open SSL v1 hashing algorithms. upgrade whatever uses webpack
Yep
default is 16
is this by chance a create react app?
(using 18 wouldn't solve the issue, the issue is an outdated package)
For what it’s worth if it’s 16 and it is react there’s a good chance updating react scripts may resolve this.
it definitely will, but his logs didn't mention anything about react-scripts, so I asked 🙂
Im on react 17.0.2 fwiw
?
it started off as one years ago
since been ejected and customized
ah gotcha, then you should have webpack listed as a first class dependency, try updating it
"webpack": "^4.46.0"
we on 5.82.1
is there any gotchas with the version bump?
oh probably
yea Ill look into it
you think that'll resolve the issue?
4.46.0 is from jan 11 2021, they were definitely using openssl v1 back then. so yeah confident it will fix the
ERR_OSSL_EVP_UNSUPPORTED issueAlright thank you