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

configure-gitea init error panic #26857

Closed
wenchao5211 opened this issue Sep 1, 2023 · 2 comments
Closed

configure-gitea init error panic #26857

wenchao5211 opened this issue Sep 1, 2023 · 2 comments
Labels

Comments

@wenchao5211
Copy link

Description

2023/09/01 05:53:10 .../cli@v1.22.13/app.go:410:RunAsSubcommand() [I] PING DATABASE postgres
2023/09/01 05:53:10 .../cli@v1.22.13/app.go:410:RunAsSubcommand() [W] Table system_setting Column version db default is , struct default is 1
2023/09/01 05:53:11 .../cli@v1.22.13/app.go:410:RunAsSubcommand() [W] Table oauth2_application Column confidential_client db default is true, struct default is TRUE
2023/09/01 05:53:11 .../cli@v1.22.13/app.go:410:RunAsSubcommand() [W] Table user Column max_repo_creation db default is '-1', struct default is -1
Wait for redis to become avialable...
wukong-redis-cluster-headless.wentest.svc.cluster.local (10.42.1.126:6379) open
Admin account 'xxxx' already exist. Running update to sync password...
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0x50fa3a]

goroutine 1 [running]:
fmt.Fprintf({0x0, 0x0}, {0x328870b, 0x12}, {0xc00337e780, 0x1, 0x1})
/usr/local/go/src/fmt/print.go:225 +0x7a
code.gitea.io/gitea/cmd.RunMainApp(0xc0034ae1c0, {0xc000052080?, 0x4?, 0xc00337e978?})
/go/src/code.gitea.io/gitea/cmd/main.go:23 +0xc7
main.main()
/go/src/code.gitea.io/gitea/main.go:166 +0xc2

Gitea Version

1.20.3

Can you reproduce the bug on the Gitea demo site?

Yes

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

No response

How are you running Gitea?

k8s

Database

PostgreSQL

@wenchao5211
Copy link
Author

This error doesn't exist after gitea pod restarts automatically a few times, but I think it's a problem

@wenchao5211 wenchao5211 changed the title config-gitea init erroe configure-gitea init error Sep 1, 2023
@wenchao5211 wenchao5211 changed the title configure-gitea init error configure-gitea init error panic Sep 1, 2023
@wxiaoguang
Copy link
Contributor

It should have been fixed by "Set errwriter for urfave/cli v1 #26616"

You can use the nightly build.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 17, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants