[Question] What will happen in case of Code Rot

[Tailscale-VPS]

Using these options -

CLEANUP_DELETE_IF_NOT_IN_GITHUB=true
CLEANUP_ORPHANED_REPO_ACTION=delete

It will delete any repo not stared or forked in github, But what will happend let's say one day the owner of the repo deleted their repo.
In this case it will not be able to fine the repo on github also if there's no repo then no star logic also. Will it delete the repo from gitea also in that case?

[Tailscale-VPS]

Tested myself and it's as suspected , if the owner of the repo by any chance deletes the repo or its gets banned,etc u will loose your backup in gitea also.

So this is a reminder for other people also who are using

CLEANUP_DELETE_IF_NOT_IN_GITHUB=true
CLEANUP_ORPHANED_REPO_ACTION=delete

We need to use

CLEANUP_DELETE_IF_NOT_IN_GITHUB=true
CLEANUP_ORPHANED_REPO_ACTION=archive

@arunavo4 But when i tested the above i got this error

[Scheduler] Checking for orphaned repositories to cleanup for user HEip83zsQMqZ0Jb9pa0rMgmEXZdgg1Se...
[Scheduler] Found 1 orphaned repositories for cleanup
[Repository Cleanup] Archiving orphaned repository K11MCH1/AdrenoToolsDrivers in Gitea
Error archiving repository starred/AdrenoToolsDrivers: 1 | class HttpError extends Error {
2 |   constructor(message, status, statusText, response) {
3 |     super(message);
        ^
HttpError: HTTP 405: Method Not Allowed
     status: 405,
 statusText: "Method Not Allowed",
   response: "",
      at new HttpError (/app/dist/server/chunks/http-client_agXhlCmA.mjs:3:5)
      at httpRequest (/app/dist/server/chunks/http-client_agXhlCmA.mjs:46:13)
[Repository Cleanup] Error handling orphaned repository K11MCH1/AdrenoToolsDrivers: 1 | class HttpError extends Error {
2 |   constructor(message, status, statusText, response) {
3 |     super(message);
        ^
HttpError: HTTP 405: Method Not Allowed
     status: 405,
 statusText: "Method Not Allowed",
   response: "",
      at new HttpError (/app/dist/server/chunks/http-client_agXhlCmA.mjs:3:5)
      at httpRequest (/app/dist/server/chunks/http-client_agXhlCmA.mjs:46:13)
[Scheduler] Failed to handle orphaned repository K11MCH1/AdrenoToolsDrivers: 1 | class HttpError extends Error {
2 |   constructor(message, status, statusText, response) {
3 |     super(message);
        ^
HttpError: HTTP 405: Method Not Allowed
     status: 405,
 statusText: "Method Not Allowed",
   response: "",
      at new HttpError (/app/dist/server/chunks/http-client_agXhlCmA.mjs:3:5)
      at httpRequest (/app/dist/server/chunks/http-client_agXhlCmA.mjs:46:13)
[Scheduler] No repositories to sync for user HEip83zsQMqZ0Jb9pa0rMgmEXZdgg1Se
Job 645f439c-f4bd-4942-a45a-a3ca4a84c063 has no log data
Job 1de67863-5754-47b3-8bac-34e1772b95fc has no log data
[Scheduler] Processing 1 configurations with scheduling enabled (out of 1 total active configs)
[Scheduler] Skipping user HEip83zsQMqZ0Jb9pa0rMgmEXZdgg1Se - next run at 2025-08-30T05:52:10.470Z
[Scheduler] Processing 1 configurations with scheduling enabled (out of 1 total active configs)
[Scheduler] Skipping user HEip83zsQMqZ0Jb9pa0rMgmEXZdgg1Se - next run at 2025-08-30T05:52:10.470Z

[arunavo4]

@Tailscale-VPS Thank you for testing this senario. You have been a huge help testing out this app. I will work on this next week.

[Tailscale-VPS]

@Tailscale-VPS Thank you for testing this senario. You have been a huge help testing out this app. I will work on this next week.

No problem, take your time.
It's my pleasure, I'm not a coder but being tester and suggestor is the least i can do to contribute to this fantastic app.

[arunavo4]

@Tailscale-VPS Hi please try out v3.5.2

[Tailscale-VPS]

@arunavo4 Tested v3.5.3 and found this -

• Ignore the not found error that was because it's not mirrored.

[Scheduler] Found 2 orphaned repositories for cleanup
[Repository Cleanup] Archiving orphaned repository Tailscale-VPS/test in Gitea
[Archive] Could not mark repository Tailscale-VPS/test as archived: 1 | class HttpError extends Error {
2 |   constructor(message, status, statusText, response) {
3 |     super(message);
        ^
HttpError: HTTP 404: GetUserByName
     status: 404,
 statusText: "Not Found",
   response: "{\"errors\":[\"user redirect does not exist [name: tailscale-vps]\"],\"message\":\"GetUserByName\",\"url\":\"https://mirror.example.com/api/swagger\"}\n",
      at new HttpError (/app/dist/server/chunks/http-client_BsveYDLl.mjs:3:5)
      at httpRequest (/app/dist/server/chunks/http-client_BsveYDLl.mjs:46:13)
[Archive] Repository Tailscale-VPS/test data is preserved but not marked as archived
Publishing event to channel repository for user ZqeM8j8ax988V1Cvku1SxDrdHcBHEju7
Event published successfully with ID c211c68c-cb29-400f-b13a-26ea7b53a163
[Scheduler] Handled orphaned repository: Tailscale-VPS/test

[Repository Cleanup] Archiving orphaned repository Tailscale-VPS/test in Gitea
[Archive] Repository starred/test is a mirror. Using safe rename strategy.
[Archive] Repository starred/test data is preserved but not marked as archived
[Archive] Could not mark repository starred/test as archived: 1 | class HttpError extends Error {
2 |   constructor(message, status, statusText, response) {
3 |     super(message);
        ^
HttpError: HTTP 422: [Name]: AlphaDashDot
     status: 422,
 statusText: "Unprocessable Entity",
   response: "{\"message\":\"[Name]: AlphaDashDot\",\"url\":\"https://mirror.example.com/api/swagger\"}\n",
      at new HttpError (/app/dist/server/chunks/http-client_BsveYDLl.mjs:3:5)
      at httpRequest (/app/dist/server/chunks/http-client_BsveYDLl.mjs:46:13)
Publishing event to channel repository for user ZqeM8j8ax988V1Cvku1SxDrdHcBHEju7
Event published successfully with ID 8c5b87a9-d240-4d19-9e13-048dcd49bfda
[Scheduler] Handled orphaned repository: Tailscale-VPS/test

• After it has tried to archive the repo, when loading the Repo section on the Web UI it's blank and giving Internal server error.

Error in repositories fetch: ZodError: [
  {
    "code": "invalid_value",
    "values": [
      "imported",
      "mirroring",
      "mirrored",
      "failed",
      "skipped",
      "ignored",
      "deleting",
      "deleted",
      "syncing",
      "synced"
    ],
    "path": [],
    "message": "Invalid option: expected one of \"imported\"|\"mirroring\"|\"mirrored\"|\"failed\"|\"skipped\"|\"ignored\"|\"deleting\"|\"deleted\"|\"syncing\"|\"synced\""
  }
]

[arunavo4]

@Tailscale-VPS Can you try v3.7.1 I have added a few things that should help.

[Tailscale-VPS]

@arunavo4 Tested v3.7.1

• Archiving is fixed, haven't tested deleting but i believe it was working fine before so it should work.

New issue

• When a repo is archived, on next sync it's keep's getting renamed again and again

[Scheduler] Next sync for user c1eVoDrsZ4eu3ppaGqb1NyJ4LJeS7Vpt scheduled for: 2025-09-14T03:49:40.225Z (in 7m)
[Scheduler] Checking for new GitHub repositories for user c1eVoDrsZ4eu3ppaGqb1NyJ4LJeS7Vpt...
[Scheduler] No new repositories found for user c1eVoDrsZ4eu3ppaGqb1NyJ4LJeS7Vpt
[Scheduler] Checking for orphaned repositories to cleanup for user c1eVoDrsZ4eu3ppaGqb1NyJ4LJeS7Vpt...
GET /user/repos?per_page=100 - 200 with id 85B6:278085:7DCC07:A82188:68C639B0 in 386ms
GET /user/starred?per_page=100 - 200 with id 85B0:1E043F:7BEEE4:A645BA:68C639B0 in 394ms
[Repository Cleanup] Found 1 orphaned repositories for user c1eVoDrsZ4eu3ppaGqb1NyJ4LJeS7Vpt
[Scheduler] Found 1 orphaned repositories for cleanup
[Repository Cleanup] Archiving orphaned repository brunodev85/winlator in Gitea
Repository found at recorded mirrored location: starred/winlator-brunodev85-1
[Archive] Repository starred/winlator-brunodev85-1 is a mirror. Using safe rename strategy.
[Archive] Successfully marked mirror repository starred/winlator-brunodev85-1 as archived (renamed to archived-winlator-brunodev85-1)
[Archive] Reduced sync frequency for starred/archived-winlator-brunodev85-1 to yearly
Publishing event to channel repository for user c1eVoDrsZ4eu3ppaGqb1NyJ4LJeS7Vpt


[Repository Cleanup] Found 2 orphaned repositories for user c1eVoDrsZ4eu3ppaGqb1NyJ4LJeS7Vpt
[Scheduler] Found 2 orphaned repositories for cleanup
[Repository Cleanup] Archiving orphaned repository Tailscale-VPS/test in Gitea
[Archive] Repository starred/test-Tailscale-VPS-3 is a mirror. Using safe rename strategy.
[Archive] Successfully marked mirror repository starred/test-Tailscale-VPS-3 as archived (renamed to archived-test-Tailscale-VPS-3)
[Archive] Reduced sync frequency for starred/archived-test-Tailscale-VPS-3 to yearly
Publishing event to channel repository for user c1eVoDrsZ4eu3ppaGqb1NyJ4LJeS7Vpt
Event published successfully with ID 03f14217-0f79-4ee5-adee-c4b62d17bf20


[Scheduler] Found 2 orphaned repositories for cleanup
[Repository Cleanup] Archiving orphaned repository Tailscale-VPS/test in Gitea
[Archive] Repository starred/test-Tailscale-VPS-3 is a mirror. Using safe rename strategy.
[Archive] Successfully marked mirror repository starred/test-Tailscale-VPS-3 as archived (renamed to archived-archived-test-Tailscale-VPS-3)
[Archive] Reduced sync frequency for starred/archived-archived-test-Tailscale-VPS-3 to yearly
Publishing event to channel repository for user c1eVoDrsZ4eu3ppaGqb1NyJ4LJeS7Vpt
Event published successfully with ID af979d48-81e2-4de4-b95a-605b2320297c
[Scheduler] Handled orphaned repository: Tailscale-VPS/test
[Repository Cleanup] Archiving orphaned repository brunodev85/winlator in Gitea
[Archive] Repository starred/winlator-brunodev85-1 is a mirror. Using safe rename strategy.
[Archive] Successfully marked mirror repository starred/winlator-brunodev85-1 as archived (renamed to archived-archived-archived-archived-winlator-brunodev85-1)
[Archive] Reduced sync frequency for starred/archived-archived-archived-archived-winlator-brunodev85-1 to yearly
Publishing event to channel repository for user c1eVoDrsZ4eu3ppaGqb1NyJ4LJeS7Vpt

Sync Time interval
When a repo is archived its sync frequency is reduced to yearly (1y), it's a good workarround for now , but i believe it can cause issues when the time of sync will come (assuming the owner has deleted the github repo/code rot)
What we can do -

• We can stop syncing of archived repo completely (This is preferred as you have already added a description for the archived repo in gitea)
• Increase the sync time exponentially, for eg, lets say after 1y when the time comes for the sync the app could not found the github repo , so it will just increase the sync time of gitea repo to 2y or 5y,etc

[arunavo4]

@Tailscale-VPS whats the original name of the repo?

I think for archived repo stop sync and have the ability to manually start syncing would be best

[Tailscale-VPS]

@arunavo4 The original name was test, but for the above it's test-Tailscale-VPS-3
Because when i recreated the container for clean setup i havent deleted the repos from gitea (Will be opening a new issue later ,found something about minimum sync interval should be > 5min, else it will fail and make unwanted repos in gitea)

• The idea of manually start syncing seems be best.