Core:detect_github_repo_move_core error on repos that have been deleted

Open Beginner friendly
#85 13 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
github, python
Domain
backend

Research direction

Read augur/tasks/github/detect_move/tasks.py and augur/tasks/github/detect_move/core.py, starting at detect_github_repo_move_core and ping_github_for_repo_move. Use the deleted repository example and traceback to trace the 404 path. Done means deleted repositories no longer produce the unhandled error and the existing move-detection behavior remains intact.

Written by the indexing model from the issue text.

Description

API database documentation

[!NOTE]
Migrated from augurlabs/augur#3166
Originally opened by @cdolfi on 2025-06-03

Error handling needed for repositories that have been deleted

Example: https://github.com/anaconda-platform/transformers-feedstock

Exception('ERROR: Repo has moved, and there is no redirection! 404 returned, not 301. Resetting Collection!')

Traceback (most recent call last): 
    File "/opt/venv/lib/python3.9/site-packages/celery/app/trace.py", line 451, in trace_task
        R = retval = fun(*args, **kwargs)  
    File "/opt/venv/lib/python3.9/site-packages/celery/app/trace.py", line 734, in __protected_call__
        return self.run(*args, **kwargs)  
    File "/augur/augur/tasks/github/detect_move/tasks.py", line 27, in detect_github_repo_move_core
        ping_github_for_repo_move(session, key_auth, repo, logger)  
    File "/augur/augur/tasks/github/detect_move/core.py", line 118, in ping_github_for_repo_move
        raise Exception("ERROR: Repo has moved, and there is no redirection! 404 returned, not 301. Resetting Collection!") 
Exception: ERROR: Repo has moved, and there is no redirection! 404 returned, not 301. Resetting Collection!
Dominant language
Python
Stars
14
Forks
18
Avg merge
3h 31m
Merged PRs (30d)
2

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from chaoss/CollectOSS

All issues in chaoss/CollectOSS

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.