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

ASF GitHub Bot commented on COUCHDB-3316:
-----------------------------------------

GitHub user nickva opened a pull request:

    https://github.com/apache/couchdb-couch/pull/231

    Fix `badarith` error in couch_db:get_db_info call

    When folding we account for a previous `null`, `undefined`, or a number. 
However
    btree:size/1 returns 0, `nil` or a number.
    
    Switched `undefined` to `nil`. Couldn't find where btree:size would ever 
return
    `undefined`, it seems we meant to use `nil` instead.
    
    COUCHDB-3316

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/cloudant/couchdb-couch couchdb-3316

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/couchdb-couch/pull/231.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #231
    
----
commit 63ef337475a266379c7208f52f827980e69d1d1b
Author: Nick Vatamaniuc <[email protected]>
Date:   2017-03-03T02:24:52Z

    Fix `badarith` error in couch_db:get_db_info call
    
    When folding we account for a previous `null`, `undefined`, or a number. 
However
    btree:size/1 returns 0, `nil` or a number.
    
    Switched `undefined` to `nil`. Couldn't find where btree:size would ever 
return
    `undefined`, it seems we meant to use `nil` instead.
    
    COUCHDB-3316

----


> Log replicator db name not just doc ids
> ---------------------------------------
>
>                 Key: COUCHDB-3316
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-3316
>             Project: CouchDB
>          Issue Type: Improvement
>            Reporter: Nick Vatamaniuc
>
> Currently replicator logs only doc_id. However in 2.0 there could be more 
> than one _replicator db. So for logs to be useful it would be nice to log the 
> db as well.



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

Reply via email to