date:20170705

[Jenkins] FAILURE: CouchDB » master #57

2017-07-05 Thread Apache Jenkins Server

Boo, we failed. https://builds.apache.org/job/CouchDB/job/master/57/

[GitHub] eiri commented on issue #645: [WIP] Pass db open options in fabric_view_map

2017-07-05 Thread git

eiri commented on issue #645: [WIP] Pass db open options in fabric_view_map
URL: https://github.com/apache/couchdb/pull/645#issuecomment-313237324
 
 
   End-points `_list` and `_show` are not working on `_users` as well. `_show` 
because of the missing user context and `_list` because it is using not `#vacc` 
record as an acc for `query_view` and crashing on request. So this fix needs a 
bit different approach, changing PR on WIP for now.
 

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] eiri commented on issue #648: Fix couch_replicator_changes_reader:process_change

2017-07-05 Thread git

eiri commented on issue #648: Fix couch_replicator_changes_reader:process_change
URL: https://github.com/apache/couchdb/pull/648#issuecomment-313266084
 
 
   +1
 

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] iilyak opened a new pull request #648: Fix couch_replicator_changes_reader:process_change

2017-07-05 Thread git

iilyak opened a new pull request #648: Fix 
couch_replicator_changes_reader:process_change
URL: https://github.com/apache/couchdb/pull/648
 
 
   ## Overview
   
   The size of the tuple was changed in all clauses of process_change but one.
   Remove TS argument from `#doc_info{id = <<>>}` clause of process_change.
   
   ## Testing recommendations
   
   make eunit 
   
   ## Checklist
   
   - [x] Code is written and works correctly;
   - [ ] Changes are covered by tests;
   - [ ] Documentation reflects the changes;
   
 

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] iilyak commented on issue #648: Fix couch_replicator_changes_reader:process_change

2017-07-05 Thread git

iilyak commented on issue #648: Fix 
couch_replicator_changes_reader:process_change
URL: https://github.com/apache/couchdb/pull/648#issuecomment-313255711
 
 
   This is a fixup for 
https://github.com/apache/couchdb/commit/571a2fc0b7445df0f6ad4626f6172bfe6c8c9a7c
 

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] wohali commented on issue #642: Build pipeline and package build tasks

2017-07-05 Thread git

wohali commented on issue #642: Build pipeline and package build tasks
URL: https://github.com/apache/couchdb/issues/642#issuecomment-313239888
 
 
   If all of this hits, also complete 
https://github.com/apache/couchdb-documentation/issues/141
 

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] wohali opened a new issue #141: Include pointers to alternative installation mechanisms

2017-07-05 Thread git

wohali opened a new issue #141: Include pointers to alternative installation 
mechanisms
URL: https://github.com/apache/couchdb-documentation/issues/141
 
 
   * When ready, add references to FreeBSD/NetBSD, Windows packages, Docker, 
etc.
   * When ready, add callouts to the new packages for Debian, Ubuntu, CentOS 
and snaps
   * List these above the "Compiling from source" section.
 

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] wohali commented on issue #134: Improve installation and initial setup documentation

2017-07-05 Thread git

wohali commented on issue #134: Improve installation and initial setup 
documentation
URL: 
https://github.com/apache/couchdb-documentation/issues/134#issuecomment-313239026
 
 
   (2) is landed. I am closing this and opening a new issue for (3).
 

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] wohali closed issue #134: Improve installation and initial setup documentation

2017-07-05 Thread git

wohali closed issue #134: Improve installation and initial setup documentation
URL: https://github.com/apache/couchdb-documentation/issues/134
 
 
   
 

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] wohali commented on issue #134: Improve installation and initial setup documentation

2017-07-05 Thread git

wohali commented on issue #134: Improve installation and initial setup 
documentation
URL: 
https://github.com/apache/couchdb-documentation/issues/134#issuecomment-313238337
 
 
   (1) is done. (2) will land shortly. (3) I will split into a new issue.
 

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] wohali commented on issue #620: POST and ETag header

2017-07-05 Thread git

wohali commented on issue #620: POST and ETag header
URL: https://github.com/apache/couchdb/issues/620#issuecomment-313237534
 
 
   I'm closing this one as "works as designed" assuming that 
apache/couchdb-documentation#139 will hit in the next day or two.
 

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[Jenkins] FAILURE: CouchDB » master #56

2017-07-05 Thread Apache Jenkins Server

Boo, we failed. https://builds.apache.org/job/CouchDB/job/master/56/

[GitHub] wohali commented on issue #548: [Jenkins] 500 error on getting view output

2017-07-05 Thread git

wohali commented on issue #548: [Jenkins] 500 error on getting view output
URL: https://github.com/apache/couchdb/issues/548#issuecomment-313230957
 
 
   OK, see #647 for the continuation to this bug. I am closing this one out for 
now, unless we see repeats of this pop up in test runs.
   
   Thanks everyone! ? ? ? 
 

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] wohali closed issue #548: [Jenkins] 500 error on getting view output

2017-07-05 Thread git

wohali closed issue #548: [Jenkins] 500 error on getting view output
URL: https://github.com/apache/couchdb/issues/548
 
 
   
 

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] wohali opened a new issue #647: Race condition with ddoc deletion/recreation with same signature

2017-07-05 Thread git

wohali opened a new issue #647: Race condition with ddoc deletion/recreation 
with same signature
URL: https://github.com/apache/couchdb/issues/647
 
 
   See #548 for the history on this one. Quoting @kocolosk on how our test 
suite worked prior to #646 landing:
   
   > In many cases we have consecutive invocations where the ddocs have the 
