[ 
https://issues.apache.org/jira/browse/COUCHDB-3415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16044632#comment-16044632
 ] 

ASF subversion and git services commented on COUCHDB-3415:
----------------------------------------------------------

Commit aca0693a5a0767254c5d5146b44fac6fba339f7f in couchdb's branch 
refs/heads/2.1.x from [~paul.joseph.davis]
[ https://gitbox.apache.org/repos/asf?p=couchdb.git;h=aca0693 ]

Account for extra newlines in response body

The timeout=1 (1ms) parameter would some times trigger extra newlines to be
included in the response body. The use of `binary:split/2` would then
return different portions of the body depending on timing in the
cluster. This change adds a helper function to split out all newlines in
the response and then returns the last non-empty line.

This also removes introspection of the clustered update sequence since
this is an HTTP API behavior tests and those are defined as opaque
values.

COUCHDB-3415


> EUnit: should_accept_live_as_an_alias_for_continuous invalid_trailing_data
> --------------------------------------------------------------------------
>
>                 Key: COUCHDB-3415
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-3415
>             Project: CouchDB
>          Issue Type: Bug
>          Components: Test Suite
>            Reporter: Joan Touzet
>
> New bug. Seen once in Travis, Erlang 17.5. Re-running caused the error to 
> disappear.
> {noformat}
> module 'chttpd_db_test'
>   chttpd db tests
>     chttpd_db_test:71: should_return_ok_true_on_bulk_update...[0.073 s] ok
>     chttpd_db_test:86: 
> should_accept_live_as_an_alias_for_continuous...*failed*
> in function couch_util:json_decode/1 (src/couch_util.erl, line 414)
> in call from 
> chttpd_db_test:'-should_accept_live_as_an_alias_for_continuous/1-fun-1-'/1 
> (test/chttpd_db_test.erl, line 98)
> **throw:{invalid_json,{error,{257,invalid_trailing_data}}}
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to