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

GetUserRepoPermission: invalid character '&' looking for beginning of value #9422

New Issue
Closed
opened 2025-11-02 08:38:16 -06:00 by GiteaMirror · 1 comment
GiteaMirror commented 2025-11-02 08:38:16 -06:00
Owner
Copy Link

Originally created by @safag05 on GitHub (Aug 18, 2022).

Description

We are using helm chart to deploy Gitea. We are trying to migrate our instance from image version 1.14.5 to 1.16.7. After the helm upgrade we received the following error in the logs when trying to access the existing repos. We do not have any issues with the new repos.

GetUserRepoPermission: invalid character '&' looking for beginning of value

Gitea Version

1.16.7

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

2022/08/17 22:24:16 ...orm@v1.2.5/engine.go:1139:Get() [I] [SQL] SELECT "id", "owner_id", "owner_name", "lower_name", "name", "description", "website", "original_service_type", "original_url", "default_branch", "num_watches", "num_stars", "num_forks", "num_issues", "num_closed_issues", "num_pulls", "num_closed_pulls", "num_milestones", "num_closed_milestones", "num_projects", "num_closed_projects", "is_private", "is_empty", "is_archived", "is_mirror", "status", "is_fork", "fork_id", "is_template", "template_id", "size", "is_fsck_enabled", "close_issues_via_commit_in_any_branch", "topics", "trust_model", "avatar", "created_unix", "updated_unix" FROM "repository" WHERE "owner_id"=$1 AND "lower_name"=$2 LIMIT 1 [1 test-cve] - 1.04514ms 2022/08/17 22:24:16 ...orm@v1.2.5/engine.go:1139:Get() [I] [SQL] SELECT "id", "repo_id", "user_id", "mode", "created_unix", "updated_unix" FROM "collaboration" WHERE "repo_id"=$1 AND "user_id"=$2 LIMIT 1 [949 5] - 747.96µs 2022/08/17 22:24:16 ...ls/repo/repo_unit.go:226:getUnitsByRepoID() [I] [SQL] SELECT "id", "repo_id", "type", "config", "created_unix" FROM "repo_unit" WHERE (repo_id = $1) [949] - 666.38µs 2022/08/17 22:24:16 ...ules/context/repo.go:351:repoAssignment() [E] GetUserRepoPermission: invalid character '&' looking for beginning of value 2022/08/17 22:24:16 ...s/context/context.go:204:HTML() [D] Template: status/500

Screenshots

No response

Git Version

2.30.5

Operating System

Kubernetes Pod (Linux)

How are you running Gitea?

Gitea is deployed via helm charts on Kubernetes cluster.

Database

PostgreSQL

Originally created by @safag05 on GitHub (Aug 18, 2022). ### Description We are using helm chart to deploy Gitea. We are trying to migrate our instance from image version 1.14.5 to 1.16.7. After the helm upgrade we received the following error in the logs when trying to access the existing repos. We do not have any issues with the new repos. `GetUserRepoPermission: invalid character '&' looking for beginning of value` ### Gitea Version 1.16.7 ### Can you reproduce the bug on the Gitea demo site? No ### Log Gist 2022/08/17 22:24:16 ...orm@v1.2.5/engine.go:1139:Get() [I] [SQL] SELECT "id", "owner_id", "owner_name", "lower_name", "name", "description", "website", "original_service_type", "original_url", "default_branch", "num_watches", "num_stars", "num_forks", "num_issues", "num_closed_issues", "num_pulls", "num_closed_pulls", "num_milestones", "num_closed_milestones", "num_projects", "num_closed_projects", "is_private", "is_empty", "is_archived", "is_mirror", "status", "is_fork", "fork_id", "is_template", "template_id", "size", "is_fsck_enabled", "close_issues_via_commit_in_any_branch", "topics", "trust_model", "avatar", "created_unix", "updated_unix" FROM "repository" WHERE "owner_id"=$1 AND "lower_name"=$2 LIMIT 1 [1 test-cve] - 1.04514ms 2022/08/17 22:24:16 ...orm@v1.2.5/engine.go:1139:Get() [I] [SQL] SELECT "id", "repo_id", "user_id", "mode", "created_unix", "updated_unix" FROM "collaboration" WHERE "repo_id"=$1 AND "user_id"=$2 LIMIT 1 [949 5] - 747.96µs 2022/08/17 22:24:16 ...ls/repo/repo_unit.go:226:getUnitsByRepoID() [I] [SQL] SELECT "id", "repo_id", "type", "config", "created_unix" FROM "repo_unit" WHERE (repo_id = $1) [949] - 666.38µs 2022/08/17 22:24:16 ...ules/context/repo.go:351:repoAssignment() [E] GetUserRepoPermission: invalid character '&' looking for beginning of value 2022/08/17 22:24:16 ...s/context/context.go:204:HTML() [D] Template: status/500 ### Screenshots _No response_ ### Git Version 2.30.5 ### Operating System Kubernetes Pod (Linux) ### How are you running Gitea? Gitea is deployed via helm charts on Kubernetes cluster. ### Database PostgreSQL
GiteaMirror added the type/bugissue/duplicate labels 2025-11-02 08:38:16 -06:00
GiteaMirror commented 2025-11-02 08:38:17 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Aug 18, 2022):

This is #16961. There was a bug in gitea dump from 1.14.3—1.14.6 and 1.15.0.

See https://blog.gitea.io/2021/12/gitea-1.15.8-is-released/ (+ many other blog posts in the 1.15 series.)

⚠️ We remind users that a bug was discovered with gitea dump in 1.14.3–1.14.6 and 1.15.0. Database dumps from these versions cause broken fields in the repo_unit and login_source tables causing the issue identified in #16961. Users on 1.14.x must upgrade to 1.14.7 before running gitea dump. If this is not possible and you are affected #17137 provides a new gitea doctor command to fix the repo_unit issue:

gitea doctor --fix --run fix-broken-repo-units
@zeripath commented on GitHub (Aug 18, 2022): This is #16961. There was a bug in gitea dump from 1.14.3—1.14.6 and 1.15.0. See https://blog.gitea.io/2021/12/gitea-1.15.8-is-released/ (+ many other blog posts in the 1.15 series.) --- :warning: We remind users that a bug was discovered with gitea dump in 1.14.3–1.14.6 and 1.15.0. Database dumps from these versions cause broken fields in the repo_unit and login_source tables causing the issue identified in [#16961](https://github.com/go-gitea/gitea/pull/16961). Users on 1.14.x must upgrade to 1.14.7 before running gitea dump. If this is not possible and you are affected [#17137](https://github.com/go-gitea/gitea/pull/17137) provides a new gitea doctor command to fix the repo_unit issue: ``` gitea doctor --fix --run fix-broken-repo-units ```
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/duplicate 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#9422
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?