-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
Language column in language_stat table is too small (needs to be at least 34) #12379
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
Comments
@somera are there really no other lines there? That pq log looks very difficult to read. I'd also turn off stacktrace logging it's just not useful in general. |
Is there a connection to #12380? I see this after Gitea (re)start prozess:
|
You are likely seeing the logging in #12380 because this is failing - #12380 is not a really a problem and I've proposed a PR to suggest that that logging goes down to Debug level. The issue here is that the language of at least one of your files has been detected as That is clearly > 30 characters - which is then caused postgres to report: I don't know much about the language stats detector but have you explicitly added types etc? |
Which types? Where? PostgreSQL? My PostgreSQL 11 is default installation without any special exensions. |
OK it looks like As a fix for you right now: In Postgres do: or even set it to |
In go-gitea#12379 it was discovered that enry v2 has a maximum language length of 34 characters which is larger than the 30 previously provided. This PR updates the language column to 50. Fix go-gitea#12379 Signed-off-by: Andrew Thornton <[email protected]>
[x]
):Enry v2 can detect languages with names longer than the currently provided maximum of 30 characters.
A quick look at Enry's source code demonstrates that the current maximum length for a detected language is 34 characters (see below code).
We therefore need to provide a migration to increase the size of this column or consider forcibly shortening Enry's detected language.
The text was updated successfully, but these errors were encountered: