I just adjusting this to if group and repo in group.projects instead :)

Anyhow, the code is going inside the for group in groups and the error comes from the projects attribute so wouldn't it be better a if group and group.projects and repo ?

I'll try to figure how can we test this during this weekend :)

The change itself looks good, I'm very curious about the test though (ie: how it got triggered :))

Can't reproduce this on a normal usage of pagure, just when I use dev-data.py -a so dunno how to proceed with it. Should I add tests against the weird dev-data.py db state? Does that worth it since it can not be reproduced using standard pagure workflows?

I think we should try to fix the dev-data script then :)

Note that we already test the dev-data script in the tests itself, so we could adjust this test to ensure the fix to dev-data does fix the situation.

I'm hitting this using fas backend too, so now it does not look as a dev-data problem :D

I'll return here someday :)

I found the real problem. We continue on https://pagure.io/pagure/pull-request/4679