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

Backup (dump) command fails with stacktrace - latest tag on dockerhub (1.7.6 works fine) #3281

New Issue
Closed
opened 2025-11-02 05:06:29 -06:00 by GiteaMirror · 2 comments
GiteaMirror commented 2025-11-02 05:06:29 -06:00
Owner
Copy Link

Originally created by @jgwilson42 on GitHub (May 1, 2019).

  • Gitea version (or commit ref): Gitea version caba282 built with GNU Make 4.2.1, go1.12.4 : bindata, sqlite, sqlite_unlock_notify
  • Git version: NA
  • Operating system: docker image gitea/gitea:latest
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist:

Description

When trying to run the backup I get the following stack trace:

git-67778cc5ff-xmz9c:/app/gitea$ ./gitea dump -c /data/gitea/conf/app.ini
dump flag redefined: v
panic: dump flag redefined: v

goroutine 1 [running]:
flag.(*FlagSet).Var(0xc000168780, 0x1c4ea00, 0xc000040cf5, 0x199833c, 0x1, 0x19a9963, 0x11)
	/usr/local/go/src/flag/flag.go:850 +0x4af
flag.(*FlagSet).BoolVar(...)
	/usr/local/go/src/flag/flag.go:623
flag.(*FlagSet).Bool(0xc000168780, 0x199833c, 0x1, 0x0, 0x19a9963, 0x11, 0x1)
	/usr/local/go/src/flag/flag.go:636 +0x8b
github.com/urfave/cli.BoolFlag.Apply.func1(0x199833c, 0x1)
	/go/src/code.gitea.io/gitea/vendor/github.com/urfave/cli/flag.go:274 +0xb3
github.com/urfave/cli.eachName(0x1998333, 0xa, 0xc0005f1770)
	/go/src/code.gitea.io/gitea/vendor/github.com/urfave/cli/flag.go:78 +0xdc
github.com/urfave/cli.BoolFlag.Apply(0x1998333, 0xa, 0x19a9963, 0x11, 0x0, 0x0, 0x0, 0x0, 0xc000168780)
	/go/src/code.gitea.io/gitea/vendor/github.com/urfave/cli/flag.go:269 +0xfa
github.com/urfave/cli.flagSet(0x198a6e5, 0x4, 0xc0002f2960, 0x9, 0xa, 0x1)
	/go/src/code.gitea.io/gitea/vendor/github.com/urfave/cli/flag.go:69 +0x90
github.com/urfave/cli.Command.Run(0x198a6e5, 0x4, 0x0, 0x0, 0x0, 0x0, 0x0, 0x19c5241, 0x1d, 0x0, ...)
	/go/src/code.gitea.io/gitea/vendor/github.com/urfave/cli/command.go:94 +0xc1
github.com/urfave/cli.(*App).Run(0xc0002a8820, 0xc00003c100, 0x4, 0x4, 0x0, 0x0)
	/go/src/code.gitea.io/gitea/vendor/github.com/urfave/cli/app.go:241 +0x658
main.main()
	/go/src/code.gitea.io/gitea/main.go:100 +0x75b
git-67778cc5ff-xmz9c:/app/gitea$

...

Screenshots

NA

Originally created by @jgwilson42 on GitHub (May 1, 2019). - Gitea version (or commit ref): Gitea version caba282 built with GNU Make 4.2.1, go1.12.4 : bindata, sqlite, sqlite_unlock_notify - Git version: NA - Operating system: docker image gitea/gitea:latest - Database (use `[x]`): - [ ] PostgreSQL - [x] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [x] Not relevant - Log gist: ## Description When trying to run the backup I get the following stack trace: ``` git-67778cc5ff-xmz9c:/app/gitea$ ./gitea dump -c /data/gitea/conf/app.ini dump flag redefined: v panic: dump flag redefined: v goroutine 1 [running]: flag.(*FlagSet).Var(0xc000168780, 0x1c4ea00, 0xc000040cf5, 0x199833c, 0x1, 0x19a9963, 0x11) /usr/local/go/src/flag/flag.go:850 +0x4af flag.(*FlagSet).BoolVar(...) /usr/local/go/src/flag/flag.go:623 flag.(*FlagSet).Bool(0xc000168780, 0x199833c, 0x1, 0x0, 0x19a9963, 0x11, 0x1) /usr/local/go/src/flag/flag.go:636 +0x8b github.com/urfave/cli.BoolFlag.Apply.func1(0x199833c, 0x1) /go/src/code.gitea.io/gitea/vendor/github.com/urfave/cli/flag.go:274 +0xb3 github.com/urfave/cli.eachName(0x1998333, 0xa, 0xc0005f1770) /go/src/code.gitea.io/gitea/vendor/github.com/urfave/cli/flag.go:78 +0xdc github.com/urfave/cli.BoolFlag.Apply(0x1998333, 0xa, 0x19a9963, 0x11, 0x0, 0x0, 0x0, 0x0, 0xc000168780) /go/src/code.gitea.io/gitea/vendor/github.com/urfave/cli/flag.go:269 +0xfa github.com/urfave/cli.flagSet(0x198a6e5, 0x4, 0xc0002f2960, 0x9, 0xa, 0x1) /go/src/code.gitea.io/gitea/vendor/github.com/urfave/cli/flag.go:69 +0x90 github.com/urfave/cli.Command.Run(0x198a6e5, 0x4, 0x0, 0x0, 0x0, 0x0, 0x0, 0x19c5241, 0x1d, 0x0, ...) /go/src/code.gitea.io/gitea/vendor/github.com/urfave/cli/command.go:94 +0xc1 github.com/urfave/cli.(*App).Run(0xc0002a8820, 0xc00003c100, 0x4, 0x4, 0x0, 0x0) /go/src/code.gitea.io/gitea/vendor/github.com/urfave/cli/app.go:241 +0x658 main.main() /go/src/code.gitea.io/gitea/main.go:100 +0x75b git-67778cc5ff-xmz9c:/app/gitea$ ``` ... ## Screenshots NA
GiteaMirror added the type/bug label 2025-11-02 05:06:29 -06:00
GiteaMirror commented 2025-11-02 05:06:29 -06:00
Author
Owner
Copy Link

@jgwilson42 commented on GitHub (May 1, 2019):

This appears to be a regression in the latest tag on dockerhub (compared with gitea/gitea:1.7.6)

@jgwilson42 commented on GitHub (May 1, 2019): This appears to be a regression in the latest tag on dockerhub (compared with gitea/gitea:1.7.6)
GiteaMirror commented 2025-11-02 05:06:29 -06:00
Author
Owner
Copy Link

@jolheiser commented on GitHub (May 1, 2019):

This is caused by the addition of the Version Flag (source), which is fighting with our existing Verbose Flag.

@jolheiser commented on GitHub (May 1, 2019): This is caused by the addition of the [Version Flag](https://github.com/go-gitea/gitea/blob/master/main.go#L86) [(source)](https://github.com/urfave/cli/blob/master/flag.go#L23-L27), which is fighting with our existing [Verbose Flag](https://github.com/go-gitea/gitea/blob/master/cmd/dump.go#L38-L41).
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 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#3281
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?