-
Notifications
You must be signed in to change notification settings - Fork 48
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
Bodhi update fixes #2596
Bodhi update fixes #2596
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
Build succeeded. ✔️ pre-commit SUCCESS in 2m 11s |
cls, | ||
koji_nvrs: str, | ||
) -> set["BodhiUpdateTargetModel"]: | ||
regexp = "|".join(re.escape(nvr) for nvr in set(koji_nvrs.split())) |
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.
👀 What could go wrong :D
session.query(BodhiUpdateTargetModel) | ||
.filter( | ||
BodhiUpdateTargetModel.status.in_(("queued", "retry", "success")), | ||
BodhiUpdateTargetModel.koji_nvrs.regexp_match(regexp).compile( |
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.
Does this actually precompile?
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.
Not sure, I followed an example from the documentation.
Signed-off-by: Nikola Forró <[email protected]>
…date Signed-off-by: Nikola Forró <[email protected]>
Signed-off-by: Nikola Forró <[email protected]>
Build succeeded. ✔️ pre-commit SUCCESS in 2m 17s |
Build succeeded (gate pipeline). ✔️ pre-commit SUCCESS in 2m 05s |
23bc167
into
packit:main
…2609) Make sure `bodhi_update` job runs don't get stuck in `queued` state When an unhandled exception occurs, a Sentry issue is created but the job run stays in queued state, which breaks the condition that is supposed to prevent submitting the same update more than once, as it considers that job run to be in progress. Make sure the state is updated when that happens. Question is, in such case should the exception and traceback be stored and issue with it created in the issue repository or do we consider that internal? Related to #2596. Reviewed-by: Matej Focko Reviewed-by: Laura Barcziová Reviewed-by: Nikola Forró
Fixes #2573.