nickva commented on issue #3773:
URL: https://github.com/apache/couchdb/issues/3773#issuecomment-932603969
Hmm, I could not reproduce it with latest 3.x branch. Erlang 20, MacOS,
libicu 59:
```
otool -L couch_ejson_compare.so
couch_ejson_compare.so:
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current
version 1292.100.5)
/usr/local/opt/icu4c/lib/libicuuc.59.dylib (compatibility version
59.0.0, current version 59.1.0)
/usr/local/opt/icu4c/lib/libicudata.59.1.dylib (compatibility version
59.0.0, current version 59.1.0)
/usr/local/opt/icu4c/lib/libicui18n.59.dylib (compatibility version
59.0.0, current version 59.1.0)
```
I slightly tweaked your script
https://gist.github.com/nickva/e351e678fc10d3b5424de44be992703c but ensure it
still preserved the encoded values:
```
% ./collation_bug_view.sh
{"ok":true}
{"ok":true}
{"ok":true,"id":"_design/by-type-name","rev":"1-c5fc5a56efeddb94b1c3a3de0d25f7dd"}
{"ok":true,"id":"doc1","rev":"1-b269c8b395d44f4a054ad149f232886c"}
{"ok":true,"id":"doc2","rev":"1-af18b03890d4f08e8e41b720f27c11fa"}
We can see that "chaîne" is encoded one time as 69cc82, and one time as c3ae
00000000: 2020 2020 2020 2020 226e 616d 6522 3a20 "name":
00000010: 2263 6861 c3ae 6e65 220a 2020 2020 2020 "cha..ne".
00000020: 2020 226e 616d 6522 3a20 2263 6861 69cc "name": "chai.
00000030: 826e 6522 0a .ne".
Request the view, one time for each encoding
--- c h a i n e ---
{"rows":[
{"key":["file","chaîne"],"value":1}
]}
--- c h a i ^ n e ---
{"rows":[
{"key":["file","chaîne"],"value":1}
]}
Expected: 1 row in each response, but I got 2 rows in first response and 0
on the second
```
See if you can determine the version of Erlang and libicu used?
And you're definitely not using the "raw" collation option?
Another idea is to try with the the latest 3.1.1 version, perhaps different
OS...
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
