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

[bug] guacone query vuln hangs #1561

Closed
jeffmendoza opened this issue Dec 7, 2023 · 2 comments · Fixed by #1580
Closed

[bug] guacone query vuln hangs #1561

jeffmendoza opened this issue Dec 7, 2023 · 2 comments · Fixed by #1580
Labels
bug Something isn't working

Comments

@jeffmendoza
Copy link
Collaborator

Describe the bug
guacone query vuln does not return

[jeffm@fedora guac]$ go run ./cmd/guacone query vuln "pkg:guac/spdx/ghcr.io/guacsec/vul-image-latest"
{"level":"info","ts":1701983654.642494,"caller":"logging/logger.go:70","msg":"Logging at info level"}
{"level":"info","ts":1701983654.6425474,"caller":"cli/init.go:67","msg":"Using config file: /home/jeffm/git/guac/guac.yaml"}
  C-c C-csignal: interrupt
[jeffm@fedora guac]$ 

To Reproduce
Steps to reproduce the behavior:

  1. Startup guac, must include nats/ingestor/csub with deps.dev collector. If just running gql only, the hang will not happen
  2. guacone collect files ../guac-data/docs/
  3. guacone certifier osv --poll=false
  4. guacone query vuln "pkg:guac/spdx/ghcr.io/guacsec/vul-image-latest"

Expected behavior
command returns

GUAC version
head

Additional context
Seems like a deadlock, as CPU is 0 (an infinite loop would use a lot of cpu).

@jeffmendoza jeffmendoza added the bug Something isn't working label Dec 7, 2023
@ridhoq
Copy link
Contributor

ridhoq commented Dec 8, 2023

I believe I ran into this when testing #1540

@pxp928
Copy link
Collaborator

pxp928 commented Dec 12, 2023

It seems not to happen all the time but after a few attempts to run guacone query vuln "pkg:guac/spdx/ghcr.io/guacsec/vul-image-latest", it does cause a deadlock with the go run ./cmd/guacingest. It looks like it gets locked up by calls to the graphQL server.

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

Successfully merging a pull request may close this issue.

3 participants