Conversation
|
@ziadhany please rebase your branch and add tests for oss-fuzz |
I think we need to add Git Version/Version range aboutcode-org/univers#85 before merge this . |
|
@ziadhany does this importer only give |
Most of the data uses the git version, and there are rare cases that use both versions like this : https://github.com/google/oss-fuzz-vulns/search?p=1&q=fixed |
|
@ziadhany let's ingest the data where we can get versions that are parsable by univers for now and add a follow up issue to ingest git versions from OSS-Fuzz. |
|
@ziadhany please run the importer and improver on this and provide the logs for same. |
A lot of logs like this and the importer add just 2617 row in vulnerabilities_advisory table . And the improve logs : |
|
@ziadhany please add tests |
ce96986 to
1f75c02
Compare
|
@TG1999 |
| @@ -0,0 +1,20 @@ | |||
| { | |||
There was a problem hiding this comment.
Please rename these expected files to use the same base name as a the test data file with an -expected.json suffix. Here do not use oss-fuzz-expected1.json. Instead use oss-fuzz-data1.yaml-expected.json .... ths way the test data file and the expected results show up side by side.
pombredanne
left a comment
There was a problem hiding this comment.
LGTM with a tiny nit for the test results expected file names
|
@ziadhany thanks++ this looks good and we can merge it, please just resolve the merge conflicts. |
Add OSSFuzzImprover to IMPROVERS_REGISTRY Fix oss-fuzz test ( add weakness in expected test file ) Add oss-fuzz tests Import data from oss_fuzz using osv format Resolve merge conflicts Signed-off-by: ziadhany <ziadhany2016@gmail.com>
Done |
using osv format #780 but we need to add support for oss-fuzz version , version range in univers and edit
get_fixed_version