Garren Smith | 20 Dec 16:49 2014
Picon

[DISCUSS] Fauxton 2015 plans

Hi Everyone,

This year has been a really busy and exciting year for the Fauxton team. We have worked on many new features.
We have also had a lot more contributors which is fantastic. We are now up to 31 contributors to the Fauxton
code base. Fauxton is being used more and more. It will replace Futon in CouchDB 2.0 as the default web user
interface. It is also used in Pouchdb-server [1]. Fauxton is also used as the base of the Cloudant
dashboard, which has 4 different versions.

With the year nearly up we are making plans for what we will be focusing on next year. I’ve tried to
summarise what we want to do.

From the beginning we have used backbone.js to build Fauxton. This has worked well but we are pushing
Backbone.js further than what it was designed to do and are starting to feel its limits. Over the year we
have outgrown the custom framework we built on top of Backbone.js and it adds unnecessary complexity. It
also made building new features more complex than we would like, which makes it difficult for new
contributors to get involved. 

We have been doing a fair amount of research and want to replace Backbone.js with React.js combined with the
Flux architecture. We want to do this in an iterative way so that we don’t limit any new feature
development or add any unnecessary bugs - the cool thing about React is that an iterative approach is
possible and many other teams [4] [5] [6] have done this with great success. Adding React.js to a
backbone.js project is easy. It doesn't require rewriting or removing. Its purely a refactor effort. As a
proof of concept We’ve taken the Index/View Editor which has the most complex code and rebuilt most of it
in React.js [2]. I’ve also added some nice unit tests because writing tests for React.js is a lot easier
than backbone.js.

We are very excited about doing this as we believe it will really simplify our codebase and  should make it
much easier for new contributors to get involved. We should have a pull request for the basic React.js
setup work in the New Year. If you want to take a look at our research-prototype, that work is being done here
[2]. For a nice introduction to React.js, see [7]. 
(Continue reading)

