Hi Robert,
Thanks for the reply. I'll start on the tasks and let you updated on the
progress.
Regards,
Nishani
On Thu, Apr 2, 2015 at 12:30 AM, Robert Kowalski wrote:
> Hi Nishani,
>
> I wrote a small tutorial last week:
>
> It would be nice if you can finish the tutorial at
> https://github.c
[
https://issues.apache.org/jira/browse/COUCHDB-2651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14393492#comment-14393492
]
ASF subversion and git services commented on COUCHDB-2651:
--
Com
Hi everyone,
the latest CouchDB Weekly News is out:
http://blog.couchdb.org/2015/04/02/couchdb-weekly-news-april-02-2015/
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/
If y
Github user sebastianrothbucher commented on the pull request:
https://github.com/apache/couchdb/pull/310#issuecomment-89025857
Well, at least it would serve its purpose here:
```
http://somecouch:5984/_design/somedoc";
download="somedoc.txt">download it!
```
will trig
Github user kxepal commented on the pull request:
https://github.com/apache/couchdb/pull/310#issuecomment-89023281
Sounds as not suitable for us, right?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does
Github user robertkowalski commented on the pull request:
https://github.com/apache/couchdb/pull/310#issuecomment-89017725
so we could use it if we had base64 data urls containing the document
available for fauxton without Content-Disposition header
---
If your project is set up for
Github user robertkowalski commented on the pull request:
https://github.com/apache/couchdb/pull/310#issuecomment-89017298
HTML 5 does provide a download attribute, with the following restrictions:
```
Can be used with blob: URLs and data: URLs, to make it easy for users to
Github user robertkowalski commented on the pull request:
https://github.com/apache/couchdb/pull/310#issuecomment-89017415
source:
https://developer.mozilla.org/en-US/docs/Web/HTML/Element/a#attr-download
---
If your project is set up for it, you can reply to this email and have your
Github user benkeen closed the pull request at:
https://github.com/apache/couchdb-fauxton/pull/354
---
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 featu
Github user benkeen commented on the pull request:
https://github.com/apache/couchdb-fauxton/pull/354#issuecomment-88995262
Merged as e229a45
---
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 t
Github user kxepal commented on a diff in the pull request:
https://github.com/apache/couchdb/pull/312#discussion_r27681224
--- Diff: build-aux/print-committerlist.sh ---
@@ -0,0 +1,68 @@
+#!/bin/sh
+#
+# Licensed under the Apache License, Version 2.0 (the "License"); yo
Github user kxepal commented on the pull request:
https://github.com/apache/couchdb/pull/312#issuecomment-88992737
> the thanks file was never ordered alphabetically and i don't see why it
should be.
To easily notice duplicates and actual authors? Jason Smith mentioned three
times
Github user sebastianrothbucher commented on the pull request:
https://github.com/apache/couchdb/pull/312#issuecomment-88991042
for me, it's totally OK as it is, no need to sort
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as w
Github user robertkowalski commented on a diff in the pull request:
https://github.com/apache/couchdb/pull/312#discussion_r27680459
--- Diff: build-aux/print-committerlist.sh ---
@@ -0,0 +1,68 @@
+#!/bin/sh
+#
+# Licensed under the Apache License, Version 2.0 (the "Licen
Github user robertkowalski commented on the pull request:
https://github.com/apache/couchdb/pull/312#issuecomment-88990194
building the thanks file on 1.x currently works like this:
1. take content from THANKS.in and pipe it into the THANKS file
2. get committer list from d
Github user sebastianrothbucher commented on the pull request:
https://github.com/apache/couchdb/pull/311#issuecomment-88928603
the restart fail in https://travis-ci.org/apache/couchdb/jobs/56791906 is a
heisenbug - it happens arbitrarily when timeouts are too small. Otherwise it
look
Github user asfgit closed the pull request at:
https://github.com/apache/couchdb/pull/311
---
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 ena
[
https://issues.apache.org/jira/browse/COUCHDB-2655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14392554#comment-14392554
]
ASF subversion and git services commented on COUCHDB-2655:
--
Com
[
https://issues.apache.org/jira/browse/COUCHDB-2655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14392555#comment-14392555
]
ASF subversion and git services commented on COUCHDB-2655:
--
Com
[
https://issues.apache.org/jira/browse/COUCHDB-2655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14392558#comment-14392558
]
ASF subversion and git services commented on COUCHDB-2655:
--
Com
[
https://issues.apache.org/jira/browse/COUCHDB-2655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14392552#comment-14392552
]
ASF subversion and git services commented on COUCHDB-2655:
--
Com
Robert Newson created COUCHDB-2655:
--
Summary: Indicate it read quorum ("r") was reached
Key: COUCHDB-2655
URL: https://issues.apache.org/jira/browse/COUCHDB-2655
Project: CouchDB
Issue Type:
Github user robertkowalski commented on the pull request:
https://github.com/apache/couchdb-fauxton/pull/355#issuecomment-88871957
changed the commit message to something meaningful
merged as a03be3c548e189a5c319815eece17c5d5072d38a because the build
depends on it.
--
Github user robertkowalski commented on the pull request:
https://github.com/apache/couchdb-fauxton/pull/355#issuecomment-88871175
+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 feat
To move this along I have COUCHDB-2655 and three branches with a working
solution;
https://git-wip-us.apache.org/repos/asf?p=couchdb-chttpd.git;h=b408ce5
https://git-wip-us.apache.org/repos/asf?p=couchdb-couch.git;h=7d811d3
https://git-wip-us.apache.org/repos/asf?p=couchdb-fabric.git;h=90e9691
A
[
https://issues.apache.org/jira/browse/COUCHDB-1652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14392449#comment-14392449
]
Robert Newson commented on COUCHDB-1652:
does this ever happen without the compa
Yeah, not a bad idea. An extra query arg (akin to open_revs=all,
conflicts=true, etc) would avoid compatibility breaks and would clearly put the
onus on those supplying it to tolerate the presence of the extra reserved field.
+1
> On 2 Apr 2015, at 10:32, Benjamin Bastian wrote:
>
> What ab
What about adding an optional query parameter to indicate whether or not
Couch should include the _r_met flag in the document body/bodies
(defaulting to false)? That wouldn't break older clients and it'd work for
the bulk API as well. As far as the case where there are conflicts, it
seems like the
Paul outlined his previous efforts to introduce this indication, and the
problems he faced doing so. Can we come up with an acceptable mechanism?
A different status code will break a lot of users. While the http spec says you
can treat any 2xx code as success, plenty of libraries, etc, only rec
[
https://issues.apache.org/jira/browse/COUCHDB-2651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14392338#comment-14392338
]
ASF subversion and git services commented on COUCHDB-2651:
--
Com
30 matches
Mail list logo
