Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
gencer opened this issue Nov 11, 2016 · 5 comments
Closed

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

gencer opened this issue Nov 11, 2016 · 5 comments
Assignees
@lunny
Labels
issue/critical This issue should be fixed ASAP. If it is a PR, the PR should be merged ASAP type/bug
Milestone
1.0.0

Comments

@gencer
Copy link

gencer commented Nov 11, 2016 •
edited
Loading

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
@lunny lunny added type/bug issue/critical This issue should be fixed ASAP. If it is a PR, the PR should be merged ASAP labels Nov 11, 2016
@lunny lunny added this to the 1.0.0 milestone Nov 11, 2016
@lunny lunny self-assigned this Nov 11, 2016
lunny added a commit to lunny/gitea that referenced this issue Nov 11, 2016
@lunny
fixed bug go-gitea#151 caused Find should be Get
ec7b136
thibaultmeyer pushed a commit that referenced this issue Nov 11, 2016
@lunny @0xBAADF00D
fixed bug #151 caused Find should be Get (#153)
555d8b1
@strk
Copy link
Member

strk commented Nov 12, 2016

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

@gencer
Copy link
Author

gencer commented Nov 12, 2016 •
edited
Loading

@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
Copy link
Author

gencer commented 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

lunny added a commit to lunny/gitea that referenced this issue Nov 12, 2016
@lunny
fixed bug go-gitea#151 finally
995eb70
@lunny lunny mentioned this issue Nov 12, 2016
Merged
lunny added a commit that referenced this issue Nov 12, 2016
@lunny
fixed bug #151 finally (#164)
bd76e15
@fabian-z fabian-z mentioned this issue Nov 13, 2016
Merged
@gencer
Copy link
Author

gencer commented 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

@lunny
Copy link
Member

lunny commented 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 lunny closed this as completed Nov 14, 2016
@go-gitea go-gitea locked and limited conversation to collaborators Nov 23, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@lunny lunny

Labels
issue/critical This issue should be fixed ASAP. If it is a PR, the PR should be merged ASAP type/bug
Projects
None yet
Milestone
1.0.0
Development

No branches or pull requests
3 participants
@lunny @strk @gencer