[jira] [Created] (COUCHDB-3175) When PUT-ing a multipart/related doc with attachment get a 500 error on md5 mismatch

Nick Vatamaniuc created COUCHDB-3175: Summary: When PUT-ing a multipart/related doc with attachment get a 500 error on md5 mismatch Key: COUCHDB-3175 URL: https://issues.apache.org/jira/browse/COUCHDB-3175

[jira] [Commented] (COUCHDB-3174) max_document_size setting can by bypassed by issuing multipart/related requests

[ https://issues.apache.org/jira/browse/COUCHDB-3174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15544234#comment-15544234 ] Nick Vatamaniuc commented on COUCHDB-3174: -- The problem seems to be here:

[jira] [Created] (COUCHDB-3174) max_document_size setting can by bypassed by issuing multipart/related requests

Nick Vatamaniuc created COUCHDB-3174: Summary: max_document_size setting can by bypassed by issuing multipart/related requests Key: COUCHDB-3174 URL: https://issues.apache.org/jira/browse/COUCHDB-3174

[GitHub] couchdb-couch-mrview issue #56: Make Query Limit Results Configurable

Github user rnewson commented on the issue: https://github.com/apache/couchdb-couch-mrview/pull/56 I still think the default behaviour of _all_docs, _changes and _view should be to return everything that the parameters dictate (that is, we should fix the default, the longstanding

[GitHub] couchdb-couch pull request #185: 3061 adaptive header search

Github user jaydoane commented on a diff in the pull request: https://github.com/apache/couchdb-couch/pull/185#discussion_r81645651 --- Diff: src/couch_file.erl --- @@ -531,27 +537,96 @@ find_header(Fd, Block) -> {ok, Bin} -> {ok, Bin}; _Error ->

[GitHub] couchdb-couch-replicator issue #49: Fix replicator handling of max_document_...

Github user rnewson commented on the issue: https://github.com/apache/couchdb-couch-replicator/pull/49 +1 , v nice! --- 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

[jira] [Commented] (COUCHDB-3168) Replicator doesn't handle well writing documents to a target db which has a small max_document_size

[ https://issues.apache.org/jira/browse/COUCHDB-3168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15543211#comment-15543211 ] ASF GitHub Bot commented on COUCHDB-3168: - GitHub user nickva opened a pull request:

[GitHub] couchdb-couch-replicator pull request #49: Fix replicator handling of max_do...

GitHub user nickva opened a pull request: https://github.com/apache/couchdb-couch-replicator/pull/49 Fix replicator handling of max_document_size when posting to _bulk_docs Currently `max_document_size` setting is a misnomer, it actually configures maximum request body size. For

[GitHub] couchdb-couch-replicator issue #48: Port HTTP 429 Commits

Github user tonysun83 commented on the issue: https://github.com/apache/couchdb-couch-replicator/pull/48 @kxepal: made every macro configurable --- 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

[GitHub] couchdb-couch-log issue #16: a systemd-journald compatible log output on std...

Github user gdamjan commented on the issue: https://github.com/apache/couchdb-couch-log/pull/16 @kxepal I guess so, let me see what the systemd community thinks too (maybe there's previous precedent). --- If your project is set up for it, you can reply to this email and have your

[GitHub] couchdb-couch-log issue #16: a systemd-journald compatible log output on std...

Github user kxepal commented on the issue: https://github.com/apache/couchdb-couch-log/pull/16 LGFM, but I'm not systemd user. @gdamjan may be name it journald to direct match with the service name without leaving a room for confusion? --- If your project is set up for it,

[GitHub] couchdb-couch-mrview issue #56: Make Query Limit Results Configurable

Github user kxepal commented on the issue: https://github.com/apache/couchdb-couch-mrview/pull/56 @tonysun83 > I still think we should make all our index limits configurable, starting with views. That's a good position while requesting indexes is not cheap. Say, there

[GitHub] couchdb-couch-log issue #16: a systemd-journald compatible log output on std...

Github user gdamjan commented on the issue: https://github.com/apache/couchdb-couch-log/pull/16 this setup works fine when configured in in `local.ini`: ``` [log] writer = journal ``` but perhaps it would be better if the writer can be forced from the systemd

[GitHub] couchdb-couch-log pull request #16: a systemd-journald compatible log output...

GitHub user gdamjan opened a pull request: https://github.com/apache/couchdb-couch-log/pull/16 a systemd-journald compatible log output on stderr based on the stderr logger but changed: - doesn't output the timestamp, the journal already has a timestamp - output the log

[GitHub] couchdb-couch pull request #185: 3061 adaptive header search

Github user davisp commented on a diff in the pull request: https://github.com/apache/couchdb-couch/pull/185#discussion_r81586171 --- Diff: src/couch_file.erl --- @@ -531,27 +537,96 @@ find_header(Fd, Block) -> {ok, Bin} -> {ok, Bin}; _Error -> -

[jira] [Commented] (COUCHDB-3007) Navigating to 'Main config' fails after visiting 'CORS'

[ https://issues.apache.org/jira/browse/COUCHDB-3007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15542126#comment-15542126 ] ASF GitHub Bot commented on COUCHDB-3007: - Github user samk1 closed the pull request at:

[GitHub] couchdb-fauxton pull request #750: Config section reactjs rewrite

Github user samk1 closed the pull request at: https://github.com/apache/couchdb-fauxton/pull/750 --- 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] couchdb-fauxton issue #750: Config section reactjs rewrite

Github user samk1 commented on the issue: https://github.com/apache/couchdb-fauxton/pull/750 Done thankyou. On 3 October 2016 at 19:05, garren smith wrote: > @samk1 could you close this PR. We can't close > it

[jira] [Created] (COUCHDB-3173) Views return corrupt data for text fields containing non-BMP characters

Loke created COUCHDB-3173: - Summary: Views return corrupt data for text fields containing non-BMP characters Key: COUCHDB-3173 URL: https://issues.apache.org/jira/browse/COUCHDB-3173 Project: CouchDB

[GitHub] couchdb-fauxton issue #750: Config section reactjs rewrite

Github user garrensmith commented on the issue: https://github.com/apache/couchdb-fauxton/pull/750 @samk1 could you close this PR. We can't close it from our side. And the work is now all merged. --- If your project is set up for it, you can reply to this email and have your reply

[GitHub] couchdb-fauxton issue #781: Make jump to database async

Github user garrensmith commented on the issue: https://github.com/apache/couchdb-fauxton/pull/781 This is merged --- 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