[jira] [Commented] (COUCHDB-3123) Remove / update Futon guide

2016-09-12 Thread Michelle Phung (JIRA) 

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

Michelle Phung commented on COUCHDB-3123:
-

https://github.com/apache/couchdb-documentation/pull/64

> Remove / update Futon guide
> ---
>
> Key: COUCHDB-3123
> URL: https://issues.apache.org/jira/browse/COUCHDB-3123
> Project: CouchDB
>  Issue Type: Documentation
>  Components: Documentation, Fauxton
>Reporter: Will Holley
>
> CouchDB 2 ships with a replacement for Futon, Fauxton. The Futon tutorial 
> (http://docs.couchdb.org/en/master/intro/futon.html), linked to from the 
> front page should be updated to reflect this.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (COUCHDB-3123) Remove / update Futon guide

2016-09-12 Thread Michelle Phung (JIRA) 

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

Michelle Phung commented on COUCHDB-3123:
-

PR is out: I opened a PR

> Remove / update Futon guide
> ---
>
> Key: COUCHDB-3123
> URL: https://issues.apache.org/jira/browse/COUCHDB-3123
> Project: CouchDB
>  Issue Type: Documentation
>  Components: Documentation, Fauxton
>Reporter: Will Holley
>
> CouchDB 2 ships with a replacement for Futon, Fauxton. The Futon tutorial 
> (http://docs.couchdb.org/en/master/intro/futon.html), linked to from the 
> front page should be updated to reflect this.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] couchdb-documentation pull request #64: fix Fauxton docs

2016-09-12 Thread michellephung 
GitHub user michellephung opened a pull request:

https://github.com/apache/couchdb-documentation/pull/64

fix Fauxton docs

Please check since i've never made a PR to couchdb-docs before 

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

$ git pull https://github.com/michellephung/couchdb-documentation 
Fix-Fauxton-Docs

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

https://github.com/apache/couchdb-documentation/pull/64.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 #64


commit e109982ba5f0bf6a60fd33d435d0e0eb9aa823b3
Author: michellephung 
Date:   2016-09-13T03:53:24Z

fix Fauxton docs




---
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 is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] couchdb-fauxton pull request #770: Update readme

2016-09-12 Thread robertkowalski 
GitHub user robertkowalski opened a pull request:

https://github.com/apache/couchdb-fauxton/pull/770

Update readme

 - Update outdated parts on grunt
 - fix uppercase written npm to lowercase
 - don't encourage dangerous sudo usage

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

$ git pull https://github.com/robertkowalski/couchdb-fauxton patch-1

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

https://github.com/apache/couchdb-fauxton/pull/770.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 #770


commit 3a1dd48a0526afd9a167945158797e85c73fe23a
Author: Robert Kowalski 
Date:   2016-09-13T02:52:21Z

Update readme

 - Update outdated parts on grunt
 - fix uppercase written npm to lowercase
 - don't encourage dangerous sudo usage




---
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 is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] couchdb-couch pull request #197: Fix Windows version string determination

2016-09-12 Thread asfgit 
Github user asfgit closed the pull request at:

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


---
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 is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] couchdb-couch issue #197: Fix Windows version string determination

2016-09-12 Thread rnewson 
Github user rnewson commented on the issue:

https://github.com/apache/couchdb-couch/pull/197
  
+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 not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] couchdb-couch pull request #197: Fix Windows version string determination

2016-09-12 Thread wohali 
GitHub user wohali opened a pull request:

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

Fix Windows version string determination

For some reason, the COUCHDB_VERSION string on Windows is getting
suffixed whitespace. We fix this by string:strip(Version0, right) on the
variable before use.

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

$ git pull https://github.com/wohali/couchdb-couch fix-windows-version

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

https://github.com/apache/couchdb-couch/pull/197.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 #197


commit 70b61f08618c34f4604bebc2ad2b8d71f90cca5e
Author: Joan Touzet 
Date:   2016-09-12T19:28:31Z

Fix Windows version string determination

For some reason, the COUCHD_VERSION string on Windows is getting
suffixed whitespace. We fix this by string:strip(Version0, right) on the
variable before use.




---
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 is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] couchdb-couch pull request #62: Make sure authentication_db for clustered is...

