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

NotFoundOrServerError() [id: 0, uid: 0, owner_name: vendor, name: plugins] #2036

New Issue
Closed
opened 2025-11-02 04:21:54 -06:00 by GiteaMirror · 6 comments
GiteaMirror commented 2025-11-02 04:21:54 -06:00
Owner
Copy Link

Originally created by @chliang on GitHub (Jul 10, 2018).

  • Gitea version (or commit ref):1.5.0-rc1
  • Git version:2.18
  • Operating system:
  • 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:
2018/07/10 10:46:53 [...s/context/context.go:147 NotFoundOrServerError()] [E] GetRepositoryByOwnerAndName: repository does not exist [id: 0, uid: 0, owner_name: vendor, name: plugins]

Description

...

Screenshots

Originally created by @chliang on GitHub (Jul 10, 2018). <!-- 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.5.0-rc1 - Git version:2.18 - Operating system: - Database (use `[x]`): - [ ] PostgreSQL - [ ] MySQL - [ ] MSSQL - [x] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [x] No - [ ] Not relevant - Log gist: ``` 2018/07/10 10:46:53 [...s/context/context.go:147 NotFoundOrServerError()] [E] GetRepositoryByOwnerAndName: repository does not exist [id: 0, uid: 0, owner_name: vendor, name: plugins] ``` ## Description ... ## Screenshots <!-- **If this issue involves the Web Interface, please include a screenshot** -->
GiteaMirror added the issue/staleissue/needs-feedbacktype/bug labels 2025-11-02 04:21:54 -06:00
GiteaMirror commented 2025-11-02 04:21:55 -06:00
Author
Owner
Copy Link

@lafriks commented on GitHub (Jul 10, 2018):

Need more information on when such error is displayed and for what url

@lafriks commented on GitHub (Jul 10, 2018): Need more information on when such error is displayed and for what url
GiteaMirror commented 2025-11-02 04:21:55 -06:00
Author
Owner
Copy Link

@ghost commented on GitHub (Aug 19, 2018):

As the OP is a bit quiet and I have exactly the same symptoms I like to give some informations on my installation:

Gitea version 1.5.0, but I saw it also on 1.4.3 (and ignored it)
Using MySQL/MariaDB as the database, xorm.log shows no errors.

I noticed it, when using a crawler for generating a sitemap. When remote systems are accessing my installation, it happens quite seldom. So it's more an annoyance than a real issue (for me).

The log message, only the "name:" differs, the other fields say the same:
2018/08/19 23:16:10 [...s/context/context.go:147 NotFoundOrServerError()] [E] GetRepositoryByOwnerAndName: repository does not exist [id: 0, uid: 0, owner_name: vendor, name: assets]

The following links, referenced from /vendor/librejs.html (the "JavaScript licenses" page) create this issue:

  • /vendor/assets/swagger-ui/
  • /vendor/assets/font-awesome/fonts/
  • /vendor/assets/font-awesome/css/
  • /vendor/plugins/pdfjs/
  • /vendor/assets/octicons/
  • /vendor/plugins/u2f/
@ghost commented on GitHub (Aug 19, 2018): As the OP is a bit quiet and I have exactly the same symptoms I like to give some informations on my installation: Gitea version 1.5.0, but I saw it also on 1.4.3 (and ignored it) Using MySQL/MariaDB as the database, xorm.log shows no errors. I noticed it, when using a crawler for generating a sitemap. When remote systems are accessing my installation, it happens quite seldom. So it's more an annoyance than a real issue (for me). The log message, only the "name:" differs, the other fields say the same: `2018/08/19 23:16:10 [...s/context/context.go:147 NotFoundOrServerError()] [E] GetRepositoryByOwnerAndName: repository does not exist [id: 0, uid: 0, owner_name: vendor, name: assets]` The following links, referenced from /vendor/librejs.html (the "JavaScript licenses" page) create this issue: - /vendor/assets/swagger-ui/ - /vendor/assets/font-awesome/fonts/ - /vendor/assets/font-awesome/css/ - /vendor/plugins/pdfjs/ - /vendor/assets/octicons/ - /vendor/plugins/u2f/
GiteaMirror commented 2025-11-02 04:21:55 -06:00
Author
Owner
Copy Link

