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

500 Error After Clicking A Repo Link #7710

New Issue
Closed
opened 2025-11-02 07:34:16 -06:00 by GiteaMirror · 9 comments
GiteaMirror commented 2025-11-02 07:34:16 -06:00
Owner
Copy Link

Originally created by @vw98075 on GitHub (Aug 19, 2021).

  • Gitea version (or commit ref):1.15.0+rc3-10-g25437672b
  • Git version:Go1.16.5
  • Operating system:MacOS
  • Database (use [x]):
    • [ x] PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
  • Log gist:
2021/08/18 17:24:12 Completed GET /user/events 200 OK in 3.363537959s
2021/08/18 17:24:12 Started GET /tk-shoreline/java-code-templete for [::1]:50329
2021/08/18 17:24:12 ...ules/context/repo.go:531:RepoAssignment() [E] RepoAssignment Invalid repo /Users/vewu/Documents/workspace/gitea-1.15/gitea/data/gitea-repositories/tk-shoreline/java-code-templete.git: no such file or directory
2021/08/18 17:24:12 Completed GET /tk-shoreline/java-code-templete 500 Internal Server Error in 8.093535ms
2021/08/18 17:24:12 Started GET /avatar/d6022cd695c8f486ea116a9cd2d17727?size=96 for [::1]:50329
2021/08/18 17:24:12 Completed GET /avatar/d6022cd695c8f486ea116a9cd2d17727?size=96 302 Found in 1.544404ms

Description

Clicking any repo on Gitea will lead to the 500 error.

This installation is with an existing PostgreSQL DB. I don't know whether that is the cause or not.

Screenshots

Screen Shot 2021-08-18 at 4 23 21 PM
Originally created by @vw98075 on GitHub (Aug 19, 2021). <!-- NOTE: If your issue is a security concern, please send an email to security@gitea.io instead of opening a public issue --> <!-- 1. Please speak English, this is the language all maintainers can speak and write. 2. Please ask questions or configuration/deploy problems on our Discord server (https://discord.gg/gitea) or forum (https://discourse.gitea.io). 3. Please take a moment to check that your issue doesn't already exist. 4. Make sure it's not mentioned in the FAQ (https://docs.gitea.io/en-us/faq) 5. 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.15.0+rc3-10-g25437672b - Git version:Go1.16.5 - Operating system:MacOS <!-- Please include information on whether you built gitea yourself, used one of our downloads or are using some other package --> <!-- Please also tell us how you are running gitea, e.g. if it is being run from docker, a command-line, systemd etc. ---> <!-- If you are using a package or systemd tell us what distribution you are using --> - Database (use `[x]`): - [ x] PostgreSQL - [ ] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - Log gist: <!-- It really is important to provide pertinent logs --> <!-- Please read https://docs.gitea.io/en-us/logging-configuration/#debugging-problems --> <!-- In addition, if your problem relates to git commands set `RUN_MODE=dev` at the top of app.ini --> ``` 2021/08/18 17:24:12 Completed GET /user/events 200 OK in 3.363537959s 2021/08/18 17:24:12 Started GET /tk-shoreline/java-code-templete for [::1]:50329 2021/08/18 17:24:12 ...ules/context/repo.go:531:RepoAssignment() [E] RepoAssignment Invalid repo /Users/vewu/Documents/workspace/gitea-1.15/gitea/data/gitea-repositories/tk-shoreline/java-code-templete.git: no such file or directory 2021/08/18 17:24:12 Completed GET /tk-shoreline/java-code-templete 500 Internal Server Error in 8.093535ms 2021/08/18 17:24:12 Started GET /avatar/d6022cd695c8f486ea116a9cd2d17727?size=96 for [::1]:50329 2021/08/18 17:24:12 Completed GET /avatar/d6022cd695c8f486ea116a9cd2d17727?size=96 302 Found in 1.544404ms ``` ## Description <!-- If using a proxy or a CDN (e.g. CloudFlare) in front of gitea, please disable the proxy/CDN fully and connect to gitea directly to confirm the issue still persists without those services. --> Clicking any repo on Gitea will lead to the 500 error. This installation is with an existing PostgreSQL DB. I don't know whether that is the cause or not. ## Screenshots <!-- **If this issue involves the Web Interface, please include a screenshot** --> <img width="732" alt="Screen Shot 2021-08-18 at 4 23 21 PM" src="https://user-images.githubusercontent.com/10793038/129988966-57d5f709-8b8d-44f4-9040-0c6dbb88d8d3.png">
GiteaMirror added the issue/needs-feedback label 2025-11-02 07:34:16 -06:00
GiteaMirror commented 2025-11-02 07:34:17 -06:00
Author
Owner
Copy Link

@techknowlogick commented on GitHub (Aug 19, 2021):

The error you are getting is 2021/08/18 17:24:12 ...ules/context/repo.go:531:RepoAssignment() [E] RepoAssignment Invalid repo /Users/vewu/Documents/workspace/gitea-1.15/gitea/data/gitea-repositories/tk-shoreline/java-code-templete.git: no such file or directory are you able to confirm that directory indeed does exist?

@techknowlogick commented on GitHub (Aug 19, 2021): The error you are getting is `2021/08/18 17:24:12 ...ules/context/repo.go:531:RepoAssignment() [E] RepoAssignment Invalid repo /Users/vewu/Documents/workspace/gitea-1.15/gitea/data/gitea-repositories/tk-shoreline/java-code-templete.git: no such file or directory` are you able to confirm that directory indeed does exist?
GiteaMirror commented 2025-11-02 07:34:17 -06:00
Author
Owner
Copy Link

@vw98075 commented on GitHub (Aug 19, 2021):

I posted the ticket right before I was off. I didn't look error messages in details. I certainly didn't expect that the running time data is stored in a local file system. I don't know how Gitea would run in the cloud if docker containers keep swapping unless using docker volume.

@vw98075 commented on GitHub (Aug 19, 2021): I posted the ticket right before I was off. I didn't look error messages in details. I certainly didn't expect that the running time data is stored in a local file system. I don't know how Gitea would run in the cloud if docker containers keep swapping unless using docker volume.
GiteaMirror commented 2025-11-02 07:34:18 -06:00
Author
Owner
Copy Link

@tacerus commented on GitHub (Aug 28, 2021):

After upgrading to v1.15, I have this after clicking any repository, organization or issue link. No error messages can be observed.

@tacerus commented on GitHub (Aug 28, 2021): After upgrading to v1.15, I have this after clicking any repository, organization or issue link. No error messages can be observed.
GiteaMirror commented 2025-11-02 07:34:18 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Aug 28, 2021):

