- [xC2xABxD0x9DxD0xBExD0xB2xD0xB0xD1x8F xD0x9CxD0xBExD1x81xD0xBAxD0xB2xD0xB0xC2xBB - xD1x84xD0xB8xD0xBBxD0xB8xD0xB0xD0xBB xD0x9ExD0x90xD0x9E xC2xABxD0x9CxD0x9ExD0xADxD0xA1xD0x9AxC2xBB xD0xB8xD0xBDxD1x84xD0xBExD1x80xD0xBCxD0xB8xD1x80xD1x83xD0xB5xD1x82, xD1x87xD1x82xD0xBE xD1x81xD0xB2xD1x8FxD0xB7xD0xB8 xD1x81 xD1x82xD0xB5xD1x85xD0xBDxD0xBExD0xBBxD0xBExD0xB3xD0xB8xD1x87xD0xB5xD1x81xD0xBAxD0xBExD0xB9 xD0xB0xD0xB2xD0xB0xD1x80xD0xB8xD0xB5xD0xB9 xD0xB2 xD1x8DxD0xBBxD0xB5xD0xBAxD1x82xD1x80xD0xB8xD1x87xD0xB5xD1x81xD0xBAxD0xBExD0xB9 xD1x81xD0xB5xD1x82xD0xB8, xD0xB2 xD0xBDxD0xB0xD1x81xD0xB5xD0xBBxD0xB5xD0xBDxD0xBDxD0xBExD0xBC xD0xBFxD1x83xD0xBDxD0xBAxD1x82xD0xB5 xD0xA2xD0xB5xD1x81xD1x82xD0xBExD0xB2xD0xBExD0xB5 xD0xBFxD0xBExD1x81xD0xB5xD0xBBxD0xB5xD0xBDxD0xB8xD0xB5 !! xD0xB2xD1x80xD0xB5xD0xBCxD0xB5xD0xBDxD0xBDxD0xBE xD0xBFxD1x80xD0xB8xD0xBExD1x81xD1x82xD0xB0xD0xBDxD0xBExD0xB2xD0xBBxD0xB5xD0xBDxD0xB0 xD0xBFxD0xBExD0xB4xD0xB0xD1x87xD0xB0 xD1x8DxD0xBBxD0xB5xD0xBAxD1x82xD1x80xD0xBExD1x8DxD0xBDxD0xB5xD1x80xD0xB3xD0xB8xD0xB8. xD0x9CxD0xB5xD1x81xD1x82xD0xBE xD0xBFxD0xBExD0xB2xD1x80xD0xB5xD0xB6xD0xB4xD0xB5xD0xBDxD0xB8xD1x8F xD1x83xD1x81xD1x82xD0xB0xD0xBDxD0xBExD0xB2xD0xBBxD0xB5xD0xBDxD0xBE, xD0xBDxD0xB0xD0xBFxD1x80xD0xB0xD0xB2xD0xBBxD0xB5xD0xBDxD0xB0 xD0xB1xD1x80xD0xB8xD0xB3xD0xB0xD0xB4xD0xB0. xD0x9FxD1x80xD0xB8xD0xBDxD0xBExD1x81xD0xB8xD0xBC xD0xB8xD0xB7xD0xB2xD0xB8xD0xBDxD0xB5xD0xBDxD0xB8xD1x8F xD0xB7xD0xB0 xD0xB4xD0xBExD1x81xD1x82xD0xB0xD0xB2xD0xBBxD0xB5xD0xBDxD0xBDxD1x8BxD0xB5 xD0xBDxD0xB5xD1x83xD0xB4xD0xBExD0xB1xD1x81xD1x82xD0xB2xD0xB0. xD0xA2xD0xB5xD0xBBxD0xB5xD1x84xD0xBExD0xBD xD0xB4xD0xB8xD1x81xD0xBFxD0xB5xD1x82xD1x87xD0xB5xD1x80xD1x81xD0xBAxD0xBExD0xB9 xD1x81xD0xBBxD1x83xD0xB6xD0xB1xD1x8B 8-800-700-40-70 (xD0xB7xD0xB2xD0xBExD0xBDxD0xBExD0xBA xD0xB1xD0xB5xD1x81xD0xBFxD0xBBxD0xB0xD1x82xD0xBDxD1x8BxD0xB9).
Fixed issue with malformed UTF-8 string. Fixed issue with malformed UTF-8 string. Skip to content. Features → Code review.
Defect #19550
Issue query: crash when processing saved query(filters) with cyrillic after upgrade to 3.0 from 2.*
Status: | Closed | Start date: | |
---|---|---|---|
Priority: | Normal | Due date: | |
Assignee: | - | % Done: | 0% |
Category: | Issues | ||
Target version: | - | ||
Resolution: | Wont fix | Affected version: | 3.0.0 |
Description
After updrading from 2 to 3 version I've found a bug.
Some if saved custom queries have become broken. Those that have enumeration of values in filter with cyrillic symbols. I've attached some information from log.
When I create new custom query at 3.0 version in works properly.
When I create new custom query at 3.0 version in works properly.
query_with_ciryllic.txt(1.59 KB)
rails.log(1.2 KB)
about_env.txt(584 Bytes)
mysql_encoding_info.txt(3.32 KB)
queries.filters_new_without_error.txt - do not works (607 Bytes)
queries.filters_old_with_error.txt - works (1.02 KB)
History
#1 Updated by Toshi MARUYAMAalmost 5 years ago
- Status changed from New to Needs feedback
#2 Updated by Pavel Liavonaualmost 5 years ago
- Fileabout_env.txt added
Added output of about script. What else do you need?
#3 Updated by Toshi MARUYAMAalmost 5 years ago
Check your MySQL setting and characters.
http://www.redmine.org/boards/1/topics/36573?r=36587#message-36587
http://www.redmine.org/boards/1/topics/36573?r=36587#message-36587
#4 Updated by Pavel Liavonaualmost 5 years ago
- Filemysql_encoding_info.txt added
Attached output of mysql character set information. What can you advice me to do?
#5 Updated by Toshi MARUYAMAalmost 5 years ago
- Status changed from Needs feedback to Closed
- Resolution set to Invalid
You need to set 'UTF-8' for all MySQL setting.
http://www.redmine.org/boards/1/topics/36573?r=36629#message-36629
And you need to convert all MySQL data from latin1 to UTF-8.
http://www.redmine.org/boards/2/topics/35979?r=36082#message-36082
http://www.redmine.org/boards/1/topics/36573?r=36629#message-36629
And you need to convert all MySQL data from latin1 to UTF-8.
http://www.redmine.org/boards/2/topics/35979?r=36082#message-36082
#6 Updated by Pavel Liavonauover 4 years ago
- Filequeries.filters_new_without_error.txt added
- Filequeries.filters_old_with_error.txt added
- Status changed from Closed to Reopened
Your advice has not helped me.
My all settings are now only for UTF-8, but error still occures.
It is the bug. Admit it.
Conversion of dump don't help because the problem is at queries.filters column.
I've added 2 files with content of this column for not old not working query and new created with the same functionality.
Look: old format is 'binary' but new is not.
So, fix it, or propose me script that converts queries.filters field properly.
My all settings are now only for UTF-8, but error still occures.
It is the bug. Admit it.
Conversion of dump don't help because the problem is at queries.filters column.
I've added 2 files with content of this column for not old not working query and new created with the same functionality.
Look: old format is 'binary' but new is not.
So, fix it, or propose me script that converts queries.filters field properly.
Thanks.
#7 Updated by Toshi MARUYAMAover 4 years ago
- Status changed from Reopened to Closed
- Resolution changed from Invalid to Wont fix
Pavel Liavonau wrote:
Look: old format is 'binary' but new is not.
Old format is Ruby 1.8 yaml format.
http://stackoverflow.com/questions/7576500/ruby-1-8-7-why-to-yaml-converts-some-strings-to-non-readable-bytes
http://stackoverflow.com/questions/7576500/ruby-1-8-7-why-to-yaml-converts-some-strings-to-non-readable-bytes
It is the bug. Admit it.
It is not bug.
I don't know your old yaml data.
I think it is saved in non UTF-8.
I don't know your old yaml data.
I think it is saved in non UTF-8.
Redmine treat yaml data as UTF-8 nevertheless it is Ruby 1.8 yaml data or not.
source:tags/3.0.3/app/models/custom_field.rb#L121
source:tags/3.0.3/app/models/custom_field.rb#L121
We cannot support in your case such as database encoding was not UTF-8.
You need to convert yaml data manually.
You need to convert yaml data manually.
#8 Updated by Toshi MARUYAMAover 4 years ago
Toshi MARUYAMA wrote:
I don't know your old yaml data.
I think it is saved in non UTF-8.
I think it is saved in non UTF-8.
It seems your yaml is UTF-8.
But I don't know your all Ruby 1.8 yaml is UTF-8.
But I don't know your all Ruby 1.8 yaml is UTF-8.
#9 Updated by Pavel Liavonauover 4 years ago
Toshi MARUYAMA wrote:
It seems your yaml is UTF-8.
But I don't know your all Ruby 1.8 yaml is UTF-8.
But I don't know your all Ruby 1.8 yaml is UTF-8.
what do you mean?
If it is UTF-8 already, what can I do now? I am not so strong in Ruby to write conversion script by myself.
I use ruby ruby 1.9.3p484 (2013-11-22 revision 43786) [x86_64-linux].
#10 Updated by Toshi MARUYAMAover 4 years ago
Pavel Liavonau wrote:
Toshi MARUYAMA wrote:
It seems your yaml is UTF-8.
But I don't know your all Ruby 1.8 yaml is UTF-8.
But I don't know your all Ruby 1.8 yaml is UTF-8.
what do you mean?
#11 Updated by Pavel Liavonauover 4 years ago
Ок. I see.
It is hard to create universal script for migration from ruby 1.8 to new versions.
This queries are not important for me and I've just deleted them with a sql query.
It is hard to create universal script for migration from ruby 1.8 to new versions.
This queries are not important for me and I've just deleted them with a sql query.
delete * from queries where filters like '%binary%';
Thank you very much for answering.
Also available in: AtomPDF