@ghost commented on GitHub (Oct 10, 2018):

@lafriks What additional info do you need, so the "status/needs-feedback" label can be removed?

@ghost commented on GitHub (Oct 10, 2018): @lafriks What additional info do you need, so the "status/needs-feedback" label can be removed?
GiteaMirror commented 2025-11-02 04:21:56 -06:00
Author
Owner
Copy Link

@LaughingBlue commented on GitHub (Nov 26, 2018):

My Gitea version was 1.5.3 and after got this problem I upgrade to the latest 1.6.0, but the problem still existed.
I reproduce this symptom by running gitea in terminal with
$ gitea web --port 443,
after that I stop the gitea and restart it again without port variable like
$ gitea web
and then I can't modify my repos with these kinds of error msgs

 ! [remote rejected] master -> master (pre-receive hook declined)
error: failed to push some refs to 'MyGiteaAddress.git'

And got the log msg as same as yours

2018/11/26 22:01:21 [...s/context/context.go:147 NotFoundOrServerError()] [E] GetRepositoryByOwnerAndName: repository does not exist [id: 0, uid: 0, owner_name: vendor, name: plugins]

I solve this problem by remove the line LOCAL_ROOT_URL = http://localhost:443/ in config fileapp.ini section[server] . And then restart gitea again, all works fine.

Hope this helps.

EDIT:

Sorry, I just noticed that I've got these error log for a long time. The earliest one was 10/23

2018/10/23 00:55:15 [...s/context/context.go:147 NotFoundOrServerError()] [E] GetRepositoryByOwnerAndName: repository does not exist [id: 0, uid: 0, owner_name: vendor, name: plugins]

So my problem was only "Can't modify my repos after running gitea web --port 443" and seems that not relate to the error log.

@LaughingBlue commented on GitHub (Nov 26, 2018): My Gitea version was 1.5.3 and after got this problem I upgrade to the latest 1.6.0, but the problem still existed. I reproduce this symptom by running gitea in terminal with `$ gitea web --port 443`, after that I stop the gitea and restart it again without `port` variable like `$ gitea web` and then I can't modify my repos with these kinds of error msgs ``` ! [remote rejected] master -> master (pre-receive hook declined) error: failed to push some refs to 'MyGiteaAddress.git' ``` And got the log msg as same as yours ``` 2018/11/26 22:01:21 [...s/context/context.go:147 NotFoundOrServerError()] [E] GetRepositoryByOwnerAndName: repository does not exist [id: 0, uid: 0, owner_name: vendor, name: plugins] ``` I solve this problem by remove the line `LOCAL_ROOT_URL = http://localhost:443/` in config file`app.ini` section`[server]` . And then restart gitea again, all works fine. Hope this helps. --- ### EDIT: Sorry, I just noticed that I've got these error log for a long time. The earliest one was 10/23 ``` 2018/10/23 00:55:15 [...s/context/context.go:147 NotFoundOrServerError()] [E] GetRepositoryByOwnerAndName: repository does not exist [id: 0, uid: 0, owner_name: vendor, name: plugins] ``` So my problem was only "Can't modify my repos after running `gitea web --port 443`" and seems that not relate to the error log.
GiteaMirror commented 2025-11-02 04:21:56 -06:00
Author
Owner
Copy Link

@lafriks commented on GitHub (Nov 26, 2018):

@chliang can you confirm that local_root_url is valid for you?

@lafriks commented on GitHub (Nov 26, 2018): @chliang can you confirm that local_root_url is valid for you?
GiteaMirror commented 2025-11-02 04:21:56 -06:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Jan 25, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Jan 25, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.
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 issue/stale 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#2036
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?