Adrian Edwards

@shlokgilda problem: looking into the gh-login table duplication in our instance, im noticing that, at least for this random user i picked, it seems to actually be two separate users...

> 3\. Separate the concerns - the `gh_*` columns are clearly meant for GitHub data, but if GitLab data is being stuffed in there too, that's a schema design issue...

Another problem: the `fk_commits_contributors_3` Foreign Key depends on `cntrb_login` being unique. I dont see an easy way to remove this FK cleanly, but we clearly cannot keep it because it...

ok next issue: foreign key loop in the SPDX schema between package.package_id and package_files seems like that may be just a warning though. seems interesting that alembic is generating an...

ok so that field needs to be an FK apparrently Stack Trace ``` INFO [alembic.runtime.migration] Context impl PostgresqlImpl. augur-1 | INFO [alembic.runtime.migration] Will assume transactional DDL. augur-1 | INFO [alembic.runtime.migration]...

> * to persist BadgingDEI records > DEI endpoints (`dei_track_repo`, `dei_report`) should be manually tested (although I don't think these are even used?) i think that table is unused and...

@shlokgilda are there tests to confirm that the core of this change does in fact leak fewer connections?

This already has a PR linked to it, meaning someone else has already worked on a solution. Feel free to join the [CHAOSS Slack](https://chaoss.community/kb-getting-started/) in the #wg-augur-8knot channel if you'd...

@sgoggins does this match the issues you have observed on bare metal main branch? if not please file a new issue for it. i really want to debug that ASAP

> Side note on the `.gitconfig error`: The `could not lock config file /augur/.gitconfig: Permission denied` error in the logs looks like a separate issue - looks like a container...