couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sam Rijs (JIRA)" <>
Subject [jira] [Commented] (COUCHDB-1425) Emitting UTF-8 chars >= 0xD800 in JS map stops design doc from indexing
Date Wed, 06 Mar 2013 12:22:13 GMT


Sam Rijs commented on COUCHDB-1425:

I tried to add a simple test case and ran it against the patched couch_js.
However, rspec is failing:

  1) query server normal case should sanitize wrong utf8 emits
     Failure/Error: raise "no response"
       no response
     # ./query_server_spec.rb:111:in `jsgets'
     # ./query_server_spec.rb:76:in `run'
     # ./query_server_spec.rb:525:in `block (2 levels) in <top (required)>'

This is the testcase under -- describe "query server normal case" do

  it "should sanitize wrong utf8 emits" do
    @qs.reset!["add_fun", functions["emit-once"][LANGUAGE]]).should == true
    rows =["map_doc", {:a => "\xd8\x00"}])
    rows[0][0].should == ["baz", "\xff\xfd"]

Is the testcase wrong, or have I hit an edge case where the error still persists?
> Emitting UTF-8 chars >= 0xD800 in JS map stops design doc from indexing
> -----------------------------------------------------------------------
>                 Key: COUCHDB-1425
>                 URL:
>             Project: CouchDB
>          Issue Type: Bug
>          Components: JavaScript View Server
>    Affects Versions: 1.1.1
>         Environment: Mac OS 10.6.8, but not sure that matters.
>            Reporter: Jim Klo
>         Attachments: utf8.c.diff
> Was trying determine UTF-8 Char collation, using the following Gist:
> It turns out that once the view gets to the document that would emit "\uD800", the view
server times out and stops indexing that design document.
> This seems like a bug, since I can 'store' a document with UTF-8 chars >= 0xD800,
but one cannot emit a key with that char in the string.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message