github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-24 23:46:30 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Table project warnings after upgrade from 1.13 to 1.15 #8100

New Issue
Closed
opened 2025-11-02 07:53:56 -06:00 by GiteaMirror · 3 comments
GiteaMirror commented 2025-11-02 07:53:56 -06:00
Owner
Copy Link

Originally created by @pboguslawski on GitHub (Nov 12, 2021).

Gitea Version

1cec7f5ab5

Git Version

2.30.2

Operating System

Debian 11

How are you running Gitea?

Build from github sources.

Database

MySQL

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Description

After upgrading from 1.13 to 1.15 warnings are thrown on gitea startup:

2021/11/12 21:37:00 ...om/urfave/cli/app.go:524:HandleAction() [W] Table email_address Column lower_email db nullable is true, struct nullable is false
2021/11/12 21:37:00 ...om/urfave/cli/app.go:524:HandleAction() [W] Table external_login_user column avatar_url db type is TEXT, struct type is VARCHAR(255)
2021/11/12 21:37:00 ...om/urfave/cli/app.go:524:HandleAction() [W] Table project column board_type db type is INT(11), struct type is INT UNSIGNED
2021/11/12 21:37:00 ...om/urfave/cli/app.go:524:HandleAction() [W] Table project column type db type is INT(11), struct type is INT UNSIGNED

Accroding to https://github.com/go-gitea/gitea/issues/16393 executing gitea doctor recreate-table email_address external_login_user project should resolve issue but only email_address and external_login_user warnings disappear but project table warnings still exist. Repeating only for project table...

$ gitea doctor recreate-table project
2021/11/12 21:51:21 ...s/setting/setting.go:902:NewContext() [I] Default UI Location is Europe/Warsaw
2021/11/12 21:51:21 ...om/urfave/cli/app.go:405:RunAsSubcommand() [I] PING DATABASE mysql
2021/11/12 21:51:21 ...ations/migrations.go:444:func1() [I] Recreating Table: project for Bean: Project
2021/11/12 21:51:22 ...om/urfave/cli/app.go:405:RunAsSubcommand() [W] Table project column board_type db type is INT(10) UNSIGNED, struct type is INT UNSIGNED
2021/11/12 21:51:22 ...om/urfave/cli/app.go:405:RunAsSubcommand() [W] Table project column type db type is INT(10) UNSIGNED, struct type is INT UNSIGNED

...does not help:

2021/11/12 22:02:52 ...om/urfave/cli/app.go:524:HandleAction() [W] Table project column board_type db type is INT(10) UNSIGNED, struct type is INT UNSIGNED
2021/11/12 22:02:52 ...om/urfave/cli/app.go:524:HandleAction() [W] Table project column type db type is INT(10) UNSIGNED, struct type is INT UNSIGNED

Warnings in logs should not be ignored. How to fix it?

Screenshots

No response

Originally created by @pboguslawski on GitHub (Nov 12, 2021). ### Gitea Version 1cec7f5ab5e4a02b68a4223f1ad0166118a6e953 ### Git Version 2.30.2 ### Operating System Debian 11 ### How are you running Gitea? Build from github sources. ### Database MySQL ### Can you reproduce the bug on the Gitea demo site? No ### Log Gist _No response_ ### Description After upgrading from 1.13 to 1.15 warnings are thrown on gitea startup: ``` 2021/11/12 21:37:00 ...om/urfave/cli/app.go:524:HandleAction() [W] Table email_address Column lower_email db nullable is true, struct nullable is false 2021/11/12 21:37:00 ...om/urfave/cli/app.go:524:HandleAction() [W] Table external_login_user column avatar_url db type is TEXT, struct type is VARCHAR(255) 2021/11/12 21:37:00 ...om/urfave/cli/app.go:524:HandleAction() [W] Table project column board_type db type is INT(11), struct type is INT UNSIGNED 2021/11/12 21:37:00 ...om/urfave/cli/app.go:524:HandleAction() [W] Table project column type db type is INT(11), struct type is INT UNSIGNED ``` Accroding to https://github.com/go-gitea/gitea/issues/16393 executing ` gitea doctor recreate-table email_address external_login_user project` should resolve issue but only email_address and external_login_user warnings disappear but project table warnings still exist. Repeating only for project table... ``` $ gitea doctor recreate-table project 2021/11/12 21:51:21 ...s/setting/setting.go:902:NewContext() [I] Default UI Location is Europe/Warsaw 2021/11/12 21:51:21 ...om/urfave/cli/app.go:405:RunAsSubcommand() [I] PING DATABASE mysql 2021/11/12 21:51:21 ...ations/migrations.go:444:func1() [I] Recreating Table: project for Bean: Project 2021/11/12 21:51:22 ...om/urfave/cli/app.go:405:RunAsSubcommand() [W] Table project column board_type db type is INT(10) UNSIGNED, struct type is INT UNSIGNED 2021/11/12 21:51:22 ...om/urfave/cli/app.go:405:RunAsSubcommand() [W] Table project column type db type is INT(10) UNSIGNED, struct type is INT UNSIGNED ``` ...does not help: ``` 2021/11/12 22:02:52 ...om/urfave/cli/app.go:524:HandleAction() [W] Table project column board_type db type is INT(10) UNSIGNED, struct type is INT UNSIGNED 2021/11/12 22:02:52 ...om/urfave/cli/app.go:524:HandleAction() [W] Table project column type db type is INT(10) UNSIGNED, struct type is INT UNSIGNED ``` Warnings in logs should not be ignored. How to fix it? ### Screenshots _No response_
GiteaMirror commented 2025-11-02 07:53:57 -06:00
Author
Owner
Copy Link

@pboguslawski commented on GitHub (Feb 3, 2022):

Same problem after upgrade from 1.13 to 1.16-rc1.

@pboguslawski commented on GitHub (Feb 3, 2022): Same problem after upgrade from 1.13 to 1.16-rc1.
GiteaMirror commented 2025-11-02 07:53:57 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Feb 3, 2022):

These can be ignored. They are a bug with xorm's matching of the inferred schema with that of the struct.

Please raise a bug at https://gitea.com/xorm/xorm

@zeripath commented on GitHub (Feb 3, 2022): These can be ignored. They are a bug with xorm's matching of the inferred schema with that of the struct. Please raise a bug at https://gitea.com/xorm/xorm
GiteaMirror commented 2025-11-02 07:53:57 -06:00
Author
Owner
Copy Link

@pboguslawski commented on GitHub (Feb 3, 2022):

These can be ignored.

Ignoring errors/warnings in logs is bad habit and should be avoided.

Please raise a bug at https://gitea.com/xorm/xorm

Raised:
https://gitea.com/xorm/xorm/issues/2110

@pboguslawski commented on GitHub (Feb 3, 2022): > These can be ignored. Ignoring errors/warnings in logs is bad habit and should be avoided. > Please raise a bug at https://gitea.com/xorm/xorm Raised: https://gitea.com/xorm/xorm/issues/2110
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
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#8100
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?