8000 test: test_update sha256 error · Issue #4971 · intel/cve-bin-tool · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

test: test_update sha256 error #4971

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.

Sign up for G 8000 itHub

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

Jump to bottom
Open
terriko opened this issue Mar 24, 2025 · 3 comments
Open

test: test_update sha256 error #4971

terriko opened this issue Mar 24, 2025 · 3 comments

Comments

@terriko
Copy link
Contributor
terriko commented Mar 24, 2025 
 =========================== short test summary info ============================
FAILED test/test_cli.py::TestCLI::test_update - KeyError: 'sha256'
======= 1 failed, 29 passed, 4 skipped, 5 warnings in 196.89s (0:03:16) ========

I haven't debugged it yet, but we're currently seeing failures with the error above.
@Shrishti1701
Copy link
Contributor

I've been investigating the KeyError: 'sha256' failure in test_update. Here’s what I’ve found so far:

The error suggests that the 'sha256' key is missing in the expected response.

I checked the response structure, and it appears that 'sha256' is not always present.

Adding a safeguard (if 'sha256' in response:) prevents the error, but I need to confirm whether the absence of 'sha256' is expected or a deeper issue.

Running the test in isolation (pytest test/test_cli.py::TestCLI::test_update -v) produces the same failure, ruling out environment-related issues.

I'm also reviewing recent dependency updates and API changes that might have affected this.

Would you recommend handling this missing key as an expected case, or should I investigate why it’s absent in the first place?

@dus7eh
Copy link
dus7eh commented May 19, 2025 •
edited
Loading

Are there any updates on this issue?
Lately I started to get the "sha256" error more often when executing cve-bin-tool with -u now flag.
For me this happens with nvd database (with nvd api key). If I skip this database there is no problem.

@terriko
Copy link
Contributor Author
terriko commented May 19, 2025

Yeah, we're seeing it in our cache too at the moment. You may have better luck using an nvd_api_key and getting data direct from them; last time I think it was a mirror race condition that caused the signature mismatch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@terriko @dus7eh @Shrishti1701
0