same computed signature. It looks like we're hitting a race condition where we 
request to delete a ddoc, the server starts closing all the associated indexes, 
we create a new one with the same sig, the coordinator grabs an Fd from the 
cache with that sig, and the Fd is closed underneath it during the response.
   
   And to motivate continued work on this:
   
   > I think it is possible to observe this bug in normal operations, 
especially if a user is following the best practice around ddoc upgrades. 
Deleting the temporary ddoc after migrating the main one could easily kill any 
in-progress view responses.
   
   ## Expected Behaviour
   Deleting, then recreating a ddoc with the same body (and thus the same 
computed signature) should not hit a race condition where the newly created 
ddoc indexes get reaped by the previously invoked ddoc deletion - especially 
when following the CouchDB best practice around ddoc upgrades in production 
environments.
   
   ## Current Behaviour
   See the overview above.
   
   ## Steps to Reproduce (for bugs)
   Wind your repository back prior to #646 landing and run the 
`reduce_builtin.js` test suite in a loop.
   We should write a new test harness for just this bug, should be easy to hit 
if we do so from within Erlang, for instance.
   
 

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] iilyak commented on a change in pull request #538: Catch Database Do Not Exist Error

2017-07-05 Thread git

iilyak commented on a change in pull request #538: Catch Database Do Not Exist 
Error
URL: https://github.com/apache/couchdb/pull/538#discussion_r125760158
 
 

 ##
 File path: src/mem3/src/mem3_sync_security.erl
 ##
 @@ -44,10 +44,20 @@ maybe_sync_int(#shard{name=Name}=Src, Dst) ->
 
 go() ->
 {ok, Dbs} = fabric:all_dbs(),
-lists:foreach(fun handle_db/1, Dbs).
+lists:foreach(fun handle_existing_db/1, Dbs).
 
 go(DbName) when is_binary(DbName) ->
-handle_db(DbName).
+handle_existing_db(DbName).
+
+handle_existing_db(DbName) ->
+try handle_db(DbName) of
+_ -> ok
+catch
+error:database_does_not_exist->
+couch_log:error("Db was deleted while getting security"
 
 Review comment:
   @tonysun83: Agree. Let's keep it error. However please add DbName to the 
message. 
 

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] iilyak commented on issue #615: Annotate important processes

2017-07-05 Thread git

iilyak commented on issue #615: Annotate important processes
URL: https://github.com/apache/couchdb/pull/615#issuecomment-313229321
 
 
   I am glad I opened the PR for discussion prior to any significant work
 

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] iilyak closed pull request #615: Annotate important processes

2017-07-05 Thread git

iilyak closed pull request #615: Annotate important processes
URL: https://github.com/apache/couchdb/pull/615
 
 
   
 

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] kocolosk commented on issue #548: [Jenkins] 500 error on getting view output

2017-07-05 Thread git

kocolosk commented on issue #548: [Jenkins] 500 error on getting view output
URL: https://github.com/apache/couchdb/issues/548#issuecomment-313228860
 
 
   Not a blocker. We should write a solid reproducible test case for it (should 
be easy enough in EUnit right?) and address it, but agree it's difficult.
   
   I think it is possible to observe this bug in normal operations, especially 
if a user is following the best practice around ddoc upgrades. Deleting the 
temporary ddoc after migrating the main one could easily kill any in-progress 
view responses.
 

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] kocolosk commented on issue #646: Make map functions distinct with each invocation

2017-07-05 Thread git

kocolosk commented on issue #646: Make map functions distinct with each 
invocation
URL: https://github.com/apache/couchdb/pull/646#issuecomment-313228301
 
 
   Yes, thanks. This is exactly the sort of thing I had in mind for #548 
 

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] eiri commented on issue #548: [Jenkins] 500 error on getting view output

2017-07-05 Thread git

eiri commented on issue #548: [Jenkins] 500 error on getting view output
URL: https://github.com/apache/couchdb/issues/548#issuecomment-313226682
 
 
   It's rather hard to fix it for real with a solid chance of accidentally 
adding deadlock or bottleneck and at the same time it is induced by usage 
anti-pattern, so I don't see it as a blocker.
 

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] wohali commented on issue #548: [Jenkins] 500 error on getting view output

2017-07-05 Thread git

wohali commented on issue #548: [Jenkins] 500 error on getting view output
URL: https://github.com/apache/couchdb/issues/548#issuecomment-313223484
 
 
   @kocolosk @eiri What do you want to do about the actual race condition? Do 
you think the race itself should be a 2.1 release blocker?
   
   Feel free to keep this issue for it, or open a new one.
 

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] wohali closed pull request #646: Make map functions distinct with each invocation

2017-07-05 Thread git

wohali closed pull request #646: Make map functions distinct with each 
invocation
URL: https://github.com/apache/couchdb/pull/646
 
 
   
 

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] sebastianrothbucher commented on issue #646: Make map functions distinct with each invocation

2017-07-05 Thread git

sebastianrothbucher commented on issue #646: Make map functions distinct with 
each invocation
URL: https://github.com/apache/couchdb/pull/646#issuecomment-313223339
 
 
   great!
 

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] sebastianrothbucher commented on issue #548: [Jenkins] 500 error on getting view output

2017-07-05 Thread git

sebastianrothbucher commented on issue #548: [Jenkins] 500 error on getting 
view output
URL: https://github.com/apache/couchdb/issues/548#issuecomment-313215096
 
 
   I did a PR for just that. Sadly I can't reproduce (on a CentOS VM), but 
tests still work - maybe Travis gives us more stable test runs now
 

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] eiri commented on issue #627: Pass UserCtx to fabric's all_docs from mango query

2017-07-05 Thread git

