Weird repositories on my try.gitea.io organization #351

Closed
opened 2025-11-02 03:19:48 -06:00 by GiteaMirror · 10 comments
Owner

Originally created by @kybin on GitHub (Feb 14, 2017).

Originally assigned to: @lunny on GitHub.

  • Gitea version (or commit ref): try.gitea.io
  • Git version:
  • Operating system:
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist:

Description

Hello, I created a organization long time ago in try.gitea.io

Today I see many repositories in my organization dash board that doesn't actually exist. Please see https://try.gitea.io/org/di/dashboard

Another wierd thing is I can see many issues in https://try.gitea.io/org/di/issues .
But when I click the link it send me another repositories, those are not relavant with di organization. The PR section acts exactly same.

Please take a look.

Originally created by @kybin on GitHub (Feb 14, 2017). Originally assigned to: @lunny on GitHub. - Gitea version (or commit ref): try.gitea.io - Git version: - Operating system: - Database (use `[x]`): - [ ] PostgreSQL - [ ] MySQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [x] Yes (provide example URL) - [ ] No - [ ] Not relevant - Log gist: ## Description Hello, I created a organization long time ago in try.gitea.io Today I see many repositories in my organization dash board that doesn't actually exist. Please see https://try.gitea.io/org/di/dashboard Another wierd thing is I can see many issues in https://try.gitea.io/org/di/issues . But when I click the link it send me another repositories, those are not relavant with di organization. The PR section acts exactly same. Please take a look.
GiteaMirror added the issue/criticaltype/bug labels 2025-11-02 03:19:48 -06:00
Author
Owner

@lunny commented on GitHub (Feb 14, 2017):

#933 only reosolved dashboard problem. Not resolved https://try.gitea.io/org/di/issues

@lunny commented on GitHub (Feb 14, 2017): #933 only reosolved dashboard problem. Not resolved https://try.gitea.io/org/di/issues
Author
Owner

@lunny commented on GitHub (Feb 15, 2017):

It's still not resolved completely.

@lunny commented on GitHub (Feb 15, 2017): It's still not resolved completely.
Author
Owner

@lunny commented on GitHub (Feb 15, 2017):

I'm working on this.

@lunny commented on GitHub (Feb 15, 2017): I'm working on this.
Author
Owner

@lunny commented on GitHub (Feb 17, 2017):

@kybin Please confirm #943 has resolved this.

@lunny commented on GitHub (Feb 17, 2017): @kybin Please confirm #943 has resolved this.
Author
Owner

@lunny commented on GitHub (Feb 17, 2017):

No. try.gitea.io is not updated to 847527f yet. current is 140967f0. Maybe you can confirm it after a while.

@lunny commented on GitHub (Feb 17, 2017): No. try.gitea.io is not updated to 847527f yet. current is 140967f0. Maybe you can confirm it after a while.
Author
Owner

@kybin commented on GitHub (Feb 17, 2017):

Ah, ok. I didn't catch that.

I deleted the previous post.

@kybin commented on GitHub (Feb 17, 2017): Ah, ok. I didn't catch that. I deleted the previous post.
Author
Owner

@lunny commented on GitHub (Feb 18, 2017):

Now it's the newest version and I think it should be fixed.

@lunny commented on GitHub (Feb 18, 2017): Now it's the newest version and I think it should be fixed.
Author
Owner

@kybin commented on GitHub (Feb 19, 2017):

Seems try.gitea.io is down. So I can't test it.

@kybin commented on GitHub (Feb 19, 2017): Seems try.gitea.io is down. So I can't test it.
Author
Owner

@tboerger commented on GitHub (Feb 19, 2017):

Seems try.gitea.io is down. So I can't test it.

This have been a different issue, everything is up and running.

@tboerger commented on GitHub (Feb 19, 2017): > Seems try.gitea.io is down. So I can't test it. This have been a different issue, everything is up and running.
Author
Owner

@kybin commented on GitHub (Feb 19, 2017):

Yes, it's fixed now. Thank you for the effort!

@kybin commented on GitHub (Feb 19, 2017): Yes, it's fixed now. Thank you for the effort!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#351