David Kiryazi created COUCHDB-3306:
--
Summary: PendingChanges reports wrong value in _active_tasks
Key: COUCHDB-3306
URL: https://issues.apache.org/jira/browse/COUCHDB-3306
Project: CouchDB
[
https://issues.apache.org/jira/browse/COUCHDB-3302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15877308#comment-15877308
]
ASF subversion and git services commented on COUCHDB-3302:
--
Commit
[
https://issues.apache.org/jira/browse/COUCHDB-3302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15877305#comment-15877305
]
ASF GitHub Bot commented on COUCHDB-3302:
-
Github user asfgit closed the pull request at:
[
https://issues.apache.org/jira/browse/COUCHDB-3302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15877303#comment-15877303
]
ASF subversion and git services commented on COUCHDB-3302:
--
Commit
Github user rnewson commented on the issue:
https://github.com/apache/couchdb-fabric/pull/89
+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
Github user tonysun83 commented on the issue:
https://github.com/apache/couchdb-couch/pull/229
@iilyak : The only two error types I can think of are when the input value
is invalid and also what @kxepal mentioned (the map function errors) which I
forgot to take care of. In any case,
Github user kxepal commented on the issue:
https://github.com/apache/couchdb-couch/pull/229
For map functions errors we return the response in the following format:
```
{"total_rows":14,"offset":0,"rows":[
{"key":1,"error":"not_found"}
]}
```
It's hard to
Github user nickva commented on the issue:
https://github.com/apache/couchdb-fabric/pull/89
Can now PUT aprox a 1Gb attachment
Could never do that before:
```
./attach_large.py --size=10 --mintime=120
...
> sent data in 0.000 sec res: None
>
Github user kxepal commented on the issue:
https://github.com/apache/couchdb-couch/pull/229
How the clients should handle such kind of response?
It has the result data and it has some errons. Should the result be
handled? Or an exception being throw?
I think there should
Github user iilyak commented on the issue:
https://github.com/apache/couchdb-couch/pull/229
What about other kinds of errors? Should we consider returning errors as:
```
"value": {
"key": [],
"value": ,
"errors": {
[
https://issues.apache.org/jira/browse/COUCHDB-3305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15876949#comment-15876949
]
ASF GitHub Bot commented on COUCHDB-3305:
-
GitHub user tonysun83 opened a pull request:
GitHub user tonysun83 opened a pull request:
https://github.com/apache/couchdb-couch/pull/229
Return error row instead of crashing
When input is invalid for built in reducers, we return an error row
instead of crashing. Thanks to @davisp for providing the elegant
solution.
[
https://issues.apache.org/jira/browse/COUCHDB-3302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15876925#comment-15876925
]
ASF GitHub Bot commented on COUCHDB-3302:
-
GitHub user nickva opened a pull request:
GitHub user nickva opened a pull request:
https://github.com/apache/couchdb-fabric/pull/89
Prevent attachment upload from timing out during update_docs fabric call
Currently if an attachment was large enough or the connection was slow
enough
such that it took more than
Tony Sun created COUCHDB-3305:
-
Summary: don't crash with invalid built in reducer function
Key: COUCHDB-3305
URL: https://issues.apache.org/jira/browse/COUCHDB-3305
Project: CouchDB
Issue Type:
Github user millayr closed the pull request at:
https://github.com/apache/couchdb-fauxton/pull/835
---
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
Github user millayr closed the pull request at:
https://github.com/apache/couchdb-fauxton/pull/828
---
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
[
https://issues.apache.org/jira/browse/COUCHDB-3255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15876384#comment-15876384
]
ASF subversion and git services commented on COUCHDB-3255:
--
Commit
[
https://issues.apache.org/jira/browse/COUCHDB-3287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15876381#comment-15876381
]
ASF subversion and git services commented on COUCHDB-3287:
--
Commit
[
https://issues.apache.org/jira/browse/COUCHDB-3287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15876380#comment-15876380
]
ASF subversion and git services commented on COUCHDB-3287:
--
Commit
[
https://issues.apache.org/jira/browse/COUCHDB-3287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15876383#comment-15876383
]
ASF subversion and git services commented on COUCHDB-3287:
--
Commit
[
https://issues.apache.org/jira/browse/COUCHDB-3287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15876378#comment-15876378
]
ASF subversion and git services commented on COUCHDB-3287:
--
Commit
[
https://issues.apache.org/jira/browse/COUCHDB-3288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15876377#comment-15876377
]
ASF subversion and git services commented on COUCHDB-3288:
--
Commit
[
https://issues.apache.org/jira/browse/COUCHDB-3287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15876379#comment-15876379
]
ASF subversion and git services commented on COUCHDB-3287:
--
Commit
[
https://issues.apache.org/jira/browse/COUCHDB-3288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15876366#comment-15876366
]
ASF subversion and git services commented on COUCHDB-3288:
--
Commit
[
https://issues.apache.org/jira/browse/COUCHDB-3288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15876369#comment-15876369
]
ASF subversion and git services commented on COUCHDB-3288:
--
Commit
[
https://issues.apache.org/jira/browse/COUCHDB-3287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15876374#comment-15876374
]
ASF subversion and git services commented on COUCHDB-3287:
--
Commit
[
https://issues.apache.org/jira/browse/COUCHDB-3288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15876363#comment-15876363
]
ASF subversion and git services commented on COUCHDB-3288:
--
Commit
[
https://issues.apache.org/jira/browse/COUCHDB-3288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15876372#comment-15876372
]
ASF subversion and git services commented on COUCHDB-3288:
--
Commit
[
https://issues.apache.org/jira/browse/COUCHDB-3288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15876362#comment-15876362
]
ASF subversion and git services commented on COUCHDB-3288:
--
Commit
[
https://issues.apache.org/jira/browse/COUCHDB-3288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15876364#comment-15876364
]
ASF subversion and git services commented on COUCHDB-3288:
--
Commit
[
https://issues.apache.org/jira/browse/COUCHDB-3288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15876376#comment-15876376
]
ASF subversion and git services commented on COUCHDB-3288:
--
Commit
[
https://issues.apache.org/jira/browse/COUCHDB-3288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15876373#comment-15876373
]
ASF subversion and git services commented on COUCHDB-3288:
--
Commit
[
https://issues.apache.org/jira/browse/COUCHDB-3288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15876371#comment-15876371
]
ASF subversion and git services commented on COUCHDB-3288:
--
Commit
[
https://issues.apache.org/jira/browse/COUCHDB-3293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15876361#comment-15876361
]
ASF subversion and git services commented on COUCHDB-3293:
--
Commit
[
https://issues.apache.org/jira/browse/COUCHDB-3288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15876365#comment-15876365
]
ASF subversion and git services commented on COUCHDB-3288:
--
Commit
[
https://issues.apache.org/jira/browse/COUCHDB-3293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15876368#comment-15876368
]
ASF subversion and git services commented on COUCHDB-3293:
--
Commit
[
https://issues.apache.org/jira/browse/COUCHDB-3288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15876375#comment-15876375
]
ASF subversion and git services commented on COUCHDB-3288:
--
Commit
[
https://issues.apache.org/jira/browse/COUCHDB-3288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15876370#comment-15876370
]
ASF subversion and git services commented on COUCHDB-3288:
--
Commit
[
https://issues.apache.org/jira/browse/COUCHDB-3288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15876319#comment-15876319
]
ASF subversion and git services commented on COUCHDB-3288:
--
Commit
[
https://issues.apache.org/jira/browse/COUCHDB-3302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15876250#comment-15876250
]
Nick Vatamaniuc commented on COUCHDB-3302:
--
fabric_doc_attachments used when PUT-ing individual
[
https://issues.apache.org/jira/browse/COUCHDB-3302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15876234#comment-15876234
]
Paul Joseph Davis commented on COUCHDB-3302:
You logged that nothing sends that message?
Github user glynnbird commented on the issue:
https://github.com/apache/couchdb-nano/pull/5
+1 from me
---
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
Github user garrensmith commented on the issue:
https://github.com/apache/couchdb-nano/pull/5
@glynnbird could you review this and then I can merge
---
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 mikerhodes commented on the issue:
https://github.com/apache/couchdb-chttpd/pull/114
@tonysun83 fwiw I think the suggestion is still to have the
`max_http_body_size` new config setting in addition to making
`max_document_size` work as it currently does, but sounds like we
Github user millayr commented on the issue:
https://github.com/apache/couchdb-fauxton/pull/861
+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
Github user asfgit closed the pull request at:
https://github.com/apache/couchdb-fauxton/pull/861
---
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
Github user millayr commented on a diff in the pull request:
https://github.com/apache/couchdb-fauxton/pull/861#discussion_r102219150
--- Diff: Gruntfile.js ---
@@ -72,6 +72,7 @@ module.exports = function (grunt) {
settings.template[key].app.i18n = i18n;
});
GitHub user garrensmith opened a pull request:
https://github.com/apache/couchdb-fauxton/pull/861
fix deployment to work with styles.css
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/garrensmith/couchdb-fauxton
Github user garrensmith commented on the issue:
https://github.com/apache/couchdb-fauxton/pull/860
+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
50 matches
Mail list logo
