Skip to content
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.

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

NoCommitterAccount: user does not exist #3602

Closed
2 of 7 tasks
Pofilo opened this issue Mar 1, 2018 · 1 comment · Fixed by #3621
Closed
2 of 7 tasks

NoCommitterAccount: user does not exist #3602

Pofilo opened this issue Mar 1, 2018 · 1 comment · Fixed by #3621

Comments

@Pofilo
Copy link
Contributor

Pofilo commented Mar 1, 2018

  • Gitea version (or commit ref): 1.3.3
  • Git version: 2.7.4
  • Operating system: Ubuntu 16.04.4 LTS
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No (no access to logs)
    • Not relevant
  • Log gist:

Description

I'm running my own instance of Gitea and I have some mirrors (linked to github mostly).
I have a lot of logs like this one which are errors:

[...ea/models/gpg_key.go:385 ParseCommitWithSignature()] [E] NoCommitterAccount: user does not exist [uid: 0, name: noreply@github.com, keyid: 0]

I don't know if this is relevant to the screenshot, plus I don't find any dock explaining what it means.

Does someone know what it means ? I have so many logs due to this thing I don't understand.

Screenshots

image

@lafriks
Copy link
Member

lafriks commented Mar 1, 2018

Yes this is not real error and should be lowered to information level in log

@lunny lunny added this to the 1.5.0 milestone Mar 3, 2018
lunny pushed a commit that referenced this issue Mar 4, 2018
* Don't write to log NoCommitterAccount

It's way too verbose, and the information is also printed to the user
already. Fixes #3602.

* ignore err only if it's a ErrUserNotExist

* Replace with IsErrUserNotExist
@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants