#804  length of o_content field in GpgKey table isn't long enough
Released
Sassan opened 2 years ago

Hi Guys

I got the following error during the upgrade procedure when using MySQL as external database

(conn=12724) Data too long for column 'o_content' at row 1

please notice this bug occurred when I imported too long a GPG signing key.

my temporary solution is to change the type of this field to Text (it was varchar(5000) )

Robin Shen commented 2 years ago

How long is your GPG key?

Sassan commented 2 years ago

$ gpg --armor --export inbox@sassan.info|wc 
    232     239   14847
OneDev changed state to 'Closed' 2 years ago
Previous Value Current Value
Open
Closed
OneDev commented 2 years ago

State changed as code fixing the issue is committed

OneDev changed state to 'Released' 2 years ago
Previous Value Current Value
Closed
Released
OneDev commented 2 years ago

State changed as build #2820 is successful

issue 1 of 1
Type
Bug
Priority
Minor
Assignee
Affected Versions
Not Found
Issue Votes (0)
Watchers (4)
Reference
onedev/server#804
Please wait...
Page is in error, reload to recover