While this is needed for testing, I don't think we want this committed :)

I've dropped that line

Shouldn't there be a link between model.Project and distgit.PagureBZOverride in the WHERE clause of the query?

Can you elaborate on what you mean by that ?

Well, you are using two tables in one query and from what I can read, there are no constraint between these two tables in the WHERE clause of your query.

I've pushed the following change:

• ).filter(
• model.Project.id == distgit.PagureBZOverride.project_id
  )

the path mangling crept in again, removed...

Likely not needed

To be tested but this looks fine at the moment.

Alright, so after local testing, this is not working, it only considered the project for which I have set an overrides, not the others, which makes sense considering the query we're running here.

that filter... I'll look into it

pls try again

Where is this being used?

So the current approach leads to results such as:

"criu": {
    "admin": "pingou",
    "epel": null,
    "fedora": "ralph"
},

Where epel is wrong, it should be pingou not null.

Also a better approach to this would be to do a join between the two tables, I guess an outer join (no certainty though, I always have to check which type of join is needed), which allow to do everything in one query as you had previously tried.

an outer join (left for example) + coalesce to select owner if assignee is null?

I need to read up on outer joints as that might be much faster. For now I've fixed the code to use the repo admin when the assignee is unset

You explode entry into multiple variables above and here you're going back to it :(

I'm pretty sure flake8 wants that line

I think I've already asked it: where is this used?

I think I've already asked it: where is this used?

At the very bottom, but there's another import sys. This line can and will go

You were right, flake wanted that empty line, along with some minor other fixes.

Did you try running the script?

I find it quite amusing that when I try to run your PR as you push it I keep running into:

AttributeError: module 'pagure_distgit.model' has no attribute 'PagureBZOverride'

Are you even running the script before you push your changes?

Yes, I run the script in vagrant and it succeeds:
(python3-pagure) [vagrant@pagure-dev pagure-dist-git]$ PAGURE_CONFIG=/home/vagrant/pagure.cfg PYTHONPATH=.:/home/vagrant/devel/ python3 scripts/pagure_poc.py /tmp/scriptoutput/

After that command there's a /tmp/scriptoutput/pagure_poc.json and its contents look ok

You need to run it with the other patch from https://pagure.io/pagure-dist-git/pull-request/82 in place, otherwise you'll see the "no attribute 'PagureBZOverride'" error

82 is merged, so could you rebase this pr to current master? Thanks :)

that's probably what Pierre meant with his comment, I just didn't get it ;-(
Rebased...

What's the status of this ?

It is still waiting on this comment: https://pagure.io/pagure-dist-git/pull-request/90#comment-105733

I'm looking at outer joints docs atm

I've also tried coalesce as suggested, but that fails when one of the assignees is set to an empty string instead of None. The current version works for both, '' and None. I don't think the current pagure-dist-git version will write '' into the db anymore, but this seems to be the save way to handle this special case.

:thumbsup:

Let's get this in, thanks for your work on all this! :)