[jira] [Commented] (COUCHDB-2657) if _metadata is there, creating a db does not work

2015-04-17 Thread Russell Branca (JIRA)

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

Russell Branca commented on COUCHDB-2657:
-

I tracked this down to making a `fabric:open_doc` call from within the 
`cassim_metadata_cache` gen_server. The problem is that `fabric:open_doc` does 
a `receive` call while waiting for a worker response, and this intercepts any 
other messages sent in. I've got a patch out [1] that shows the rough solution. 
I did notice however that in the test case we're still getting a 409 error on 
the second request, so we'll want to make sure we handle that properly. Should 
we check and see if the values are the same? and if not reload? That might be 
worthwhile but potentially expensive. Alternatively we could automatically 
create the security doc on db creation.

Also, I think COUCHDB-2659 might be a duplicate of this issue.



[1] https://github.com/apache/couchdb-cassim/tree/2657-fix-cassim-fabric-calls

> if _metadata is there, creating a db does not work
> --
>
> Key: COUCHDB-2657
> URL: https://issues.apache.org/jira/browse/COUCHDB-2657
> Project: CouchDB
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: BigCouch, Database Core
>Reporter: Robert Kowalski
>Priority: Blocker
>
> with the new _setup_cluster endpoint a _metadata db is created.
> when it exists, and we create a db, read it _all_doc immediatly [1] (Fauxton 
> does that) we get:
> `document update conflict`
> [1] 
> http://localhost:8000/sdfsdtest/_all_docs?startkey=%22_design%2F%22&endkey=%22_design0%22&include_docs=true&limit=501



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


[jira] [Commented] (COUCHDB-2659) CouchDB master failing the PouchDB test suite - live changes

2015-04-17 Thread Russell Branca (JIRA)

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

Russell Branca commented on COUCHDB-2659:
-

Is this a duplicate of COUCHDB-2657?

