github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-09 12:46:42 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

After upgrading, repositories without an issuetracker can not be accessed. #1093

New Issue
Closed
opened 2025-11-02 03:48:15 -06:00 by GiteaMirror · 12 comments
GiteaMirror commented 2025-11-02 03:48:15 -06:00
Owner
Copy Link

Originally created by @iamnumbersix on GitHub (Sep 24, 2017).

  • Gitea version (or commit ref): 1.2.0+rc3
  • Git version: 2.11.0
  • Operating system: Linux Debian 9.1 kernel 4.9.0-3-amd64
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist:
    routers/repo/view.go:274 Home()] [E] Home: Cannot find any unit on this repository which you are allowed to access

Description

After upgrading from 1.1.4 to the release candidate (1.2.0+rc3), repositories without an issue tracker can not be accessed. You will get a 404 error, Page can not be found.

Switching back to 1.1.4 and enabling the internal issue tracker for that repository and switching again to 1.2.0+rc3 version, the repository is accessible again.

After disabling the issue tracker in 1.2.0+rc3 it is still accessible.
It stays accessible after switching back to 1.1.4 and 1.2.0+rc3 again.

This has been the case for rc1 and rc2 too.

Originally created by @iamnumbersix on GitHub (Sep 24, 2017). <!-- 1. Please speak English, this is the language all of us can speak and write. 2. Please ask questions or configuration/deploy problems on our Discord server (https://discord.gg/NsatcWJ) or forum (https://discourse.gitea.io). 3. Please take a moment to check that your issue doesn't already exist. 4. Please give all relevant information below for bug reports, because incomplete details will be handled as an invalid report. --> - Gitea version (or commit ref): 1.2.0+rc3 - Git version: 2.11.0 - Operating system: Linux Debian 9.1 kernel 4.9.0-3-amd64 - Database (use `[x]`): - [ ] PostgreSQL - [ ] MySQL - [ ] MSSQL - [x] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [x] Not relevant - Log gist: routers/repo/view.go:274 Home()] [E] Home: Cannot find any unit on this repository which you are allowed to access ## Description After upgrading from 1.1.4 to the release candidate (1.2.0+rc3), repositories without an issue tracker can not be accessed. You will get a 404 error, Page can not be found. Switching back to 1.1.4 and enabling the internal issue tracker for that repository and switching again to 1.2.0+rc3 version, the repository is accessible again. After disabling the issue tracker in 1.2.0+rc3 it is still accessible. It stays accessible after switching back to 1.1.4 and 1.2.0+rc3 again. This has been the case for rc1 and rc2 too.
GiteaMirror added the issue/criticaltype/bug labels 2025-11-02 03:48:15 -06:00
GiteaMirror commented 2025-11-02 03:48:16 -06:00
Author
Owner
Copy Link

@daviian commented on GitHub (Sep 25, 2017):

@iamnumbersix Does this issue happen to all types of repositories (private, public, repositories from organizations)?

@daviian commented on GitHub (Sep 25, 2017): @iamnumbersix Does this issue happen to all types of repositories (private, public, repositories from organizations)?
GiteaMirror commented 2025-11-02 03:48:17 -06:00
Author
Owner
Copy Link

@lafriks commented on GitHub (Sep 25, 2017):

I think it could be related to #1794

@lafriks commented on GitHub (Sep 25, 2017): I think it could be related to #1794
GiteaMirror commented 2025-11-02 03:48:17 -06:00
Author
Owner
Copy Link

@daviian commented on GitHub (Sep 25, 2017):

@iamnumbersix Can you please test my fix in PR #2600

@daviian commented on GitHub (Sep 25, 2017): @iamnumbersix Can you please test my fix in PR #2600
GiteaMirror commented 2025-11-02 03:48:17 -06:00
Author
Owner
Copy Link

@daviian commented on GitHub (Sep 25, 2017):

@iamnumbersix Are you sure it is because of a disabled issue tracker? Could there be anything else they have in common?

@daviian commented on GitHub (Sep 25, 2017): @iamnumbersix Are you sure it is because of a disabled issue tracker? Could there be anything else they have in common?
GiteaMirror commented 2025-11-02 03:48:17 -06:00
Author
Owner
Copy Link

@iamnumbersix commented on GitHub (Sep 25, 2017):

Can you please test my fix in PR #2600

I'm sorry, I don't have go installed, I only use the binaries

Are you sure it is because of a disabled issue tracker? Could there be anything else they have in common?

maybe...
I'm the owner of the repositories and after I enable the issue tracker, it is available again.
The repositories are private and have been previously imported in gogs.
I've been running gitea from the first version.

@iamnumbersix commented on GitHub (Sep 25, 2017): > Can you please test my fix in PR #2600 I'm sorry, I don't have go installed, I only use the binaries >Are you sure it is because of a disabled issue tracker? Could there be anything else they have in common? maybe... I'm the owner of the repositories and after I enable the issue tracker, it is available again. The repositories are private and have been previously imported in gogs. I've been running gitea from the first version.
GiteaMirror commented 2025-11-02 03:48:17 -06:00
Author
Owner
Copy Link

@iamnumbersix commented on GitHub (Sep 25, 2017):

I ran the sqlite commands in #1794
https://github.com/go-gitea/gitea/issues/1794#issuecomment-316824479

And that fixed it!
Hooray!

@iamnumbersix commented on GitHub (Sep 25, 2017): I ran the sqlite commands in #1794 https://github.com/go-gitea/gitea/issues/1794#issuecomment-316824479 And that fixed it! Hooray!
GiteaMirror commented 2025-11-02 03:48:18 -06:00
Author
Owner
Copy Link

@daviian commented on GitHub (Sep 25, 2017):

Did you upgrade from gogs?

@daviian commented on GitHub (Sep 25, 2017): Did you upgrade from gogs?
GiteaMirror commented 2025-11-02 03:48:18 -06:00
Author
Owner
Copy Link

@iamnumbersix commented on GitHub (Sep 25, 2017):

Yes, I did upgrade from gogs

@iamnumbersix commented on GitHub (Sep 25, 2017): Yes, I did upgrade from gogs
GiteaMirror commented 2025-11-02 03:48:18 -06:00
Author
Owner
Copy Link

@daviian commented on GitHub (Sep 25, 2017):

From which version of gogs to which version of gitea?

@daviian commented on GitHub (Sep 25, 2017): From which version of gogs to which version of gitea?
GiteaMirror commented 2025-11-02 03:48:18 -06:00
Author
Owner
Copy Link

@iamnumbersix commented on GitHub (Sep 25, 2017):

I think from gogs_v0.9.97_linux_amd64 to gitea-1.1.0-linux-amd64
(those where still in my download folder)
The date was about 30-april-2017.

But as I said, #1794 is likely the bug and the solution provided worked.

@iamnumbersix commented on GitHub (Sep 25, 2017): I think from gogs_v0.9.97_linux_amd64 to gitea-1.1.0-linux-amd64 (those where still in my download folder) The date was about 30-april-2017. But as I said, #1794 is likely the bug and the solution provided worked.
GiteaMirror commented 2025-11-02 03:48:18 -06:00
Author
Owner
Copy Link

@daviian commented on GitHub (Sep 25, 2017):

I needed verification to be sure ;-)

@daviian commented on GitHub (Sep 25, 2017): I needed verification to be sure ;-)
GiteaMirror commented 2025-11-02 03:48:19 -06:00
Author
Owner
Copy Link

@iamnumbersix commented on GitHub (Sep 25, 2017):

Thanks for all your help.

#1794 is likely describing the bug and the solution provided worked.

@iamnumbersix commented on GitHub (Sep 25, 2017): Thanks for all your help. #1794 is likely describing the bug and the solution provided worked.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label issue/critical type/bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#1093
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?