Skip to content
New issue

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

CLI returns error while API returns success #1524

Open
furi0us333 opened this issue Oct 22, 2024 · 1 comment · May be fixed by #1525
Open

CLI returns error while API returns success #1524

furi0us333 opened this issue Oct 22, 2024 · 1 comment · May be fixed by #1525
Assignees
Labels
bug Something isn't working needs triage Needs to be reviewed or assigned

Comments

@furi0us333
Copy link
Contributor

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:

  1. Run phylum package nuget pagedlist 1.17.0
  2. See error
  3. Look up package via API https://api.phylum.io/api/v0/data/packages/nuget/pagedlist/1.17.0
  4. See success

Expected Behavior

Both requests return package details.

Additional Context

This seems tied to the updated error messaging, but the pipelineStatus seems fine.
image

image

@furi0us333 furi0us333 added bug Something isn't working needs triage Needs to be reviewed or assigned labels Oct 22, 2024
@kylewillmon
Copy link
Contributor

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 ...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working needs triage Needs to be reviewed or assigned
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants