-
Notifications
You must be signed in to change notification settings - Fork 24
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
Checker: Fix checking of missing files #441
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Code looks good, BUT I have a problem while testing. Using the example data from the standard
results in ...
{
"type": 2,
"text": "Fetching https://127.0.0.1/.well-known/csaf/2020/example_company_-_2020-yh4711.json failed: Status code 404 (404 Not Found)"
},
... Which is a result OK. But there seems to be no complaint that this isn't found in any ROLIE or some similar message (which should be according to @JanHoefelmeyer ). More: Using
results in {
"type": 2,
"text": "Fetching https://127.0.0.1/.well-known/csaf/2019/rhsa-2019_1862.json failed: Status code 404 (404 Not Found)"
},
...
{
"type": 2,
"text": "https://localhost:8443/.well-known/csaf/amber/2019/rhsa-2019_1862.json in ROLIE, not in changes.csv"
},
{ which seems to be confusing. Going one step further: Using
results in: {
"type": 2,
"text": "https://localhost:8443/.well-known/csaf/amber/2019/rhsa-2019_1862.json in ROLIE, not in changes.csv"
}, which is confusing.
Am I testing wrong here or is there a bug hidden? Aside: The date part seems to be neglectable as long a date is present in an entry. |
Okay using
which should read
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM and using URLs it works.
Jan mentioned yesterday there is something wrong with this he still wants to fix. I currently do not know any more details. Postponing merge ATM. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@JanHoefelmeyer please fix what you have planned to fix.
(I have added a review so that merging is blocked until @JanHoefelmeyer can do his fixes next week.) |
The "right" way to prevent this is to set it back to draft. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Still LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM & Works
No actual changes requested.
Part of #438
Currently, any file discrepancies between the different file retrieval methods is reported in integrity.
This PR changes the checker so it reports any file missing from a list in their respective retrieval methods Requirement