Closed webdevian closed 2 years ago
Hi @webdevian!
Probably, it's something that is not related to the CLI and somehow related to JRE. Please check this thread - it looks like it's the same issue.
Thanks for the quick response. We get JRE installed through crowdin-cli via https://github.com/nvuillam/njre so I don't think we can choose a specific PATH.
It seems to be downloading the same version or JRE whether it works or not (https://download.oracle.com/otn-pub/java/jdk/8u131-b11/d54c1d3a095b4ff2b6607d096fa80163/jre-8u131-linux-x64.tar.gz
). Am I better off looking for help at Heroku or from the njre package maintainers
@webdevian recently we have updated the jDeploy version used to create the NPM package but have not yet deployed this change as there are no other features to deploy. The new version of jDeploy is using AdoptOpenJDK JRE instead of Oracle JRE. Maybe it should work ok in your case after releasing a new version of CLI.
Hello, I have the same problem running it with Bitbucket pipelines. Please, release a new versión.
Describe the bug Intermittently we get this error when the package is installed via Yarn. It fails 10-20% of the time and we've only seen it appear in the last few days. It breaks the build and we have to deploy again.
To Reproduce In package.json
"@crowdin/cli": "^3.7.7",
Config File
Expected behavior Expect it to install without error, like it does most of the time
Environment: Region - United States Stack - heroku-20 Framework - Node.js