nickva commented on issue #1171: couchdb unable to run on FIPS enabled CentOS
URL: https://github.com/apache/couchdb/issues/1171#issuecomment-370601327
Like @rnewson mentioned it is about the FIPS check.
`erlang:md5` seems to be there in every supported Erlang version R16B03 ->
rnewson commented on issue #373: Add global handler for delegated auth
URL: https://github.com/apache/couchdb/pull/373#issuecomment-370590745
no interest from me.
This is an automated message from the Apache Git Service.
To
rnewson commented on issue #1171: couchdb unable to run on FIPS enabled CentOS
URL: https://github.com/apache/couchdb/issues/1171#issuecomment-370589633
I was referring the FIPS_mode() function.
This is an automated message
wohali commented on issue #1199: Prevent access to Fauxton on node-local port
(5986)
URL: https://github.com/apache/couchdb/pull/1199#issuecomment-370574453
@rnewson I've moved the CSP tests over to chttpd, where they should be
anyway, and of course they pass with flying colours because
Yay, we passed. https://builds.apache.org/job/CouchDB/job/master/203/
wohali commented on issue #1199: Prevent access to Fauxton on node-local port
(5986)
URL: https://github.com/apache/couchdb/pull/1199#issuecomment-370565054
@janl Hm, if we bind chttpd to 0.0.0.0 it could be tricky to determine the
right IP address to choose, 127.0.0.1 might not be
wohali opened a new pull request #253: Remove mention of Fauxton on port 5986
URL: https://github.com/apache/couchdb-documentation/pull/253
See apache/couchdb#1198 for detail.
Even without apache/couchdb#1199 landing, this will at least stop directing
people to use a feature we
wohali closed pull request #334: Backport CSRF feature
URL: https://github.com/apache/couchdb/pull/334
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (from a
wohali commented on issue #334: Backport CSRF feature
URL: https://github.com/apache/couchdb/pull/334#issuecomment-370560677
I think new development has died for 1.x at this point.
This is an automated message from the Apache
wohali commented on issue #366: Allow server admins to retrieve an auth token
for any other user
URL: https://github.com/apache/couchdb/pull/366#issuecomment-370560506
I'm going to close this out, simply because new feature development for 1.x
has ended.
I'd still very much like to
wohali closed pull request #366: Allow server admins to retrieve an auth token
for any other user
URL: https://github.com/apache/couchdb/pull/366
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
wohali commented on issue #373: Add global handler for delegated auth
URL: https://github.com/apache/couchdb/pull/373#issuecomment-370560095
Ping. Cleaning up old stuff. Any interest in reviving this or instead taking
https://github.com/cloudant/delegated_auth
davisp closed pull request #1201: This fixes couch_bt_engine:fold_local_docs/4
URL: https://github.com/apache/couchdb/pull/1201
This is an automated message from the Apache Git Service.
To respond to the message, please log
wohali closed issue #20: Empty debian binary-i386 packages
URL: https://github.com/apache/couchdb-pkg/issues/20
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and
wohali commented on issue #20: Empty debian binary-i386 packages
URL: https://github.com/apache/couchdb-pkg/issues/20#issuecomment-370542139
Apache CouchDB is not building 32-bit convenience packages, and does not
intend to do so in the future.
You may be able to build your own
elistevens commented on issue #1200: [DISCUSS] CouchDB Request Size Limits
URL: https://github.com/apache/couchdb/pull/1200#issuecomment-370542104
I'd like to add that if iii.1 moves forward, I'd like to have some
information about what impact setting `max_http_request_size` to large
oliverdain commented on issue #252: Suggested edit to make clear what a quorum
actually represents.
URL:
https://github.com/apache/couchdb-documentation/pull/252#issuecomment-370540368
@flimzy what's your process? Do you do the merge or should I do that?
Thanks again for the
flimzy commented on issue #252: Suggested edit to make clear what a quorum
actually represents.
URL:
https://github.com/apache/couchdb-documentation/pull/252#issuecomment-370539721
+1
This is an automated message from the
lune opened a new issue #20: Empty debian binary-i386 packages
URL: https://github.com/apache/couchdb-pkg/issues/20
Not sure, if this is the right place to submit the issue, please let me know
otherwise.
Unable to install coucbdb using the steps listed at
Yay, we passed. https://builds.apache.org/job/CouchDB/job/master/202/
Antonio-Maranhao opened a new pull request #1058: Allow setting the protocol of
the couchdb URL for nightwatch tests
URL: https://github.com/apache/couchdb-fauxton/pull/1058
## Overview
Currently the couchDB URL used by Nightwatch is hardcoded to use HTTP.
This PR adds the new
nickva closed issue #1153: Flexible replicator client auth + session support
URL: https://github.com/apache/couchdb/issues/1153
This is an automated message from the Apache Git Service.
To respond to the message, please log
nickva closed pull request #1176: Implement pluggable authentication and
session support for replicator
URL: https://github.com/apache/couchdb/pull/1176
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of
elistevens commented on issue #1200: [DISCUSS] CouchDB Request Size Limits
URL: https://github.com/apache/couchdb/pull/1200#issuecomment-370512799
I have a concrete use case that I don't think is well-served by iii.1:
- I have some documents with many small attachments
- I have
oliverdain commented on issue #252: Suggested edit to make clear what a quorum
actually represents.
URL:
https://github.com/apache/couchdb-documentation/pull/252#issuecomment-370511614
All fixed. Thanks for the review.
This
nickva commented on issue #1200: [DISCUSS] CouchDB Request Size Limits
URL: https://github.com/apache/couchdb/pull/1200#issuecomment-370489809
Good write-up @janl
`max_http_request_size` is a quick and dirty way of specifying limits but
not very accurate and has loopholes in it
nickva commented on issue #1200: [DISCUSS] CouchDB Request Size Limits
URL: https://github.com/apache/couchdb/pull/1200#issuecomment-370489809
Good write-up @janl
`max_http_request_size` is a quick and dirty way of specifying limits but
not very accurate and has loopholes in it
Dear Customer,
We offer a loan on 2.5 APR, same day approval- For more information email us at
- moredeta...@163.com
We would like to finance your Project, Business loans, Personal loan,
Investment loan and Consolidation loan are all types of loan application we
have available for now.
We
davisp commented on issue #1186: [WIP] Clustered purge mixed cluster upgrade
URL: https://github.com/apache/couchdb/pull/1186#issuecomment-370492585
I've not got anything good no. Other than I'm starting to really really
wanting to avoid the possibility of downgrading. The one thing that
Boo, we failed. https://builds.apache.org/job/CouchDB/job/master/201/
nickva commented on issue #1200: [DISCUSS] CouchDB Request Size Limits
URL: https://github.com/apache/couchdb/pull/1200#issuecomment-370489809
Good write-up @janl
`max_http_request_size` is a quick and dirty way of specifying limits but
not very accurate and has a loopholes in it
wohali commented on issue #71: Change default user in the Docker image from
root to couchdb
URL: https://github.com/apache/couchdb-docker/issues/71#issuecomment-370472838
I don't see how this can work, since [these
mangelov95 commented on issue #71: Change default user in the Docker image from
root to couchdb
URL: https://github.com/apache/couchdb-docker/issues/71#issuecomment-370471032
I actually just managed to do this by adding a `USER couchdb` tag after the
`ENTRYPOINT` in the Dockerfile and
mangelov95 commented on issue #71: Change default user in the Docker image from
root to couchdb
URL: https://github.com/apache/couchdb-docker/issues/71#issuecomment-370471032
I actually just managed to do this by adding a `USER couchdb` tag after the
`ENTRYPOINT` in the Dockerfile and
wohali commented on issue #1093: Hanging or 500 errors during concurrent
replication
URL: https://github.com/apache/couchdb/issues/1093#issuecomment-370470585
@ReeceStevens In testing together, it looks like the candidate fix for #745
has resolved this problem. I'm going to tentatively
wohali closed issue #1093: Hanging or 500 errors during concurrent replication
URL: https://github.com/apache/couchdb/issues/1093
This is an automated message from the Apache Git Service.
To respond to the message, please
Boo, we failed. https://builds.apache.org/job/CouchDB/job/master/200/
wohali closed issue #71: Change default user in the Docker image from root to
couchdb
URL: https://github.com/apache/couchdb-docker/issues/71
This is an automated message from the Apache Git Service.
To respond to the
wohali commented on issue #71: Change default user in the Docker image from
root to couchdb
URL: https://github.com/apache/couchdb-docker/issues/71#issuecomment-370466689
I don't see how this is possible. Without root access inside of the
container, we can't fix ownership of files in
Nanonid commented on issue #1171: couchdb unable to run on FIPS enabled CentOS
URL: https://github.com/apache/couchdb/issues/1171#issuecomment-370455069
So we have a erlang:MD5 polyfill. Aren't there already such fills?
I'd rather not have a secure couchdb fork, with IA patches, but it
Nanonid commented on issue #1171: couchdb unable to run on FIPS enabled CentOS
URL: https://github.com/apache/couchdb/issues/1171#issuecomment-370455069
So we have a erlang:MD5 polyfill. Aren't there already such fills?
This
janl closed pull request #1172: re-enable "flaky" test in quest to nail down
#745
URL: https://github.com/apache/couchdb/pull/1172
This is an automated message from the Apache Git Service.
To respond to the message, please
janl opened a new pull request #1203: Compaction Daemon & db-per-user
URL: https://github.com/apache/couchdb/pull/1203
This PR addresses a number of issues with the Compaction Daemon when run
under a db-per-user scenario:
1. with many database and/or many view groups in one or more
Yay, we passed. https://builds.apache.org/job/CouchDB/job/master/199/
[
https://issues.apache.org/jira/browse/COUCHDB-3287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16386064#comment-16386064
]
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=16386065#comment-16386065
]
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=16386067#comment-16386067
]
ASF subversion and git services commented on COUCHDB-3287:
--
Commit
[
https://issues.apache.org/jira/browse/COUCHDB-3255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16386068#comment-16386068
]
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=16386066#comment-16386066
]
ASF subversion and git services commented on COUCHDB-3287:
--
Commit
janl closed pull request #1189: Remove unused code for starting compactions
URL: https://github.com/apache/couchdb/pull/1189
This is an automated message from the Apache Git Service.
To respond to the message, please log on
mangelov95 opened a new issue #71: Change default user in the Docker image from
root to couchdb
URL: https://github.com/apache/couchdb-docker/issues/71
I would like to change the defualt running user in the couchdb image from
`root` to `couchdb`. What that means is basically when I do
janl commented on issue #1200: [DISCUSS] CouchDB Request Size Limits
URL: https://github.com/apache/couchdb/pull/1200#issuecomment-370381759
Summing up, here are the things we need to decide:
1. What is the desired behaviour for CouchDB?
1. Replication can fail if
janl commented on issue #745: Replication with attachments never completes,
{mp_parser_died,noproc} error
URL: https://github.com/apache/couchdb/issues/745#issuecomment-370375722
I suggest we close this in favour of #1200.
tl;dr: CouchDB master works as expected, but has an
janl closed issue #745: Replication with attachments never completes,
{mp_parser_died,noproc} error
URL: https://github.com/apache/couchdb/issues/745
This is an automated message from the Apache Git Service.
To respond to
jiangphcn commented on issue #1186: [WIP] Clustered purge mixed cluster upgrade
URL: https://github.com/apache/couchdb/pull/1186#issuecomment-370373499
Still trying to think about downgrade and upgrade from pre-CP to Clustered
Purge.
There is another situation where database are
garrensmith closed pull request #1046: Add support for stable and update
parameter for views
URL: https://github.com/apache/couchdb-fauxton/pull/1046
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of
garrensmith commented on issue #1056: Add async/await polyfill
URL: https://github.com/apache/couchdb-fauxton/pull/1056#issuecomment-370340521
+1 thanks.
This is an automated message from the Apache Git Service.
To respond to
style95 opened a new issue #1202: [questions] Recommended way to delete huge
number of documents.
URL: https://github.com/apache/couchdb/issues/1202
What is the most desirable way to delete a huge number of documents?
For example, let's say I want to delete 500K ~ 1000K documents.
58 matches
Mail list logo