wojtek opened 11 months ago
|
|||||
less: vim |
|||||
1dev 7.9.3: |
|||||
Upgrading to latest 8.2.6 yields the same problem. I'm not sure that info at the end:
Would change anything. |
|||||
Btw. what is the recommended option for HA to avoid crash / system downtime? |
|||||
Seems that some characters in your database are treated as invalid chars in XML. Can you please attach |
|||||
Robin Shen changed confidential 11 months ago
|
|||||
I have changed the issue as confidential so that no one else can see the file. |
|||||
This feature is already in EE version, which will be released in the end of this year. |
|||||
As said earlier it's unicode symbol U+FFFF which is invalid. Oddly enough 1dev doesn't accept it in the comment (it got into 1dev via import). Here's the short/cut file with single line as it doesn't make sense to upload complete file... Could you give more information about the EE version? Any link to ticket? |
|||||
OneDev changed state to 'Closed' 11 months ago
|
|||||
State changed as code fixing the issue is committed (8c830375) |
|||||
Robin Shen changed confidential 11 months ago
|
|||||
OneDev changed state to 'Released' 11 months ago
|
|||||
State changed as build #3659 is successful |
|||||
You may restore the backup with 8.2.7 to get around the issue. |
|||||
Features currently included in EE version:
|
|||||
Thank you. I took a look at the commit and it seems to fix the issue, though to avoid data-loss - could we maybe replace invalid string with string representation akin vim's: <00ffff>? Or like in the exception message: Context - it was a bug report, so we fixed it but we knew what the character was.
Thanks. I assume those EE would stand for Enterprise Edition? |
|||||
I tried
But it failed with the same exception:
|
Type |
Bug
|
Priority |
Normal
|
Assignee | |
Affected Versions |
7.9.12
|
I tried to upgrade 7.9.3->7.9.12 (I'm aware that there are newer versions, but I intended to avoid jumping too much) and it result in following exception:
I get the backup file, extracted the files and checked
Issues.xml.6
file, and the mentioned line has this (view invim
):I'm going to try to upgrade to the latest version, but considering there wasn't any similar issue it will probably still happen.