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

Gogs: internal error Failed to get user by key ID(1): needs a pointer to a slice or a map #53

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

Originally created by @gencer on GitHub (Nov 11, 2016).

Originally assigned to: @lunny on GitHub.

I get following error;

Gogs: internal error Failed to get user by key ID(1): needs a pointer to a slice or a map fatal: Could not read from remote repository.

..when I try to push newly created repository.

SSH key is added to user's account.

PostgreSQL 9.6 used for data backend.

I use current master branch.

serv.log contains:
2016/11/11 17:16:19 [...o/gitea/cmd/serve.go:241 runServ()] [F] Failed to get user by key ID(1): needs a pointer to a slice or a map

Originally created by @gencer on GitHub (Nov 11, 2016). Originally assigned to: @lunny on GitHub. I get following error; `Gogs: internal error Failed to get user by key ID(1): needs a pointer to a slice or a map fatal: Could not read from remote repository. ` ..when I try to push newly created repository. SSH key is added to user's account. PostgreSQL 9.6 used for data backend. I use current **master** branch. serv.log contains: ` 2016/11/11 17:16:19 [...o/gitea/cmd/serve.go:241 runServ()] [F] Failed to get user by key ID(1): needs a pointer to a slice or a map`
GiteaMirror added the issue/criticaltype/bug labels 2025-11-02 03:06:18 -06:00
GiteaMirror commented 2025-11-02 03:06:19 -06:00
Author
Owner
Copy Link

@strk commented on GitHub (Nov 12, 2016):

@gencer could you please check if this is fixed now that #153 was merged ?

@strk commented on GitHub (Nov 12, 2016): @gencer could you please check if this is fixed now that #153 was merged ?
GiteaMirror commented 2025-11-02 03:06:19 -06:00
Author
Owner
Copy Link

@gencer commented on GitHub (Nov 12, 2016):

@strk I have successfully managed to push BUT almost. I get lot of hook rejected errors.

! [remote rejected] v1.16.10583-alpha -> v1.16.10583-alpha (hook declined)
remote: 2016/11/12 10:27:43 <nil>
remote: error: hook declined to update refs/tags/v4.23.304872-beta
remote: 2016/11/12 10:27:43 <nil>
remote: error: hook declined to update refs/tags/v4.233.304871-beta
remote: 2016/11/12 10:27:43 <nil>
remote: error: hook declined to update refs/tags/v5.0.330151-beta
remote: 2016/11/12 10:27:43 <nil>
remote: error: hook declined to update refs/tags/v6.0.0

...

 ! [remote rejected] master -> master (hook declined)
 ! [remote rejected] v1.16.10583-alpha -> v1.16.10583-alpha (hook declined)
 ! [remote rejected] v1.16.10584-alpha -> v1.16.10584-alpha (hook declined)
 ! [remote rejected] v1.17.10585-alpha -> v1.17.10585-alpha (hook declined)
 ! [remote rejected] v1.18.10586-alpha -> v1.18.10586-alpha (hook declined)
 ! [remote rejected] v1.18.10587-alpha -> v1.18.10587-alpha (hook declined)
 ! [remote rejected] v1.19.10588-alpha -> v1.19.10588-alpha (hook declined)
 ! [remote rejected] v2.20.10589-alpha -> v2.20.10589-alpha (hook declined)
 ! [remote rejected] v2.21.10590-alpha -> v2.21.10590-alpha (hook declined)
 ! [remote rejected] v2.21.10591-alpha -> v2.21.10591-alpha (hook declined)
 ! [remote rejected] v3.109.20389-alpha -> v3.109.20389-alpha (hook declined)
 ! [remote rejected] v4.23.304872-beta -> v4.23.304872-beta (hook declined)
 ! [remote rejected] v4.233.304871-beta -> v4.233.304871-beta (hook declined)
 ! [remote rejected] v5.0.330151-beta -> v5.0.330151-beta (hook declined)
 ! [remote rejected] v6.0.0 -> v6.0.0 (hook declined)

Aditional note: repo page shows 500 error.

Gogs has no this issue at all.

@gencer commented on GitHub (Nov 12, 2016): @strk I have successfully managed to push BUT almost. I get lot of hook rejected errors. ``` ! [remote rejected] v1.16.10583-alpha -> v1.16.10583-alpha (hook declined) remote: 2016/11/12 10:27:43 <nil> remote: error: hook declined to update refs/tags/v4.23.304872-beta remote: 2016/11/12 10:27:43 <nil> remote: error: hook declined to update refs/tags/v4.233.304871-beta remote: 2016/11/12 10:27:43 <nil> remote: error: hook declined to update refs/tags/v5.0.330151-beta remote: 2016/11/12 10:27:43 <nil> remote: error: hook declined to update refs/tags/v6.0.0 ... ! [remote rejected] master -> master (hook declined) ! [remote rejected] v1.16.10583-alpha -> v1.16.10583-alpha (hook declined) ! [remote rejected] v1.16.10584-alpha -> v1.16.10584-alpha (hook declined) ! [remote rejected] v1.17.10585-alpha -> v1.17.10585-alpha (hook declined) ! [remote rejected] v1.18.10586-alpha -> v1.18.10586-alpha (hook declined) ! [remote rejected] v1.18.10587-alpha -> v1.18.10587-alpha (hook declined) ! [remote rejected] v1.19.10588-alpha -> v1.19.10588-alpha (hook declined) ! [remote rejected] v2.20.10589-alpha -> v2.20.10589-alpha (hook declined) ! [remote rejected] v2.21.10590-alpha -> v2.21.10590-alpha (hook declined) ! [remote rejected] v2.21.10591-alpha -> v2.21.10591-alpha (hook declined) ! [remote rejected] v3.109.20389-alpha -> v3.109.20389-alpha (hook declined) ! [remote rejected] v4.23.304872-beta -> v4.23.304872-beta (hook declined) ! [remote rejected] v4.233.304871-beta -> v4.233.304871-beta (hook declined) ! [remote rejected] v5.0.330151-beta -> v5.0.330151-beta (hook declined) ! [remote rejected] v6.0.0 -> v6.0.0 (hook declined) ``` Aditional note: repo page shows **500** error. Gogs has no this issue at all.
GiteaMirror commented 2025-11-02 03:06:19 -06:00
Author
Owner
Copy Link

@gencer commented on GitHub (Nov 12, 2016):

@strk this message is for notification only. (email)

Also fresh installation of database and repo dir has same issue. hooks are rejected.

git push -u origin master --tags

@gencer commented on GitHub (Nov 12, 2016): @strk this message is for notification only. (email) Also fresh installation of database and repo dir has same issue. hooks are rejected. `git push -u origin master --tags`
GiteaMirror commented 2025-11-02 03:06:20 -06:00
Author
Owner
Copy Link

@gencer commented on GitHub (Nov 13, 2016):

@lunny @strk issue has been fixed. Thanks!

I made a github theme patch. If anyone interested. It is still in development and file size is bigger. It will be smaller in the future.

https://github.com/gencer/gitea-gihubify

@gencer commented on GitHub (Nov 13, 2016): @lunny @strk issue has been fixed. Thanks! I made a github theme patch. If anyone interested. It is still in development and file size is bigger. It will be smaller in the future. https://github.com/gencer/gitea-gihubify
GiteaMirror commented 2025-11-02 03:06:20 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Nov 14, 2016):

Great theme! We will support theme feature later. Now I will close this issue. Please feel free if you have any further question.

@lunny commented on GitHub (Nov 14, 2016): Great theme! We will support theme feature later. Now I will close this issue. Please feel free if you have any further question.
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#53
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?