eiri commented on issue #627: Pass UserCtx to fabric's all_docs from mango query
URL: https://github.com/apache/couchdb/pull/627#issuecomment-313203328
 
 
   Depends on apache/couchdb#645
 

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] eiri opened a new pull request #645: Pass db open options in fabric_view_map

2017-07-05 Thread git

eiri opened a new pull request #645: Pass db open options in fabric_view_map
URL: https://github.com/apache/couchdb/pull/645
 
 
   ## Overview
   
   We don't set db open options in `fabric_view_map` which doesn't matter in 
the most cases, but prevents from opening docs on admin-only databases such as 
`_users`, because of the missing `user_ctx`
   
   This patch passes `user_ctx` set at http request down to a database that 
holds a querying view.  
   
   ## Testing recommendations
   
   We don't have full coverage of this part of fabric, unfortunately. To quick 
test add a simple ddoc to `_users` database, something like:
   
   ```json
   {
 "views": {
   "names": {
 "map": "function(doc) { emit(doc.name); }"
   }
 }
   }
   ```
   
   And then query it with `include_docs=true` that should return all the user 
documents in the users database.
   
   ## Checklist
   
   - [x] Code is written and works correctly;
   - [ ] Changes are covered by tests;
   - [ ] Documentation reflects the changes;
   
 

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] wohali commented on issue #630: EUnit couch_changes_tests failing should_select_with_continuous test

2017-07-05 Thread git

wohali commented on issue #630: EUnit couch_changes_tests failing 
should_select_with_continuous test
URL: https://github.com/apache/couchdb/issues/630#issuecomment-313199914
 
 
   @eiri spied on IRC that these failures both point to heartbeats showing up 
in the _changes feed, possibly unexpected ones. Good eye! 
   
   Test case needing to be partially rewritten, perhaps?
 

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] wohali commented on issue #630: EUnit couch_changes_tests failing should_select_with_continuous test

2017-07-05 Thread git

wohali commented on issue #630: EUnit couch_changes_tests failing 
should_select_with_continuous test
URL: https://github.com/apache/couchdb/issues/630#issuecomment-313199914
 
 
   @eiri spied on IRC that these failures both point to heartbeats showing up 
in the _changes feed, possibly unexpected ones. Good eye! 
   
   Yest case needing to be partially rewritten, perhaps?
 

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] sebastianrothbucher commented on issue #548: [Jenkins] 500 error on getting view output

2017-07-05 Thread git

sebastianrothbucher commented on issue #548: [Jenkins] 500 error on getting 
view output
URL: https://github.com/apache/couchdb/issues/548#issuecomment-313192665
 
 
   or append a randomized comment when uploading the map fkt
 

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[Jenkins] FAILURE: CouchDB » 2.1.x #10

2017-07-05 Thread Apache Jenkins Server

Boo, we failed. https://builds.apache.org/job/CouchDB/job/2.1.x/10/

[GitHub] wohali commented on issue #630: EUnit couch_changes_tests failing should_select_with_continuous test

2017-07-05 Thread git

wohali commented on issue #630: EUnit couch_changes_tests failing 
should_select_with_continuous test
URL: https://github.com/apache/couchdb/issues/630#issuecomment-313183466
 
 
   And again:
   * https://travis-ci.org/apache/couchdb/jobs/250437167
 

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[Jenkins] FAILURE: CouchDB » master #55

2017-07-05 Thread Apache Jenkins Server

Boo, we failed. https://builds.apache.org/job/CouchDB/job/master/55/

[Jenkins] FAILURE: CouchDB » master #54

2017-07-05 Thread Apache Jenkins Server

Boo, we failed. https://builds.apache.org/job/CouchDB/job/master/54/

[Jenkins] FAILURE: CouchDB » master #53

2017-07-05 Thread Apache Jenkins Server

Boo, we failed. https://builds.apache.org/job/CouchDB/job/master/53/

[Jenkins] FAILURE: CouchDB » 2.1.x #9

2017-07-05 Thread Apache Jenkins Server

Boo, we failed. https://builds.apache.org/job/CouchDB/job/2.1.x/9/

[GitHub] wohali opened a new issue #644: couch_replicator_scheduler killing "completed normally" replication?

2017-07-05 Thread git

wohali opened a new issue #644: couch_replicator_scheduler killing "completed 
normally" replication?
URL: https://github.com/apache/couchdb/issues/644
 
 
   ## Current & Expected Behavior
   Normally the `couch_replicator_use_checkpoints_tests` pass fine. However, we 
have an unusual failure in a Travis run today. The replication scheduler says 
it "completed normally", but then it appears it proceeds to KILL it?! Odd.
   
   ## Logs
   * **Travis**: https://travis-ci.org/apache/couchdb/jobs/250436888#L5400-L5407
   * **`couch.log`**: 
https://couchdb-vm2.apache.org/ci_errorlogs/travis-couchdb-250436888-2017-07-05T17%3A16%3A05.960154/couchlog.tar.gz
   * **Useful excerpt**: 
https://gist.github.com/wohali/0bc580a1edf96205a52df30a72e55ddc
   
   Assigning to @nickva because this feels like a scheduler bug.
 

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] wohali commented on issue #643: EUnit couchdb_views_tests failure: suspend_process after termination

2017-07-05 Thread git

wohali commented on issue #643: EUnit couchdb_views_tests failure: 
suspend_process after termination
URL: https://github.com/apache/couchdb/issues/643#issuecomment-313176291
 
 
   Another instance:
   * https://travis-ci.org/apache/couchdb/jobs/250437020
 

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[Jenkins] FAILURE: CouchDB » master #51

2017-07-05 Thread Apache Jenkins Server

Boo, we failed. https://builds.apache.org/job/CouchDB/job/master/51/

[Jenkins] SUCCESS: CouchDB » master #50

