Laura Barcziová

@mulkieran ah ok, I see, this is likely caused by https://github.com/packit/packit-service/issues/2669, I will try to get https://github.com/packit/packit-service/pull/2785 which fixes it into production this week.

Since the linked PR is in prod, I am closing this now.

hi! I would close this as a duplicate of https://github.com/packit/dashboard/issues/468 which covers the whole effort of filtering in our dashboard if that works with you.

hi! Could you please provide an example? I would like to see what is being linked. This might be likely related to Gitlab's behaviour where you can't update the pipeline...

> the issue is that status is "running" but there's no link to the in-progress job: Do you mean this is happenning consistently or just occassionaly? > Looking at the...

Thanks, I think I understand it a bit better now, so in usual builds+tests case, we link at least dashboard https://dashboard.packit.dev/jobs/testing-farm (what I wrote previously about linking the job itself...

This is currently low prio, but we could have a look while working on #1954.

I briefly looked into the code and I am thinking if it wouldn't be more fitting to have the logic for checking this in [this method](https://github.com/packit/packit-service/blob/e24583035cf6abb96559ee7586bd0127351aaba2/packit_service/worker/jobs.py#L849), which would mean it...

@LecrisUT can you elaborate more on what you are suggesting? I agree the code I linked could be refactored, but it is something different than the Checker's logic, as that...

@LecrisUT understood, thanks for the explanation! Yes, that sounds like it could improve the readability and extensibility.