2016-09-12 Thread davisp 
Github user davisp commented on a diff in the pull request:

https://github.com/apache/couchdb-couch/pull/62#discussion_r78438428
  
--- Diff: src/couch_server.erl ---
@@ -116,12 +116,16 @@ delete(DbName, Options) ->
 maybe_add_sys_db_callbacks(DbName, Options) when is_binary(DbName) ->
 maybe_add_sys_db_callbacks(?b2l(DbName), Options);
 maybe_add_sys_db_callbacks(DbName, Options) ->
+Normalized = couch_db:normalize_dbname(DbName),
+IsShard = couch_db:is_shard(DbName),
+
 DbsDbName = config:get("mem3", "shards_db", "_dbs"),
 NodesDbName = config:get("mem3", "nodes_db", "_nodes"),
-IsReplicatorDb = DbName == config:get("replicator", "db", 
"_replicator") orelse
-   path_ends_with(DbName, <<"_replicator">>),
-IsUsersDb = DbName ==config:get("couch_httpd_auth", 
"authentication_db", "_users") orelse
-   path_ends_with(DbName, <<"_users">>),
+IsReplicatorDb = Normalized == config:get("replicator", "db", 
"_replicator") orelse
--- End diff --

As I read this, Normalized is guaranteed to be a binary, where config:get/3 
is guaranteed to be a list, so the first part of the orelse is guaranteed to be 
false.


---
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 is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] couchdb-fauxton issue #767: Check dependencies added to Fauxton build

2016-09-12 Thread garrensmith 
Github user garrensmith commented on the issue:

https://github.com/apache/couchdb-fauxton/pull/767
  
I'm closing this since @robertkowalski has some nice plugins to do this for 
us now.


---
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 is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] couchdb-fauxton pull request #767: Check dependencies added to Fauxton build

2016-09-12 Thread garrensmith 
Github user garrensmith closed the pull request at:

https://github.com/apache/couchdb-fauxton/pull/767


---
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 is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Closed] (COUCHDB-3144) Documentation for specific design document has typo