> CouchDB master failing the PouchDB test suite - live changes
> 
>
> Key: COUCHDB-2659
> URL: https://issues.apache.org/jira/browse/COUCHDB-2659
> Project: CouchDB
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: Database Core
>Reporter: Nolan Lawson
>
> See [this comment | 
> https://github.com/pouchdb/pouchdb/pull/3722#issuecomment-91571425] for 
> details. We have automated tests that pull in the latest CouchDB master 
> branch and run the PouchDB test suite against it, and recently our tests 
> started failing due to [apache/couchdb#313 | 
> https://github.com/apache/couchdb/pull/313]. So I switched back to admin 
> party mode, but now it's failing for another reason:
> {quote}
> 1) test.attachments.js-http #3074 live changes():
>  Uncaught Database encountered an unknown error
> {quote}
> Instructions for running the PouchDB test suite are in our TESTING.md, it's 
> pretty straightforward but basically you just want to point it to any CouchDB 
> server like so and run the tests:
> {code}
> BAIL=0 COUCH_HOST=http://localhost:15984 npm test
> {code}
> {{BAIL=0}} will prevent bailing upon the first error.



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


[jira] [Commented] (COUCHDB-2657) if _metadata is there, creating a db does not work

2015-04-17 Thread ASF subversion and git services (JIRA)

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

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

Commit 7d9cc47176c3f7899208e754ce8ec13d1ab6f070 in couchdb-cassim's branch 
refs/heads/2657-fix-cassim-fabric-calls from [~chewbranca]
[ https://git-wip-us.apache.org/repos/asf?p=couchdb-cassim.git;h=7d9cc47 ]

Move fabric:open_doc calls outside of gen_server

COUCHDB-2657


> if _metadata is there, creating a db does not work
> --
>
> Key: COUCHDB-2657
> URL: https://issues.apache.org/jira/browse/COUCHDB-2657
> Project: CouchDB
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: BigCouch, Database Core
>Reporter: Robert Kowalski
>Priority: Blocker
>
> with the new _setup_cluster endpoint a _metadata db is created.
> when it exists, and we create a db, read it _all_doc immediatly [1] (Fauxton 
> does that) we get:
> `document update conflict`
> [1] 
> http://localhost:8000/sdfsdtest/_all_docs?startkey=%22_design%2F%22&endkey=%22_design0%22&include_docs=true&limit=501



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


Re: Vote on the CouchDB logo

2015-04-17 Thread Alexander Shorin
Hi Nolan!

What about the other candidates? We need the votes for all of them,
not a single one.
--
,,,^..^,,,


On Fri, Apr 17, 2015 at 6:28 PM, Nolan Lawson  wrote:
> +1 for Constantin's. :)
>
> - Nolan
>
> --
> Nolan Lawson
> nolanlawson.com
> github.com/nolanlawson


[jira] [Commented] (COUCHDB-2657) if _metadata is there, creating a db does not work

2015-04-17 Thread Russell Branca (JIRA)

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

Russell Branca commented on COUCHDB-2657:
-

Also the error I'm seeing with this is:


[<<"gen_server:call/2 L182">>,<<"cassim_security:get_security_doc/1 
L58">>,<<"cassim_security:get_security/2 L46">>,<<"chttpd_db:do_db_req/2 
L263">>,<<"chttpd:handle_request/1 L210">>,<<"mochiweb_http:headers/5 
L93">>,<<"proc_lib:init_p_do_apply/3 L237">>]

> if _metadata is there, creating a db does not work
> --
>
> Key: COUCHDB-2657
> URL: https://issues.apache.org/jira/browse/COUCHDB-2657
> Project: CouchDB
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: BigCouch, Database Core
>Reporter: Robert Kowalski
>Priority: Blocker
>
> with the new _setup_cluster endpoint a _metadata db is created.
> when it exists, and we create a db, read it _all_doc immediatly [1] (Fauxton 
> does that) we get:
> `document update conflict`
> [1] 
> http://localhost:8000/sdfsdtest/_all_docs?startkey=%22_design%2F%22&endkey=%22_design0%22&include_docs=true&limit=501



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


[jira] [Commented] (COUCHDB-2657) if _metadata is there, creating a db does not work

2015-04-17 Thread Russell Branca (JIRA)

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

Russell Branca commented on COUCHDB-2657:
-

Thanks for the report [~robertkowalski]. I ported the test script to Python [1] 
and I'm able to reproduce these issues. Deleting the _metadata db and rerunning 
the test works, but I haven't been able to test a fresh start of the dev 
cluster without the _metadata db as it keeps getting recreated.

[~ilyak] where are you observing those failures? Is that during the first run 
of setup? I'm not seeing those.


[1] https://gist.github.com/chewbranca/44e266140cbb74db9c47

> if _metadata is there, creating a db does not work
> --
>
> Key: COUCHDB-2657
> URL: https://issues.apache.org/jira/browse/COUCHDB-2657
> Project: CouchDB
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: BigCouch, Database Core
>Reporter: Robert Kowalski
>Priority: Blocker
>
> with the new _setup_cluster endpoint a _metadata db is created.
> when it exists, and we create a db, read it _all_doc immediatly [1] (Fauxton 
> does that) we get:
> `document update conflict`
> [1] 
> http://localhost:8000/sdfsdtest/_all_docs?startkey=%22_design%2F%22&endkey=%22_design0%22&include_docs=true&limit=501



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


[GitHub] couchdb-fauxton pull request: Add test for hasDataSize function

2015-04-17 Thread asfgit
Github user asfgit closed the pull request at:

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


---
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] [Created] (COUCHDB-2664) Replication failing silently

2015-04-17 Thread Bob Jones (JIRA)
Bob Jones created COUCHDB-2664:
--

 Summary: Replication failing silently
 Key: COUCHDB-2664
 URL: https://issues.apache.org/jira/browse/COUCHDB-2664
 Project: CouchDB
  Issue Type: Bug
  Security Level: public (Regular issues)
  Components: Replication
Reporter: Bob Jones


Have been running couch successfully since 1.1.  Currently running several 
instances of 1.6.0.

I am experiencing a problem where replication reports 100% complete but the 
number of documents do not match.

Have repeatedly dropped replication documents and attempted one time 
replication with no success.

Documents are moving but it never catches up.

Hosts are at AWS so networking between them should be good.

max_dbs_open = 300 on both hosts and only 29 databases on the system

no errors in the couchdb log




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


[GitHub] couchdb-fauxton pull request: Updating Auth module to use React

2015-04-17 Thread benkeen
GitHub user benkeen opened a pull request:

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

Updating Auth module to use React



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

$ git pull https://github.com/benkeen/couchdb-fauxton auth-react

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

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


commit 36c7a95eb31f7ed56bd50f1b32fdf0f360eae7f5
Author: Ben Keen 
Date:   2015-04-16T23:14:27Z

Updating Auth module to use React




---
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: Test for error handling in Active Ta...

2015-04-17 Thread michellephung
Github user michellephung commented on a diff in the pull request:

https://github.com/apache/couchdb-fauxton/pull/388#discussion_r28626362
  
--- Diff: app/addons/activetasks/tests/activetasks.componentsSpec.react.jsx 
---
@@ -70,6 +70,14 @@ define([
 window.confirm.restore && window.confirm.restore();
   });
 
+
+  it('it displays a message instead of an empty table, if there are 
undefined active tasks', function () {
+spy = sinon.spy(Actions, 'setCollection');
--- End diff --

sounds good!


---
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: Test for error handling in Active Ta...

2015-04-17 Thread sebastianrothbucher
Github user sebastianrothbucher commented on a diff in the pull request:

https://github.com/apache/couchdb-fauxton/pull/388#discussion_r28626281
  
--- Diff: app/addons/activetasks/tests/activetasks.componentsSpec.react.jsx 
---
@@ -70,6 +70,14 @@ define([
 window.confirm.restore && window.confirm.restore();
   });
 
+
+  it('it displays a message instead of an empty table, if there are 
undefined active tasks', function () {
+spy = sinon.spy(Actions, 'setCollection');
--- End diff --

actually just leaving out this line does the trick except that we'd have to 
modify afterEach: 
```
if (spy) {
  spy.restore();
  spy = undefined;
}
```



---
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: Test for error handling in Active Ta...

2015-04-17 Thread michellephung
Github user michellephung commented on a diff in the pull request:

https://github.com/apache/couchdb-fauxton/pull/388#discussion_r28626267
  
--- Diff: app/addons/activetasks/tests/activetasks.componentsSpec.react.jsx 
---
@@ -70,6 +70,14 @@ define([
 window.confirm.restore && window.confirm.restore();
   });
 
+
+  it('it displays a message instead of an empty table, if there are 
undefined active tasks', function () {
+spy = sinon.spy(Actions, 'setCollection');
--- End diff --

good point though, it's unclear what's happening.
I can initialize the spy in beforeEach, and then each test will have to 
assign it again, if necessary.


---
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: Test for error handling in Active Ta...

2015-04-17 Thread michellephung
Github user michellephung commented on a diff in the pull request:

https://github.com/apache/couchdb-fauxton/pull/388#discussion_r28626153
  
--- Diff: app/addons/activetasks/tests/activetasks.componentsSpec.react.jsx 
---
@@ -70,6 +70,14 @@ define([
 window.confirm.restore && window.confirm.restore();
   });
 
+
+  it('it displays a message instead of an empty table, if there are 
undefined active tasks', function () {
+spy = sinon.spy(Actions, 'setCollection');
--- End diff --

:/ i'm not really asserting that the spy is called, that's not what i'm 
testing for. but if i leave the spy uninitialized, the afterEach function calls 
spy.restore, and errors at that point.


---
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: Test for error handling in Active Ta...

2015-04-17 Thread sebastianrothbucher
Github user sebastianrothbucher commented on a diff in the pull request:

https://github.com/apache/couchdb-fauxton/pull/388#discussion_r28625892
  
--- Diff: app/addons/activetasks/tests/activetasks.componentsSpec.react.jsx 
---
@@ -70,6 +70,14 @@ define([
 window.confirm.restore && window.confirm.restore();
   });
 
+
+  it('it displays a message instead of an empty table, if there are 
undefined active tasks', function () {
+spy = sinon.spy(Actions, 'setCollection');
--- End diff --

maybe I'm not fully getting it, but we call the method we just mocked? 
Would we not rather leave out this line and see what happens?


---
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: add loading lines to active tasks

2015-04-17 Thread sebastianrothbucher
Github user sebastianrothbucher commented on the pull request:

https://github.com/apache/couchdb-fauxton/pull/386#issuecomment-94062235
  
I do like the idea (and the code - exept for tests as Robert pointed out 
already)


---
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] [Created] (COUCHDB-2663) w:2 property in index docs

2015-04-17 Thread Robert Kowalski (JIRA)
Robert Kowalski created COUCHDB-2663:


 Summary: w:2 property in index docs
 Key: COUCHDB-2663
 URL: https://issues.apache.org/jira/browse/COUCHDB-2663
 Project: CouchDB
  Issue Type: Bug
  Security Level: public (Regular issues)
  Components: Mango
Reporter: Robert Kowalski


Noticed that the write quorum is saved into the indexes by mango:

{code}
{
  "_id": "_design/e4d338e5d6f047749f5399ab998b4fa04ba0c816",
  "_rev": "1-1f37105891681e717ae37dae973bc6a4",
  "language": "query",
  "views": {
"e4d338e5d6f047749f5399ab998b4fa04ba0c816": {
  "map": {
"fields": {
  "_id": "asc"
}
  },
  "reduce": "_count",
  "options": {
"def": {
  "fields": [
"_id"
  ]
},
"w": 2
  }
}
  }
}
{code}

Can we remove it?



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


[GitHub] couchdb-fauxton pull request: Add test for hasDataSize function

2015-04-17 Thread benkeen
Github user benkeen commented on the pull request:

https://github.com/apache/couchdb-fauxton/pull/389#issuecomment-94033544
  
Thanks Michelle, I owe you one +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-fauxton pull request: Add test for hasDataSize function

2015-04-17 Thread michellephung
GitHub user michellephung opened a pull request:

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

Add test for hasDataSize function



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

$ git pull https://github.com/michellephung/couchdb-fauxton 
add-test-for-hasDataSize-function

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

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


commit 1b1fb3d76e21f0e350f215a519fa8d1886acfdea
Author: michelleph...@gmail.com 
Date:   2015-04-17T15:48:09Z

Add test for hasDataSize function




---
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: Test for error handling in Active Ta...

2015-04-17 Thread michellephung
GitHub user michellephung opened a pull request:

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

Test for error handling in Active Tasks



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

$ git pull https://github.com/michellephung/couchdb-fauxton 
Active-Tasks-in-REACT

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

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


commit 93155a79efb1a9262a35968b10c67fcf50bdd679
Author: michelleph...@gmail.com 
Date:   2015-04-17T15:38:59Z

Test for error handling in Active Tasks




---
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.
---


Vote on the CouchDB logo

2015-04-17 Thread Nolan Lawson
+1 for Constantin's. :)

- Nolan

-- 
Nolan Lawson
nolanlawson.com
github.com/nolanlawson


[BLOG] The CouchDB Weekly News is out

2015-04-17 Thread Lena Reinhard
Hi everyone,

this week’s CouchDB Weekly News is out:

http://blog.couchdb.org/2015/04/17/couchdb-weekly-news-april-17-2015/

If you want to help us promote the News, please share them, e.g. in these 
networks:  
Twitter:  https://twitter.com/CouchDB/status/589085821225017344
Reddit:  
http://www.reddit.com/r/CouchDB/comments/32xi91/time_for_another_update_from_the_community_the/
 

G+: https://plus.google.com/u/0/b/109226482722655790973/+CouchDB/posts 

Facebook: 
https://www.facebook.com/permalink.php?story_fbid=642141602484734&id=507603582605204
 

Linkedin: 
https://www.linkedin.com/company/5242010/comments?topic=5994850006685745152&type=U&scope=5242010&stype=C&a=5wP6&goback=%2Ebzo_*1_*1_*1_*1_*1_*1_*1_*1_apache*5couchdb

In case you haven’t joined the CouchDB Advocate yet: we want to invite you to 
join us there and help us spread the word about CouchDB: 
https://couchdb.influitive.com/

Best,
Lena

[GitHub] couchdb-fauxton pull request: add loading lines to active tasks

2015-04-17 Thread michellephung
Github user michellephung commented on the pull request:

https://github.com/apache/couchdb-fauxton/pull/386#issuecomment-93997534
  
Do you like the idea?


---
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: add loading lines to active tasks

2015-04-17 Thread robertkowalski
Github user robertkowalski commented on the pull request:

https://github.com/apache/couchdb-fauxton/pull/386#issuecomment-93959590
  
missing tests, will take a look when tests are present


---
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.
---