[jira] [Commented] (COUCHDB-3141) Default Mango Query has browser memory leak

2016-09-11 Thread Robert Kowalski (JIRA)
[ https://issues.apache.org/jira/browse/COUCHDB-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15482867#comment-15482867 ] Robert Kowalski commented on COUCHDB-3141: -- mango issue in

[jira] [Created] (COUCHDB-3143) Make Mango's MR index default limit match the docs

2016-09-11 Thread Paul Joseph Davis (JIRA)
Paul Joseph Davis created COUCHDB-3143: -- Summary: Make Mango's MR index default limit match the docs Key: COUCHDB-3143 URL: https://issues.apache.org/jira/browse/COUCHDB-3143 Project: CouchDB

[jira] [Created] (COUCHDB-3142) replication is broken in admin party

2016-09-11 Thread Robert Kowalski (JIRA)
Robert Kowalski created COUCHDB-3142: Summary: replication is broken in admin party Key: COUCHDB-3142 URL: https://issues.apache.org/jira/browse/COUCHDB-3142 Project: CouchDB Issue Type:

[jira] [Commented] (COUCHDB-3141) Default Mango Query has browser memory leak

2016-09-11 Thread Robert Kowalski (JIRA)
[ https://issues.apache.org/jira/browse/COUCHDB-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15481783#comment-15481783 ] Robert Kowalski commented on COUCHDB-3141: -- verified that the mango query returns all docs and

[jira] [Commented] (COUCHDB-3142) replication is broken in admin party

2016-09-11 Thread Joan Touzet (JIRA)
[ https://issues.apache.org/jira/browse/COUCHDB-3142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15481826#comment-15481826 ] Joan Touzet commented on COUCHDB-3142: -- Cannot replicate. I set up my CouchDB WIndows RC4 instance

[jira] [Commented] (COUCHDB-3142) replication is broken in admin party

2016-09-11 Thread Joan Touzet (JIRA)
[ https://issues.apache.org/jira/browse/COUCHDB-3142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15483075#comment-15483075 ] Joan Touzet commented on COUCHDB-3142: -- OK, after dropping Fauxton and going straight to curl, I

[jira] [Commented] (COUCHDB-3142) replication is broken in admin party

2016-09-11 Thread Joan Touzet (JIRA)
[ https://issues.apache.org/jira/browse/COUCHDB-3142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15483087#comment-15483087 ] Joan Touzet commented on COUCHDB-3142: -- Note: {noformat} E:\relax\couchdb>grep -r "Please log in"

[jira] [Commented] (COUCHDB-3141) Default Mango Query has browser memory leak

2016-09-11 Thread Robert Kowalski (JIRA)
[ https://issues.apache.org/jira/browse/COUCHDB-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15481720#comment-15481720 ] Robert Kowalski commented on COUCHDB-3141: -- >From thinking about it it seems that the prefilled

[GitHub] couchdb-couch pull request #196: Disable should_process_waiting_queue_as_fif...

2016-09-11 Thread wohali
GitHub user wohali opened a pull request: https://github.com/apache/couchdb-couch/pull/196 Disable should_process_waiting_queue_as_fifo test COUCHDB-3140 This PR disables the problematic queue-as-fifo test. As written, any call in a test to spawn_client/1 returns

[jira] [Commented] (COUCHDB-3140) couchdb_os_proc_pool tests fail on Windows

2016-09-11 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/COUCHDB-3140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15481184#comment-15481184 ] ASF GitHub Bot commented on COUCHDB-3140: - GitHub user wohali opened a pull request:

[jira] [Commented] (COUCHDB-3140) couchdb_os_proc_pool tests fail on Windows

2016-09-11 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/COUCHDB-3140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15481186#comment-15481186 ] ASF GitHub Bot commented on COUCHDB-3140: - Github user wohali closed the pull request at:

[GitHub] couchdb-couch issue #195: Bypass couchdb_os_proc_pool tests on Windows

2016-09-11 Thread wohali
Github user wohali commented on the issue: https://github.com/apache/couchdb-couch/pull/195 Please see https://github.com/apache/couchdb-couch/pull/196. I am closing this PR. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as

[GitHub] couchdb-couch pull request #195: Bypass couchdb_os_proc_pool tests on Window...

2016-09-11 Thread wohali
Github user wohali closed the pull request at: https://github.com/apache/couchdb-couch/pull/195 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature

[GitHub] couchdb-couch issue #196: Disable should_process_waiting_queue_as_fifo test

2016-09-11 Thread wohali
Github user wohali commented on the issue: https://github.com/apache/couchdb-couch/pull/196 For reference, disabling this one test allows the subsequent test in the suite (should_reduce_pool_on_idle_os_procs) to pass on Windows, so it's just this one test that is a problem. --- If

[jira] [Commented] (COUCHDB-3140) couchdb_os_proc_pool should_process_waiting_queue_as_fifo test fails on Windows

2016-09-11 Thread Joan Touzet (JIRA)
[ https://issues.apache.org/jira/browse/COUCHDB-3140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15481200#comment-15481200 ] Joan Touzet commented on COUCHDB-3140: -- For reference, disabling this one test allows the

[GitHub] couchdb-couch issue #196: Disable should_process_waiting_queue_as_fifo test

2016-09-11 Thread rnewson
Github user rnewson commented on the issue: https://github.com/apache/couchdb-couch/pull/196 nice find and way better than disabling the whole file. +1 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does

[GitHub] couchdb-couch pull request #196: Disable should_process_waiting_queue_as_fif...

2016-09-11 Thread asfgit
Github user asfgit closed the pull request at: https://github.com/apache/couchdb-couch/pull/196 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature