You may encounter issues or unexpected behavior running Tidelift CLI. Here are some things you can do to troubleshoot, but please reach out to support@tidelift.com with any questions.
- Ensure that you are on the latest version of the Tidelift CLI. You can check the current version by visiting https://download.tidelift.com/cli/tidelift-cli.version and compare to the current installed version by running
tidelift version
. We regularly update the CLI with fixes and improvements. Information on upgrading is found at the bottom of the CLI installation doc. - Ensure that you can reach the Internet from your machine (either developer workstation or CI system). Running
curl https://api.tidelift.com/subscriber/healthcheck
should include OK in the response (Linux/Mac only) - Ensure that the Tidelift CLI can access the internet by running
tidelift selftest --project test
- Ensure that you’re using a correct API key and that the key has not been revoked. The most common case of key revocation is that your trial has ended.
- If you are running scan or align and it fails with Exit status 1 but no other information, we may be unable to generate a lockfile. Manual instructions for each platform are as follows but may give more errors than you see exposed from the tool.
- Python:
pip freeze --local
- Java:
mvn -Dstyle.color=never dependency:list -DoutputFile=maven-resolved-dependencies.txt
- Other ecosystems do not have to generate a lockfile at this time
- Python:
Comments
Article is closed for comments.