2016-09-12 Thread Steven Tseng (JIRA) 

 [ 
https://issues.apache.org/jira/browse/COUCHDB-3144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Steven Tseng closed COUCHDB-3144.
-
Resolution: Not A Problem

Work around achieved - required embedded arrays.

> Documentation for specific design document has typo
> ---
>
> Key: COUCHDB-3144
> URL: https://issues.apache.org/jira/browse/COUCHDB-3144
> Project: CouchDB
>  Issue Type: Improvement
>  Components: Documentation
>Reporter: Steven Tseng
>Priority: Trivial
>
> http://docs.couchdb.org/en/stable/api/ddoc/views.html
> {noformat}
> POST /recipes/_design/ingredients/_view/by_name HTTP/1.1
> Accept: application/json
> Content-Length: 37
> Host: localhost:5984
> {
> "keys": [  <-- Incorrect, should be "key": [
> "meatballs",
> "spaghetti"
> ]
> }
> {noformat}
> Using "keys" as the body key value, returns no rows as the current view 
> returned is based on key and value being in singular format - "key" and 
> "value"



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

2016-09-12 Thread Jan Lehnardt (JIRA) 

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

Jan Lehnardt commented on COUCHDB-3142:
---

I suggest we add this to the list of known issues.

> replication is broken in admin party
> 
>
> Key: COUCHDB-3142
> URL: https://issues.apache.org/jira/browse/COUCHDB-3142
> Project: CouchDB
>  Issue Type: Bug
>  Components: Replication
>Reporter: Robert Kowalski
>
> After replication of 4 documents in admin party I get:
> [error] 2016-09-11T13:35:44.251445Z node2@127.0.0.1 <0.9183.0>  
> Replicator: couldn't write document `spmbatch`, revision 
> `1-3d3f983c5948661dca3708b6662d9bd2`, to target database 
> `http://127.0.0.1:35984/blerg/`. Error: `forbidden`, reason: `Please log in 
> before writing to the db`.
> Which was never the case before. Replication then stalls / retries forever



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

2016-09-12 Thread Jan Lehnardt (JIRA) 

 [ 
https://issues.apache.org/jira/browse/COUCHDB-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jan Lehnardt resolved COUCHDB-3141.
---
   Resolution: Fixed
Fix Version/s: 2.0.0

fixed in linked issue

> Default Mango Query has browser memory leak
> ---
>
> Key: COUCHDB-3141
> URL: https://issues.apache.org/jira/browse/COUCHDB-3141
> Project: CouchDB
>  Issue Type: Bug
>  Components: Fauxton
>Reporter: Jan Lehnardt
> Fix For: 2.0.0
>
>
> I have a database with just over 20k docs replicated into a 2.0.0 release 
> candidate. When I navigate to the Mango screen and leave everything on 
> default, and then press the “Run Query” button, it takes maybe 30 seconds 
> before that browser tab eats up all the available RAM, I’ve confirmed this in 
> Safari, Chrome and Firefox on latest stable Mac OS X.
> I don’t know enough about Mango and whether the defaults for a query are in 
> any way useful, I just tried hitting a button to see what happens, and a 
> memory leak is not what I’ve expected ;)
> CouchDB looks like its doing fine, it’s the Browser that runs out of memory 
> *quickly* (in one instance 20GB in ~1 minute)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

2016-09-12 Thread Jan Lehnardt (JIRA) 

 [ 
https://issues.apache.org/jira/browse/COUCHDB-3143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jan Lehnardt closed COUCHDB-3143.
-
Resolution: Fixed

> Make Mango's MR index default limit match the docs
> --
>
> Key: COUCHDB-3143
> URL: https://issues.apache.org/jira/browse/COUCHDB-3143
> Project: CouchDB
>  Issue Type: Bug
>  Components: Mango
>Reporter: Paul Joseph Davis
> Fix For: 2.0.0
>
>
> We document that mango indexes return 25 rows per call by default but the 
> code had a large value to basically return unlimited. Fix is to update mango 
> to match the docs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

2016-09-12 Thread Jan Lehnardt (JIRA) 

 [ 
https://issues.apache.org/jira/browse/COUCHDB-3143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jan Lehnardt reopened COUCHDB-3143:
---

> Make Mango's MR index default limit match the docs
> --
>
> Key: COUCHDB-3143
> URL: https://issues.apache.org/jira/browse/COUCHDB-3143
> Project: CouchDB
>  Issue Type: Bug
>  Components: Mango
>Reporter: Paul Joseph Davis
> Fix For: 2.0.0
>
>
> We document that mango indexes return 25 rows per call by default but the 
> code had a large value to basically return unlimited. Fix is to update mango 
> to match the docs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

2016-09-12 Thread Jan Lehnardt (JIRA) 

 [ 
https://issues.apache.org/jira/browse/COUCHDB-3143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jan Lehnardt closed COUCHDB-3143.
-

> Make Mango's MR index default limit match the docs
> --
>
> Key: COUCHDB-3143
> URL: https://issues.apache.org/jira/browse/COUCHDB-3143
> Project: CouchDB
>  Issue Type: Bug
>  Components: Mango
>Reporter: Paul Joseph Davis
>
> We document that mango indexes return 25 rows per call by default but the 
> code had a large value to basically return unlimited. Fix is to update mango 
> to match the docs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

2016-09-12 Thread Jan Lehnardt (JIRA) 

 [ 
https://issues.apache.org/jira/browse/COUCHDB-3143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jan Lehnardt resolved COUCHDB-3143.
---
Resolution: Fixed

merged into master and 2.0.x

> Make Mango's MR index default limit match the docs
> --
>
> Key: COUCHDB-3143
> URL: https://issues.apache.org/jira/browse/COUCHDB-3143
> Project: CouchDB
>  Issue Type: Bug
>  Components: Mango
>Reporter: Paul Joseph Davis
>
> We document that mango indexes return 25 rows per call by default but the 
> code had a large value to basically return unlimited. Fix is to update mango 
> to match the docs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

2016-09-12 Thread ASF subversion and git services (JIRA) 

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

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

Commit d8432c58a004141123e13a5af6dad78e3746399d in couchdb-mango's branch 
refs/heads/master from [~paul.joseph.davis]
[ https://git-wip-us.apache.org/repos/asf?p=couchdb-mango.git;h=d8432c5 ]

Set default limit to 25

The docs claim the limit is 25 and this was the intention but this value
was never updated. The reason to set it at 25 is in case we add other
index types that are unable to stream results to the client (ie,
anything Lucene based). This allows us to maintain the same API across
all calls regardless of index type used.

COUCHDB-3143


> Make Mango's MR index default limit match the docs
> --
>
> Key: COUCHDB-3143
> URL: https://issues.apache.org/jira/browse/COUCHDB-3143
> Project: CouchDB
>  Issue Type: Bug
>  Components: Mango
>Reporter: Paul Joseph Davis
>
> We document that mango indexes return 25 rows per call by default but the 
> code had a large value to basically return unlimited. Fix is to update mango 
> to match the docs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

2016-09-12 Thread ASF subversion and git services (JIRA) 

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

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

Commit 29b59449dffea83470ec5c828a8ab2e8c6504a65 in couchdb-mango's branch 
refs/heads/master from [~paul.joseph.davis]
[ https://git-wip-us.apache.org/repos/asf?p=couchdb-mango.git;h=29b5944 ]

Fix test suite check for text indexes

This was passing by accident on travis because the $CWD is set
differently so the test would always fail. If however you tried to run
the tests locally then it would fail. Obviously the test is just wrong
since we're moving the mango_cursor_text.erl file in rebar.config, and
not mango_cursor.erl which is required for every index type.

COUCHDB-3143


> Make Mango's MR index default limit match the docs
> --
>
> Key: COUCHDB-3143
> URL: https://issues.apache.org/jira/browse/COUCHDB-3143
> Project: CouchDB
>  Issue Type: Bug
>  Components: Mango
>Reporter: Paul Joseph Davis
>
> We document that mango indexes return 25 rows per call by default but the 
> code had a large value to basically return unlimited. Fix is to update mango 
> to match the docs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (COUCHDB-3144) Documentation for specific design document has typo

2016-09-12 Thread Steven Tseng (JIRA) 
Steven Tseng created COUCHDB-3144:
-

 Summary: Documentation for specific design document has typo
 Key: COUCHDB-3144
 URL: https://issues.apache.org/jira/browse/COUCHDB-3144
 Project: CouchDB
  Issue Type: Improvement
  Components: Documentation
Reporter: Steven Tseng


http://docs.couchdb.org/en/stable/api/ddoc/views.html
{noformat}
POST /recipes/_design/ingredients/_view/by_name HTTP/1.1
Accept: application/json
Content-Length: 37
Host: localhost:5984

{
"keys": [  <-- Incorrect, should be "key": [
"meatballs",
"spaghetti"
]
}
{noformat}

Using "keys" as the body key value, returns no rows as the current view 
returned is based on key and value being in singular format - "key" and "value"



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

2016-09-12 Thread Jan Lehnardt (JIRA) 

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

Jan Lehnardt commented on COUCHDB-3142:
---

I can replicate (rimshot) Robert’s report:

[error] 2016-09-12T06:03:39.142197Z couchdb@localhost <0.1033.0>  
Replicator: couldn't write document `weibo-oauth2`, revision 
`1-8a5939da7525a316d10aeec5f33e951f`, to target database 
`http://127.0.0.1:5984/skimdb2/`. Error: `forbidden`, reason: `Please log in 
before writing to the db`.

When replicating https://skimdb.npmjs.com/registry into a local database on 
Admin Party.

> replication is broken in admin party
> 
>
> Key: COUCHDB-3142
> URL: https://issues.apache.org/jira/browse/COUCHDB-3142
> Project: CouchDB
>  Issue Type: Bug
>  Components: Replication
>Reporter: Robert Kowalski
>
> After replication of 4 documents in admin party I get:
> [error] 2016-09-11T13:35:44.251445Z node2@127.0.0.1 <0.9183.0>  
> Replicator: couldn't write document `spmbatch`, revision 
> `1-3d3f983c5948661dca3708b6662d9bd2`, to target database 
> `http://127.0.0.1:35984/blerg/`. Error: `forbidden`, reason: `Please log in 
> before writing to the db`.
> Which was never the case before. Replication then stalls / retries forever



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)