@tacerus 500 or 404 returend?

@lunny commented on GitHub (Aug 28, 2021): @tacerus 500 or 404 returend?
GiteaMirror commented 2025-11-02 07:34:18 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Aug 28, 2021):

After upgrading to v1.15, I have this after clicking any repository link. No error messages can be observed.

From which version did you upgrade?

Is your [repository] ROOT correct?

It would be helpful to see some logs.

@zeripath commented on GitHub (Aug 28, 2021): > After upgrading to v1.15, I have this after clicking any repository link. No error messages can be observed. From which version did you upgrade? Is your `[repository]` `ROOT` correct? It would be helpful to see some logs.
GiteaMirror commented 2025-11-02 07:34:19 -06:00
Author
Owner
Copy Link

@tacerus commented on GitHub (Aug 28, 2021):

@lunny 500

@zeripath Yes, it is correct.
I now downgraded back to 1.14.6 (with a manual database rollback), which sorted the issue for now - unfortunately I forgot to save the trace logs beforehand.
I will try to attempt another upgrade next week and will take care of providing logs then.

Thanks for the quick response!

@tacerus commented on GitHub (Aug 28, 2021): @lunny 500 @zeripath Yes, it is correct. I now downgraded back to 1.14.6 (with a manual database rollback), which sorted the issue for now - unfortunately I forgot to save the trace logs beforehand. I will try to attempt another upgrade next week and will take care of providing logs then. Thanks for the quick response!
GiteaMirror commented 2025-11-02 07:34:19 -06:00
Author
Owner
Copy Link

@tacerus commented on GitHub (Aug 28, 2021):

I was able to try it again sooner.

Here's the log (level: trace), started just before attempting to open one of the pages (in this case an organization) causing a 500:

https://pasta.lysergic.dev/?6c1b79c0de06b567#7cqeueQrpzupubyJk6nbz5UiAwj4bN1nq7yAHH4Mdx1C

If there's anything I can try, I am happy to do so.

@tacerus commented on GitHub (Aug 28, 2021): I was able to try it again sooner. Here's the log (level: trace), started just before attempting to open one of the pages (in this case an organization) causing a 500: https://pasta.lysergic.dev/?6c1b79c0de06b567#7cqeueQrpzupubyJk6nbz5UiAwj4bN1nq7yAHH4Mdx1C If there's anything I can try, I am happy to do so.
GiteaMirror commented 2025-11-02 07:34:19 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Aug 28, 2021):

@tacerus

...rs/web/repo/issue.go:1143:ViewIssue() [E] RenderString: RenderContext did not provide context

This is a duplicate of #16835 and will be fixed by #16842

@zeripath commented on GitHub (Aug 28, 2021): @tacerus ``` ...rs/web/repo/issue.go:1143:ViewIssue() [E] RenderString: RenderContext did not provide context ``` This is a duplicate of #16835 and will be fixed by #16842
GiteaMirror commented 2025-11-02 07:34:19 -06:00
Author
Owner
Copy Link

@tacerus commented on GitHub (Aug 28, 2021):

Thank you!

@tacerus commented on GitHub (Aug 28, 2021): Thank you!
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/needs-feedback
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#7710
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?