ILYA (JIRA | 19 Dec 21:16 2014
Picon

[jira] [Created] (COUCHDB-2525) npm and grunt dependencies need to be documented

ILYA created COUCHDB-2525:
-----------------------------

             Summary: npm and grunt dependencies need to be documented
                 Key: COUCHDB-2525
                 URL: https://issues.apache.org/jira/browse/COUCHDB-2525
             Project: CouchDB
          Issue Type: Documentation
      Security Level: public (Regular issues)
            Reporter: ILYA

Recently Makefile was updated to build fauxton. However documentation doesn't contain new build
dependencies. 

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

ASF GitHub Bot (JIRA | 19 Dec 19:52 2014
Picon

[jira] [Commented] (COUCHDB-2524) clearing out .delete directories in couch_server:init prevents boot of the node


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

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

GitHub user iilyak opened a pull request:

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

    Modify init_delete_dir to be async

    In the case when .delete directory contains lots of files.
    The deletion of the directory leads to timeout in the supervisor.
    Which in it's turn kills the node.
    So we rename original directory so couchdb cannot find it.
    Then we remove files from renamed directory asynchronously.

    COUCHDB-2524

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

    $ git pull https://github.com/iilyak/couchdb-couch 2524-cleanup-delete-on-init

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

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

(Continue reading)

iilyak | 19 Dec 19:51 2014
Picon

[GitHub] couchdb-couch pull request: Modify init_delete_dir to be async

GitHub user iilyak opened a pull request:

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

    Modify init_delete_dir to be async

    In the case when .delete directory contains lots of files.
    The deletion of the directory leads to timeout in the supervisor.
    Which in it's turn kills the node.
    So we rename original directory so couchdb cannot find it.
    Then we remove files from renamed directory asynchronously.

    COUCHDB-2524

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

    $ git pull https://github.com/iilyak/couchdb-couch 2524-cleanup-delete-on-init

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

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

----
commit a14ecb1cb8439b00a69604ead6e7eff3bd2686ee
Author: ILYA Khlopotov <iilyak@...>
(Continue reading)

ILYA (JIRA | 19 Dec 19:43 2014
Picon

[jira] [Created] (COUCHDB-2524) clearing out .delete directories in couch_server:init prevents boot of the node

ILYA created COUCHDB-2524:
-----------------------------

             Summary: clearing out .delete directories in couch_server:init prevents boot of the node
                 Key: COUCHDB-2524
                 URL: https://issues.apache.org/jira/browse/COUCHDB-2524
             Project: CouchDB
          Issue Type: Bug
      Security Level: public (Regular issues)
            Reporter: ILYA

If .delete directory contains lots of files. The deletion of the directory leads to timeout in the
supervisor. Which in it's turn kills the node. 

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

ASF GitHub Bot (JIRA | 19 Dec 17:41 2014
Picon

[jira] [Commented] (COUCHDB-1145) As a CouchApp developer, I'd like access to a listing of local-only (_local) docs.


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

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

GitHub user iilyak opened a pull request:

    https://github.com/apache/couchdb-fabric/pull/8

    Don't do manual filtering of _design docs

    Since namespace support was added we can rely on it instead

    COUCHDB-1145

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

    $ git pull https://github.com/iilyak/couchdb-fabric 1145-_local_docs-handler

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

    https://github.com/apache/couchdb-fabric/pull/8.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 #8
(Continue reading)

iilyak | 19 Dec 17:41 2014
Picon

[GitHub] couchdb-fabric pull request: Don't do manual filtering of _design ...

GitHub user iilyak opened a pull request:

    https://github.com/apache/couchdb-fabric/pull/8

    Don't do manual filtering of _design docs

    Since namespace support was added we can rely on it instead

    COUCHDB-1145

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

    $ git pull https://github.com/iilyak/couchdb-fabric 1145-_local_docs-handler

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

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

----
commit f44e627ed883f122bd9c78dc51b1578f13040423
Author: ILYA Khlopotov <iilyak@...>
Date:   2014-12-19T16:36:05Z

    Don't do manual filtering of _design docs

(Continue reading)

Noah Slater | 19 Dec 15:32 2014
Picon

Fwd: The Apache Software Foundation publishes long-overdue Code Of Conduct

FYI :D

---------- Forwarded message ----------
From: *Sally Khudairi* <sk@...>
Date: Friday, 19 December 2014
Subject: The Apache Software Foundation publishes long-overdue Code Of
Conduct
To: Apache Announce List <announce@...>

>> this announcement is available online at http://s.apache.org/dGR

We pride ourselves at The Apache Software Foundation on our principles of
"community over code" and "don't be a jerk". But, alas, we've been slow to
codify some of these things in public. Part of this, I'm sure, is that it’s
easy to think we all just know how we're supposed to treat people, and so
you shouldn't have to say, right?

But, of course, you do have to say. In part because some people don't know
[1]. And in part because it’s important that we communicate our values [2]
to the people in our community, and to people who might be considering
joining our community. There has been a recent push in tech circles to
include a Code of Conduct at events, conferences, etc. (Ashe Dryden
maintains an introductory resource for learning more about how Codes of
Conduct can help.) Increasingly, open source projects are adopting a Code
of Conduct too, and we think this is a good idea that could help improve
open source as a whole.

At ApacheCon, I was approached by Joan Touzet, an active member of the
Apache CouchDB community, who had noted that we referenced a Code of
Conduct on the main ASF website, but that no such document actually existed
(Continue reading)

Lena Reinhard | 19 Dec 12:22 2014

[BLOG] The CouchDB Weekly News and Highlights in 2014 are out

Hi everyone,

this week’s CouchDB Weekly News is out, this time with many highlights from
2014:

http://blog.couchdb.org/2014/12/19/couchdb-weekly-news-december-19-2014-and-couchdb-highlights-in-2014/

Thanks to Andy, Jan and Akshat for their contributions.

We want to ask you to help us promote the News, this is also a way to
contribute to the project –
Twitter:  https://twitter.com/CouchDB/status/545897769391890432
Reddit:
http://www.reddit.com/r/CouchDB/comments/2ps1rr/couchdb_weekly_news_december_19_2014_and_couchdb/
G+:
https://plus.google.com/b/109226482722655790973/+CouchDB/posts/D52no8zKZet
Facebook:
https://www.facebook.com/permalink.php?story_fbid=604937966205098&id=507603582605204
Linkedin:
https://www.linkedin.com/company/5242010/comments?topic=5951663846908248064&type=U&scope=5242010&stype=C&a=jZvy&goback=.bzo_*1_*1_*1_*1_*1_*1_*1_apache*5couchdb

This is the last issue of the Weekly News in 2014, we'll be back on January
08, 2015. Thanks to everyone who supported and shared the News this year.

Best,
Lena
Will Holley (JIRA | 19 Dec 11:06 2014
Picon

[jira] [Created] (COUCHDB-2523) CouchDB 2.0: Specifying startkey/endkey parameters alongside a keys parameter when querying /_all_docs should be invalid

Will Holley created COUCHDB-2523:
------------------------------------

             Summary: CouchDB 2.0: Specifying startkey/endkey parameters alongside a keys parameter when querying
/_all_docs should be invalid
                 Key: COUCHDB-2523
                 URL: https://issues.apache.org/jira/browse/COUCHDB-2523
             Project: CouchDB
          Issue Type: Bug
      Security Level: public (Regular issues)
          Components: Database Core
            Reporter: Will Holley

CouchDB 1.X validates that the combination of query parameters to _all_docs is valid. For instance, you
cannot specify keys and also startkey/endkey:

{code}
curl -g -XGET 'http://127.0.0.1:5984/testdb/_all_docs?keys=["a"]&startkey="a"' 
{"error":"query_parse_error","reason":"`keys` is incompatible with `key`, `start_key` and `end_key`"}
{code}

In CouchDB 2.0, there is no such validation:
{code}
curl -g -XGET 'http://127.0.0.1:15984/testdb/_all_docs?keys=["a"]&startkey="a"'
{"total_rows":5,"rows":[
{"id":"a","key":"a","value":{"rev":"1-4c6114c65e295552ab1019e2b046b10e"}}
]}
{code}

--
(Continue reading)

Alexander Shorin (JIRA | 19 Dec 11:04 2014
Picon

[jira] [Closed] (COUCHDB-2522) CouchDB 2.0 /_changes feed does not return full attachment data with attachments=true


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

Alexander Shorin closed COUCHDB-2522.
-------------------------------------
    Resolution: Duplicate

While you make it better and with examples, there is already another issue about.

> CouchDB 2.0 /_changes feed does not return full attachment data with attachments=true
> -------------------------------------------------------------------------------------
>
>                 Key: COUCHDB-2522
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-2522
>             Project: CouchDB
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: Database Core
>            Reporter: Glynn Bird
>
> In CouchDB 1.6, if a document is created with an attachment, and the _changes feed is consumed with
'?include_docs=true&attachments=true', the full attachments are seen in the feed e.g.:
> {Code}
> $ curl -X DELETE http://127.0.0.1:5984/test
> {"ok":true}
> ~$ curl -X PUT http://127.0.0.1:5984/test
> {"ok":true}
> ~$ curl -X POST http://127.0.0.1:5984/test -H 'Content-type:application/json' -d '{ "id": "bob",
"_attachments": { "foo.txt": {"content_type": "text/plain","data": "holy moly"} } }'
(Continue reading)


Gmane