2017-07-05 Thread Apache Jenkins Server

Yay, we passed. https://builds.apache.org/job/CouchDB/job/master/50/

[jira] [Commented] (COUCHDB-3170) Permissions are ignored in "_users" database.

2017-07-05 Thread Joan Touzet (JIRA)


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

Joan Touzet commented on COUCHDB-3170:
--

Pretty sure that you have to be an actual server-level admin ([admins] section 
in the ini file) for _users once you create a _security object for _users. I 
don't believe it is delegatable to non-server admins.

> Permissions are ignored in "_users" database.
> -
>
> Key: COUCHDB-3170
> URL: https://issues.apache.org/jira/browse/COUCHDB-3170
> Project: CouchDB
>  Issue Type: Bug
>Affects Versions: 2.0.0
>Reporter: Pavel V
>
> To reproduce (in Fauxton):
> 1. Create a user in "_users" database with role "app-admin".
> 2. Change permissions for "_users" DB to add "app-admin" role to admins and 
> members.
> 3. Check "/_users/_security". Response should be similar to:
> {"admins":{"names":[],"roles":["app-admin"]},"members":{"names":[],"roles":["app-admin"]},"ok":true}
> 4. Login as the user with the "app-admin" role.
> 5. Open "_users", you get 401 response and Fauxton shows message "An Error 
> occurred: You are not a server admin.". 401 response contains following JSON:
> {error: "unauthorized", reason: "You are not a server admin."}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (COUCHDB-3170) Permissions are ignored in "_users" database.

2017-07-05 Thread Joan Touzet (JIRA)


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

Joan Touzet resolved COUCHDB-3170.
--
Resolution: Not A Problem

> Permissions are ignored in "_users" database.
> -
>
> Key: COUCHDB-3170
> URL: https://issues.apache.org/jira/browse/COUCHDB-3170
> Project: CouchDB
>  Issue Type: Bug
>Affects Versions: 2.0.0
>Reporter: Pavel V
>
> To reproduce (in Fauxton):
> 1. Create a user in "_users" database with role "app-admin".
> 2. Change permissions for "_users" DB to add "app-admin" role to admins and 
> members.
> 3. Check "/_users/_security". Response should be similar to:
> {"admins":{"names":[],"roles":["app-admin"]},"members":{"names":[],"roles":["app-admin"]},"ok":true}
> 4. Login as the user with the "app-admin" role.
> 5. Open "_users", you get 401 response and Fauxton shows message "An Error 
> occurred: You are not a server admin.". 401 response contains following JSON:
> {error: "unauthorized", reason: "You are not a server admin."}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] wohali closed issue #632: JS design_docs test failure - incorrect response

2017-07-05 Thread git

wohali closed issue #632: JS design_docs test failure - incorrect response
URL: https://github.com/apache/couchdb/issues/632
 
 
   
 

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] wohali closed pull request #639: Fix eunit timeout option for compression tests

2017-07-05 Thread git

wohali closed pull request #639: Fix eunit timeout option for compression tests
URL: https://github.com/apache/couchdb/pull/639
 
 
   
 

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] wohali closed issue #629: EUnit compression test timeouts

2017-07-05 Thread git

wohali closed issue #629: EUnit compression test timeouts
URL: https://github.com/apache/couchdb/issues/629
 
 
   
 

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] wohali closed pull request #637: Fix mismatch between MAX_DBS_OPEN and default.ini

2017-07-05 Thread git

wohali closed pull request #637: Fix mismatch between MAX_DBS_OPEN and 
default.ini
URL: https://github.com/apache/couchdb/pull/637
 
 
   
 

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] wohali closed issue #636: Fix mismatch between MAX_DBS_OPEN and rel/overlay/etc/default.ini

2017-07-05 Thread git

wohali closed issue #636: Fix mismatch between MAX_DBS_OPEN and 
rel/overlay/etc/default.ini
URL: https://github.com/apache/couchdb/issues/636
 
 
   
 

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] davisp commented on a change in pull request #610: Optimize ddoc cache

2017-07-05 Thread git

davisp commented on a change in pull request #610: Optimize ddoc cache
URL: https://github.com/apache/couchdb/pull/610#discussion_r125699350
 
 

 ##
 File path: src/ddoc_cache/src/ddoc_cache_tables.erl
 ##
 @@ -0,0 +1,68 @@
+% Licensed under the Apache License, Version 2.0 (the "License"); you may not
+% use this file except in compliance with the License. You may obtain a copy of
+% the License at
+%
+%   http://www.apache.org/licenses/LICENSE-2.0
+%
+% Unless required by applicable law or agreed to in writing, software
+% distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
+% WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
+% License for the specific language governing permissions and limitations under
+% the License.
+
+-module(ddoc_cache_tables).
+-behaviour(gen_server).
+-vsn(1).
 
 Review comment:
   Will do
 

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] davisp commented on a change in pull request #610: Optimize ddoc cache

2017-07-05 Thread git

davisp commented on a change in pull request #610: Optimize ddoc cache
URL: https://github.com/apache/couchdb/pull/610#discussion_r125699182
 
 

 ##
 File path: src/ddoc_cache/src/ddoc_cache_speed.erl
 ##
 @@ -0,0 +1,61 @@
+-module(ddoc_cache_speed).
 
 Review comment:
   Its marked as a TEMP commit. I'll end up removing it before merging the 
final PR. Its not a very rigourous test. To keep it in history I may remove it 
iwth a revert rather than a squash if you think it'd be worth it.
 

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] davisp commented on a change in pull request #610: Optimize ddoc cache

2017-07-05 Thread git

