-
Notifications
You must be signed in to change notification settings - Fork 9
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
download specs for koji scratch builds #99
Conversation
from their SRPMs - this reintroduces the codebase originally written by @nikromen, hence the co-authorship If fetching of a spec file fails, return None instead of erroring out. We want to have the annotated snippets and can live if a few don't have spec files. Fixes fedora-copr#98 Co-authored-by: Jiri Kyjovsky <[email protected]> Signed-off-by: Tomas Tomecek <[email protected]>
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 🎸
), | ||
status_code=HTTPStatus.BAD_REQUEST, | ||
) | ||
# since we require arch in the input, we can check if the task matches it |
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.
I think the initial idea of arch here was when the user gives us arch and task ID with children, we could go to the specific child. But it somehow disappeared into the thin air. And also I am not sure if it would work :D
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.
you're right, we do that when the ID is build-id
but once they provide task id, we now require it to be the buildArch (or SCM) task so we can get the logs and spec right away
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.
though we don't accept the parent task right now :/ #97
) | ||
# since we require arch in the input, we can check if the task matches it | ||
# but I think it's not a good UX, if the user gives us task ID, let's just use it | ||
# if someone complains about, just reintroduce the if below |
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.
+1
@nikromen thank you for the review!! merging |
from their SRPMs - this reintroduces the codebase
originally written by @nikromen, hence the co-authorship
If fetching of a spec file fails, return None instead of erroring out.
We want to have the annotated snippets and can live if a few don't have
spec files.
Fixes #98