Skip to content

NotifySyncPushCommits() [E] NotifyWatchers: insert new actioner: Error 1406 (22001): Data too long for column 'content' at row 1 #28193

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
pboguslawski opened this issue Nov 24, 2023 · 5 comments · Fixed by #34233
Closed

NotifySyncPushCommits() [E] NotifyWatchers: insert new actioner: Error 1406 (22001): Data too long for column 'content' at row 1 #28193

pboguslawski opened this issue Nov 24, 2023 · 5 comments · Fixed by #34233
Labels
good first issue Likely to be an easy fix issue/critical This issue should be fixed ASAP. If it is a PR, the PR should be merged ASAP type/bug
Milestone
1.24.0

Comments

@pboguslawski
Copy link
Contributor

Description

One occurrence of

2023/11/24 02:07:13 ...ion/action/action.go:403:NotifySyncPushCommits() [E] NotifyWatchers: insert new actioner: Error 1406 (22001): Data too long for column 'content' at row 1

was caught in gitea 1.20.3 error log on mirror update.

Gitea Version

1.20.3

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

No response

Git Version

2.30.2

Operating System

Debian

How are you running Gitea?

Compiled from sources.

Database

MySQL/MariaDB
@lng2020
Copy link
Member

lng2020 commented Nov 28, 2023

This field uses TEXT in MySQL which is at most 64kb. You can adjust your MySQL settings.

@lng2020 lng2020 added the issue/needs-feedback For bugs, we need more details. For features, the feature must be described in more detail label Nov 28, 2023
@wxiaoguang
Copy link
Contributor

You can adjust your MySQL settings.

How to "adjust your MySQL settings"? At least, I do not think "truncate silently" is a choice for modern databases.

@lng2020
Copy link
Member

lng2020 commented Nov 28, 2023

I was wrong. It can't be adjusted.

@wxiaoguang
Copy link
Contributor

I think it should be truncated explicitly on Gitea side, to make sure the message fit the database size.

@lng2020 lng2020 removed the issue/needs-feedback For bugs, we need more details. For features, the feature must be described in more detail label Nov 29, 2023
@pboguslawski
Copy link
Contributor Author

Another similar message noticed in gitea 1.21.10:

2025/04/15 18:46:59 ...vices/feed/action.go:409:SyncPushCommits() [E] NotifyWatchers: insert new actioner: Error 1406 (22001): Data too long for column 'content' at row 1

@wxiaoguang wxiaoguang added this to the 1.24.0 milestone Apr 16, 2025
@wxiaoguang wxiaoguang added issue/critical This issue should be fixed ASAP. If it is a PR, the PR should be merged ASAP good first issue Likely to be an easy fix labels Apr 16, 2025
@lunny lunny mentioned this issue Apr 17, 2025
Merged
wxiaoguang added a commit that referenced this issue Apr 20, 2025
@lunny @wxiaoguang
Fix notify watch failure when the content is too long (#34233)
6d3c674 
Fix #28193

---------

Co-authored-by: wxiaoguang <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
good first issue Likely to be an easy fix 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.24.0
3 participants
@wxiaoguang @pboguslawski @lng2020