davisp commented on a change in pull request #610: Optimize ddoc cache
URL: https://github.com/apache/couchdb/pull/610#discussion_r125699144
 
 

 ##
 File path: src/ddoc_cache/src/ddoc_cache_lru.erl
 ##
 @@ -0,0 +1,293 @@
+% Licensed under the Apache License, Version 2.0 (the "License"); you may not
+% use this file except in compliance with the License. You may obtain a copy of
+% the License at
+%
+%   http://www.apache.org/licenses/LICENSE-2.0
+%
+% Unless required by applicable law or agreed to in writing, software
+% distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
+% WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
+% License for the specific language governing permissions and limitations under
+% the License.
+
+-module(ddoc_cache_lru).
+-behaviour(gen_server).
+-vsn(1).
+
+
+-export([
+start_link/0,
+open/1,
+refresh/2
+]).
+
+-export([
+init/1,
+terminate/2,
+handle_call/3,
+handle_cast/2,
+handle_info/2,
+code_change/3
+]).
+
+-export([
+handle_db_event/3
+]).
+
+
+-include("ddoc_cache.hrl").
+
+
+-record(st, {
+pids, % pid -> key
+dbs, % dbname -> docid -> key -> pid
+size,
+evictor
+}).
+
+
+start_link() ->
+gen_server:start_link({local, ?MODULE}, ?MODULE, [], []).
+
+
+open(Key) ->
+try ets:lookup(?CACHE, Key) of
+[] ->
+lru_start(Key);
+[#entry{pid = undefined}] ->
+lru_start(Key);
+[#entry{val = undefined, pid = Pid}] ->
+couch_stats:increment_counter([ddoc_cache, miss]),
+ddoc_cache_entry:open(Pid, Key);
+[#entry{val = Val, pid = Pid}] ->
+couch_stats:increment_counter([ddoc_cache, hit]),
+ddoc_cache_entry:accessed(Pid),
+{ok, Val}
+catch _:_ ->
+couch_stats:increment_counter([ddoc_cache, recovery]),
+ddoc_cache_entry:recover(Key)
+end.
+
+
+refresh(DbName, DDocIds) ->
+gen_server:cast(?MODULE, {refresh, DbName, DDocIds}).
+
+
+init(_) ->
+process_flag(trap_exit, true),
+{ok, Pids} = khash:new(),
+{ok, Dbs} = khash:new(),
+{ok, Evictor} = couch_event:link_listener(
+?MODULE, handle_db_event, nil, [all_dbs]
+),
+{ok, #st{
+pids = Pids,
+dbs = Dbs,
+size = 0,
+evictor = Evictor
+}}.
+
+
+terminate(_Reason, St) ->
+case is_pid(St#st.evictor) of
+true -> catch exit(St#st.evictor, kill);
+false -> ok
+end,
+ok.
+
+
+handle_call({start, Key}, _From, St) ->
+#st{
+pids = Pids,
+dbs = Dbs,
+size = CurSize
+} = St,
+case ets:lookup(?CACHE, Key) of
+[] ->
+MaxSize = config:get_integer("ddoc_cache", "max_size", 1000),
+case trim(St, CurSize, max(0, MaxSize)) of
+{ok, N} ->
+true = ets:insert_new(?CACHE, #entry{key = Key}),
+{ok, Pid} = ddoc_cache_entry:start_link(Key),
+true = ets:update_element(?CACHE, Key, {#entry.pid, Pid}),
+ok = khash:put(Pids, Pid, Key),
+store_key(Dbs, Key, Pid),
+{reply, {ok, Pid}, St#st{size = CurSize - N + 1}};
+full ->
+?EVENT(full, Key),
+{reply, full, St}
+end;
+[#entry{pid = Pid}] ->
+{reply, {ok, Pid}, St}
+end;
+
+handle_call(Msg, _From, St) ->
+{stop, {invalid_call, Msg}, {invalid_call, Msg}, St}.
+
+
+handle_cast({evict, DbName}, St) ->
+gen_server:abcast(mem3:nodes(), ?MODULE, {do_evict, DbName}),
+{noreply, St};
+
+handle_cast({refresh, DbName, DDocIds}, St) ->
+gen_server:abcast(mem3:nodes(), ?MODULE, {do_refresh, DbName, DDocIds}),
+{noreply, St};
+
+handle_cast({do_evict, DbName}, St) ->
+#st{
+dbs = Dbs
+} = St,
+ToRem = case khash:lookup(Dbs, DbName) of
+{value, DDocIds} ->
+AccOut = khash:fold(DDocIds, fun(_, Keys, Acc1) ->
+khash:to_list(Keys) ++ Acc1
+end, []),
+?EVENT(evicted, DbName),
+AccOut;
+not_found ->
+?EVENT(evict_noop, DbName),
+[]
+end,
+lists:foreach(fun({Key, Pid}) ->
+remove_entry(St, Key, Pid)
+end, ToRem),
+khash:del(Dbs, DbName),
+{noreply, St};
+
+handle_cast({do_refresh, DbName, DDocIdList}, St) ->
+#st{
+dbs = Dbs
+} = St,
+case khash:lookup(Dbs, DbName) of
+{value, DDocIds} ->
+lists:foreach(fun(DDocId) ->
+case khash:lookup(DDocIds, DDocId) of
+{value, Keys} ->
+khash:fold(Keys, fun(_, Pid, _) ->
+ddoc_cache_entry:refresh(Pid)
+end, nil);
+not_found ->
+ok
+end
+end, [no_ddocid |

[GitHub] davisp commented on a change in pull request #610: Optimize ddoc cache

2017-07-05 Thread git

davisp commented on a change in pull request #610: Optimize ddoc cache
URL: https://github.com/apache/couchdb/pull/610#discussion_r125698591
 
 

 ##
 File path: src/ddoc_cache/src/ddoc_cache_lru.erl
 ##
 @@ -0,0 +1,293 @@
+% Licensed under the Apache License, Version 2.0 (the "License"); you may not
+% use this file except in compliance with the License. You may obtain a copy of
+% the License at
+%
+%   http://www.apache.org/licenses/LICENSE-2.0
+%
+% Unless required by applicable law or agreed to in writing, software
+% distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
+% WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
+% License for the specific language governing permissions and limitations under
+% the License.
+
+-module(ddoc_cache_lru).
+-behaviour(gen_server).
+-vsn(1).
+
+
+-export([
+start_link/0,
+open/1,
+refresh/2
+]).
+
+-export([
+init/1,
+terminate/2,
+handle_call/3,
+handle_cast/2,
+handle_info/2,
+code_change/3
+]).
+
+-export([
+handle_db_event/3
+]).
+
+
+-include("ddoc_cache.hrl").
+
+
+-record(st, {
+pids, % pid -> key
+dbs, % dbname -> docid -> key -> pid
+size,
+evictor
+}).
+
+
+start_link() ->
+gen_server:start_link({local, ?MODULE}, ?MODULE, [], []).
+
+
+open(Key) ->
+try ets:lookup(?CACHE, Key) of
+[] ->
+lru_start(Key);
 
 Review comment:
   I'm not sure that the best thing is to add those calls here. I think that 
all of the miss cases are all correctly qualified as misses. However it might 
be useful to add a new metric to the entry process that tracks how many clients 
it responded to which would show the thundering herd issues.
 

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] davisp commented on a change in pull request #610: Optimize ddoc cache

2017-07-05 Thread git

davisp commented on a change in pull request #610: Optimize ddoc cache
URL: https://github.com/apache/couchdb/pull/610#discussion_r125698313
 
 

 ##
 File path: src/ddoc_cache/src/ddoc_cache_lru.erl
 ##
 @@ -0,0 +1,293 @@
+% Licensed under the Apache License, Version 2.0 (the "License"); you may not
+% use this file except in compliance with the License. You may obtain a copy of
+% the License at
+%
+%   http://www.apache.org/licenses/LICENSE-2.0
+%
+% Unless required by applicable law or agreed to in writing, software
+% distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
+% WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
+% License for the specific language governing permissions and limitations under
+% the License.
+
+-module(ddoc_cache_lru).
+-behaviour(gen_server).
+-vsn(1).
+
+
+-export([
+start_link/0,
+open/1,
+refresh/2
+]).
+
+-export([
+init/1,
+terminate/2,
+handle_call/3,
+handle_cast/2,
+handle_info/2,
+code_change/3
+]).
+
+-export([
+handle_db_event/3
+]).
+
+
+-include("ddoc_cache.hrl").
+
+
+-record(st, {
+pids, % pid -> key
+dbs, % dbname -> docid -> key -> pid
+size,
+evictor
+}).
+
+
+start_link() ->
+gen_server:start_link({local, ?MODULE}, ?MODULE, [], []).
+
+
+open(Key) ->
+try ets:lookup(?CACHE, Key) of
 
 Review comment:
   That's all mostly right. The motivation for this was that it would allow the 
individual entries to be direct lookups rather than table scans and also allows 
for the non-rev-specific entry to automatically update its value when a design 
document is updated. As to the extra non-cache lookups the way I reasoned about 
it was that its only a constant number in the frequently asked case so once 
they're in cache its not an issue. And on the flip side if we're iterating over 
things in such a way that if we're evicting entries and then have a lot of 
traffic to un-cached entries it doesn't matter either as we'd have to increase 
the cache size regardless.
   
   I'll take a ponder on how to insert things into the cache from non-client 
requested actions but it seems to me like it'd open up a lot of race conditions 
in the already fairly complex logic around managing the cache entries.
   
   Also for the rev-specific entries that's true for the most part. They'll 
stick around until evicted or a quorum of their database shards are compacted. 
I'll contemplate how easily it'd be to add some sort of check there so that 
they'll close if they refresh and are not the most recent revision.
 

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] garrensmith commented on issue #628: Add stable and update support to Mango

2017-07-05 Thread git

garrensmith commented on issue #628: Add stable and update support to Mango
URL: https://github.com/apache/couchdb/pull/628#issuecomment-313159484
 
 
   Yes, those are replacing stale. I'm not sure about text indexes. I don't 
think so
   
   All misspelling thanks to my iPhone.
   
   From: Tony Sun 
   Sent: Wednesday, July 5, 2017 5:49:02 PM
   To: apache/couchdb
   Cc: garren smith; Author
   Subject: Re: [apache/couchdb] Add stable and update support to Mango (#628)
   
   
   stable and update are replacing stale right? will the same options work for 
text indexes?
   
   ?
   You are receiving this because you authored the thread.
   Reply to this email directly, view it on 
GitHub, or 
mute the 
thread.
   
 

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[Jenkins] FAILURE: CouchDB » master #49

2017-07-05 Thread Apache Jenkins Server

Boo, we failed. https://builds.apache.org/job/CouchDB/job/master/49/

[Jenkins] FAILURE: CouchDB » 2.1.x #8

2017-07-05 Thread Apache Jenkins Server

Boo, we failed. https://builds.apache.org/job/CouchDB/job/2.1.x/8/

[GitHub] nickva commented on issue #637: Fix mismatch between MAX_DBS_OPEN and default.ini

2017-07-05 Thread git

nickva commented on issue #637: Fix mismatch between MAX_DBS_OPEN and 
default.ini
URL: https://github.com/apache/couchdb/pull/637#issuecomment-313144919
 
 
   Very nice!
   
   +1
 

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] nickva commented on issue #639: Fix eunit timeout option for compression tests

2017-07-05 Thread git

nickva commented on issue #639: Fix eunit timeout option for compression tests
URL: https://github.com/apache/couchdb/pull/639#issuecomment-313144646
 
 
   +1
 

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] tonysun83 commented on issue #628: Add stable and update support to Mango

2017-07-05 Thread git

tonysun83 commented on issue #628: Add stable and update support to Mango
URL: https://github.com/apache/couchdb/pull/628#issuecomment-313144229
 
 
   stable and update are replacing stale right? will the same options work for 
text indexes?
 

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] nickva commented on issue #641: Remove yet another invalid test case (ddoc_cache related)

2017-07-05 Thread git

nickva commented on issue #641: Remove yet another invalid test case 
(ddoc_cache related)
URL: https://github.com/apache/couchdb/pull/641#issuecomment-313144193
 
 
   +1
 

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[jira] [Commented] (COUCHDB-3170) Permissions are ignored in "_users" database.

2017-07-05 Thread Lebruman (JIRA)


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

Lebruman commented on COUCHDB-3170:
---

Is there any plan to solve this ?
Is there any work around ?

> Permissions are ignored in "_users" database.
> -
>
> Key: COUCHDB-3170
> URL: https://issues.apache.org/jira/browse/COUCHDB-3170
> Project: CouchDB
>  Issue Type: Bug
>Affects Versions: 2.0.0
>Reporter: Pavel V
>
> To reproduce (in Fauxton):
> 1. Create a user in "_users" database with role "app-admin".
> 2. Change permissions for "_users" DB to add "app-admin" role to admins and 
> members.
> 3. Check "/_users/_security". Response should be similar to:
> {"admins":{"names":[],"roles":["app-admin"]},"members":{"names":[],"roles":["app-admin"]},"ok":true}
> 4. Login as the user with the "app-admin" role.
> 5. Open "_users", you get 401 response and Fauxton shows message "An Error 
> occurred: You are not a server admin.". 401 response contains following JSON:
> {error: "unauthorized", reason: "You are not a server admin."}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] wohali commented on issue #630: EUnit couch_changes_tests failing should_select_with_continuous test

2017-07-05 Thread git

wohali commented on issue #630: EUnit couch_changes_tests failing 
should_select_with_continuous test
URL: https://github.com/apache/couchdb/issues/630#issuecomment-313135385
 
 
   And again:
   
   * https://travis-ci.org/apache/couchdb/jobs/250225893
 

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] wohali commented on issue #548: [Jenkins] 500 error on getting view output

2017-07-05 Thread git

wohali commented on issue #548: [Jenkins] 500 error on getting view output
URL: https://github.com/apache/couchdb/issues/548#issuecomment-313134019
 
 
   Even a *whitespace* change would be sufficient.
 

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] konrad-2013 commented on issue #48: Remote Memory Exposure in nano@6.3.0 > follow@0.12.1 > request@2.55.0

2017-07-05 Thread git

konrad-2013 commented on issue #48: Remote Memory Exposure in nano@6.3.0 > 
follow@0.12.1 > request@2.55.0
URL: https://github.com/apache/couchdb-nano/issues/48#issuecomment-313057362
 
 
   Cool thanks for figuring that out.
   :+1: for PR #51
 

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[jira] [Commented] (COUCHDB-3244) Replication is broken when database name has "/" and cluster is configured

2017-07-05 Thread Sergey Safarov (JIRA)


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

Sergey Safarov commented on COUCHDB-3244:
-

I tested a5b87955287a8ebf4c81d9bfbbfaff6091e53f58 and can confirm issue is 
resolved.

> Replication is broken when database name has "/" and cluster is configured
> --
>
> Key: COUCHDB-3244
> URL: https://issues.apache.org/jira/browse/COUCHDB-3244
> Project: CouchDB
>  Issue Type: Bug
>  Components: Database Core
>Reporter: Sergey Safarov
>
> When CouchDB host is configured as standalone server when i can execute 
> command 
> curl -s -S -X POST http://127.0.0.1:5984/_replicate -H 'Content-Type: 
> application/json' -H 'Accept: application/json, text/javascript' 
> --data-binary  
> '{"source":"http://xxx.xxx.xxx.xxx:5984/account%2f32%2fc2%2f83a70fb3146e584c4743c557b1df","target":"account/32/c2/83a70fb3146e584c4743c557b1df","continuous":false,"create_target":true}'
> And then get responce like
> {"ok":true,"session_id":"a25fa8ed55c970f3ec6dc7e3f641d515","source_last_seq":"424-g1LzeJyt0DsKwkAQBuDFCAqeQBu9gGGziTGdEU9hpbMvYtwklY2N3kRvojfRm8R9BOxESJoZGGY-hl8hhIaZx9GEVSeWcZoe4TzHga8qBopXBRxKpXd6gOi0rus88yAp9GDAAYdEyp-X_8B0pitdNbZv7SiUEkC0t1Nj7xp7Y20COIIA2tt7Y18ae2xtDAJosGxtl31d0VU3zd-Mv3a5sDgRZNGRf3f-w_hb978QnErWkf90_uv7fywII4x25L-db_MfuXyA8ZD_zj__ADLK8AQ","replication_id_version":3,"history":[{"session_id":"a25fa8ed55c970f3ec6dc7e3f641d515","start_time":"Sat,
>  26 Nov 2016 13:51:02 GMT","end_time":"Sat, 26 Nov 2016 13:51:25 
> GMT","start_last_seq":0,"end_last_seq":"424-g1LzeJyt0DsKwkAQBuDFCAqeQBu9gGGziTGdEU9hpbMvYtwklY2N3kRvojfRm8R9BOxESJoZGGY-hl8hhIaZx9GEVSeWcZoe4TzHga8qBopXBRxKpXd6gOi0rus88yAp9GDAAYdEyp-X_8B0pitdNbZv7SiUEkC0t1Nj7xp7Y20COIIA2tt7Y18ae2xtDAJosGxtl31d0VU3zd-Mv3a5sDgRZNGRf3f-w_hb978QnErWkf90_uv7fywII4x25L-db_MfuXyA8ZD_zj__ADLK8AQ","recorded_seq":"424-g1LzeJyt0DsKwkAQBuDFCAqeQBu9gGGziTGdEU9hpbMvYtwklY2N3kRvojfRm8R9BOxESJoZGGY-hl8hhIaZx9GEVSeWcZoe4TzHga8qBopXBRxKpXd6gOi0rus88yAp9GDAAYdEyp-X_8B0pitdNbZv7SiUEkC0t1Nj7xp7Y20COIIA2tt7Y18ae2xtDAJosGxtl31d0VU3zd-Mv3a5sDgRZNGRf3f-w_hb978QnErWkf90_uv7fywII4x25L-db_MfuXyA8ZD_zj__ADLK8AQ","missing_checked":106,"missing_found":106,"docs_read":106,"docs_written":106,"doc_write_failures":0}]}
> But if CouchDB node is joined to cluster same command cannot be executed.
> CouchDB not retrun any responce



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[Jenkins] FAILURE: CouchDB » master #48

2017-07-05 Thread Apache Jenkins Server

Boo, we failed. https://builds.apache.org/job/CouchDB/job/master/48/

[Jenkins] FAILURE: CouchDB » 2.1.x #7

2017-07-05 Thread Apache Jenkins Server

Boo, we failed. https://builds.apache.org/job/CouchDB/job/2.1.x/7/

[GitHub] janl commented on issue #548: [Jenkins] 500 error on getting view output

2017-07-05 Thread git

janl commented on issue #548: [Jenkins] 500 error on getting view output
URL: https://github.com/apache/couchdb/issues/548#issuecomment-313017929
 
 
   @sebastianrothbucher do you maybe have some time to tackle the JS tests? I 
know you?ve done tons of this kind of work :)
   
   One idea would be to leave the tests as-is as good as possible, and inject 
the random element in couch.js, but that?s probably only really doable for 
ad-hoc queries that  don?t reference the doc by name later. But we do have a 
bunch of those.
 

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] janl commented on issue #593: Allow bind address of 127.0.0.1 in _cluster_setup for single node

2017-07-05 Thread git

janl commented on issue #593: Allow bind address of 127.0.0.1 in _cluster_setup 
for single node
URL: https://github.com/apache/couchdb/issues/593#issuecomment-313017161
 
 
   The way forward is definitely 
   
   > Improve the /_cluster_setup endpoint to accept a new "action": 
"enable_single_node" that tolerates binding to 127.0.0.1. This would have to be 
paired with changing the validation function in Fauxton to accept that bind 
address when in the single node workflow.
   
 

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] wohali commented on issue #140: couchapps -> ddocs

2017-07-05 Thread git

wohali commented on issue #140: couchapps -> ddocs
URL: 
https://github.com/apache/couchdb-documentation/pull/140#issuecomment-313016717
 
 
   Redirects done.
 

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] janl opened a new pull request #51: feat: switch from follow to cloudant-follow, which is maintaned

