We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The CLI package command returns a "package analysis failed" error, but looking up the same package via the package endpoint succeeds.
package
Steps to reproduce this behavior:
phylum package nuget pagedlist 1.17.0
https://api.phylum.io/api/v0/data/packages/nuget/pagedlist/1.17.0
Both requests return package details.
This seems tied to the updated error messaging, but the pipelineStatus seems fine.
The text was updated successfully, but these errors were encountered:
CLI actually uses a slightly different endpoint. But the status there is reported the same.
> curl -s -H "Authorization: $(php auth token)" "https://api.phylum.io/api/v0/data/packages/nuget/pagedlist/1.17.0" | jq '{ pipelineStatus, pipelineError }' { "pipelineStatus": "Complete", "pipelineError": "" }
This appears to be yet another issue of "" vs null ...
""
null
Sorry, something went wrong.
kylewillmon
Successfully merging a pull request may close this issue.
Overview
The CLI
package
command returns a "package analysis failed" error, but looking up the same package via the package endpoint succeeds.How To Reproduce
Steps to reproduce this behavior:
phylum package nuget pagedlist 1.17.0
https://api.phylum.io/api/v0/data/packages/nuget/pagedlist/1.17.0
Expected Behavior
Both requests return package details.
Additional Context
This seems tied to the updated error messaging, but the pipelineStatus seems fine.
The text was updated successfully, but these errors were encountered: