Describe the issue
In the failed-composes issue for today's Rawhide compose - https://pagure.io/releng/failed-composes/issue/4890 - the Koji task IDs are wrong. The same two task IDs are repeated several times - 10024485 and 10024486 . Both of those are old package builds that have nothing at all to do with the compose. The problem seems to be because we've rolled over into 9-digit task numbers now: the real task number for one of the tasks is 100244862 (note the extra '2' on the end). This would be a trivial fix, except I don't know where the code is - it'd be nice if https://pagure.io/releng/failed-composes/blob/main/f/README.md told you where the tool that produces the reports lives, so you can find it to fix problems in it. @dustymabe

When do you need this? (YYYY/MM/DD)
ASAP.

When is this no longer needed or useful? (YYYY/MM/DD)
When we stop doing composes.

If we cannot complete your request, what is the impact?
It's harder to debug compose issues.