2017-07-05 Thread git

janl opened a new pull request #51: feat: switch from follow to 
cloudant-follow, which is maintaned
URL: https://github.com/apache/couchdb-nano/pull/51
 
 
   
 

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] janl commented on issue #48: Remote Memory Exposure in nano@6.3.0 > follow@0.12.1 > request@2.55.0

2017-07-05 Thread git

janl commented on issue #48: Remote Memory Exposure in nano@6.3.0 > 
follow@0.12.1 > request@2.55.0
URL: https://github.com/apache/couchdb-nano/issues/48#issuecomment-313016217
 
 
   PR here: https://github.com/apache/couchdb-nano/pull/51
 

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] janl commented on issue #48: Remote Memory Exposure in nano@6.3.0 > follow@0.12.1 > request@2.55.0

2017-07-05 Thread git

janl commented on issue #48: Remote Memory Exposure in nano@6.3.0 > 
follow@0.12.1 > request@2.55.0
URL: https://github.com/apache/couchdb-nano/issues/48#issuecomment-313015640
 
 
   Should we switch to cloudant-follow? 
https://github.com/cloudant-labs/cloudant-follow
 

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] wohali closed pull request #140: couchapps -> ddocs

2017-07-05 Thread git

wohali closed pull request #140: couchapps -> ddocs
URL: https://github.com/apache/couchdb-documentation/pull/140
 
 
   
 

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] janl commented on issue #140: couchapps -> ddocs

2017-07-05 Thread git

janl commented on issue #140: couchapps -> ddocs
URL: 
https://github.com/apache/couchdb-documentation/pull/140#issuecomment-313011782
 
 
   +1000
 

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] wohali opened a new pull request #140: couchapps -> ddocs

2017-07-05 Thread git

wohali opened a new pull request #140: couchapps -> ddocs
URL: https://github.com/apache/couchdb-documentation/pull/140
 
 
   * remove all references to couchapps in the documentation
   * include an explanation as to why this change has been made
   ## Checklist
   
   - [X] Documentation is written and is accurate;
   - [X] `make check` passes with no errors
   - [ ] Update 
[rebar.config.script](https://github.com/apache/couchdb/blob/master/rebar.config.script)
 with the commit hash once this PR is rebased and merged
   
 

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

75 matches

Mail list logo