Adrian Edwards

Thats what I was thinking, I just have to do it. And I suspect the code for it is buried somewhere in augurs various functions.

The above stack trace seems to be happening in the error handler for augur's celery tasks. The fact that it is still repo_url based is a different tech debt issue....

> This one appears ready. It largely is, however, I would like to also include a new database table alongside this fix so that, when the repo url gets updated,...

> seems to be a dependence on using the repo URL for querying: Ok so this was basically due to how the retry behavior in celery works. I think it...

OK this change now contains the new table and the code to populate it on move. Therefore it officially fixes #3129 :tada: I tested this with mild effort locally. I...

Maintainers call brought up the concern that, when github is redirecting the old url for a moved repo, another new (and different) repo can be created at the old url,...

part of me is a little worried about "use the src id for everything" since it is fundamentally a git-dependent value. I think it makes a ton of sense to...

> the src_id is not Git dependent ... each platform has their own integer identifier that follows a repository even if you change its URL. Do we know whether this...

Also, where does this conversion leave us as far as this PR? If we essentially write to the aliases table as if it is a log of each time a...

Thinking about this again, I think either framing has the same issue, but the difference is essentially who deals with it. It sounds like the possibility of the aliases table...