Skip to content

Conversation

@thomasschafer
Copy link
Contributor

@thomasschafer thomasschafer commented Jan 20, 2026

Pull Request Submission Checklist

  • Follows CONTRIBUTING guidelines
  • Commit messages
    are release-note ready, emphasizing
    what was changed, not how.
  • Includes detailed description of changes
  • Contains risk assessment (Low | Medium | High) - n/a
  • Highlights breaking API changes (if applicable) - n/a
  • Links to automated tests covering new functionality - n/a
  • Includes manual testing instructions (if necessary)
  • Updates relevant GitBook documentation (PR link: ___) - n/a
  • Includes product update to be announced in the next stable release notes - n/a

What does this PR do?

Currently when there is no python on the user's PATH they see the following error when testing a Poetry project:

 ERROR   Unspecified Error (SNYK-CLI-0000)

           Error processing poetry project. [object Object]

Docs:    https://docs.snyk.io/scan-with-snyk/error-catalog#snyk-cli-0000

This PR renders the error to show up like this:

ERROR   Unspecified Error (SNYK-CLI-0000)

           Error processing poetry project. Could not find 'python' on your PATH.
           stderr: spawn python ENOENT
           stdout:

Docs:    https://docs.snyk.io/scan-with-snyk/error-catalog#snyk-cli-0000

How should this be manually tested?

Remove python from your PATH, and then test a Poetry project locally using the CLI. On main, you should see the first error above (with [object Object]), and pointing to this branch you should see the second (referencing a missing python installation).

What's the product update that needs to be communicated to CLI users?

None

@thomasschafer thomasschafer marked this pull request as ready for review January 20, 2026 16:12
@thomasschafer thomasschafer requested review from a team as code owners January 20, 2026 16:12
@PeterSchafer
Copy link
Contributor

Hey @thomasschafer,

thank you for improving the error mesage! Is there any chance that the plugin returns SNYK-0010 instead of a generic error?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants