[VOTE] Release Apache CouchDB 2.1.1-RC1

/Testing+a+Source+Release Please remember that "rc.1" is an annotation. If the vote passes, these artefacts will be released as Apache CouchDB 2.1.1. Please cast your votes now. Thanks, Joan Touzet

Re: Nightly build & push of Docker image(s) to bintray?

Be very careful here. Making such binaries available outside of your immediate developer community is a violation of Apache policy: http://www.apache.org/dev/release-distribution.html#unreleased The middle two bullet points are the issue here. CouchDB decided to build packages and binaries

[jira] [Closed] (COUCHDB-3393) Function lookup() - script can ask for documents!

[ https://issues.apache.org/jira/browse/COUCHDB-3393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joan Touzet closed COUCHDB-3393. Resolution: Won't Fix > Function lookup() - script can ask for docume

Last call: 2.1.1 imminent

Hi everyone, Given these recent changes: * React now compatibly-licensed * Erlang 20 support * Multiple important bugfixes * Debian 9 build support I'd like to roll 2.1.1 as a release very shortly. I propose to cherry-pick everything that's hit master since we forked 2.1.x off from master.

[jira] [Commented] (COUCHDB-2995) Can't build CouchDB on Smartos

[ https://issues.apache.org/jira/browse/COUCHDB-2995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16201495#comment-16201495 ] Joan Touzet commented on COUCHDB-2995: -- Hi Andreas, Yes, it is. You shouldn't be using port 5986

[jira] [Commented] (COUCHDB-2995) Can't build CouchDB on Smartos

[ https://issues.apache.org/jira/browse/COUCHDB-2995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16200854#comment-16200854 ] Joan Touzet commented on COUCHDB-2995: -- OK, looks like couchjs is OK. Here is the relevant part

[jira] [Commented] (COUCHDB-2995) Can't build CouchDB on Smartos

[ https://issues.apache.org/jira/browse/COUCHDB-2995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16200512#comment-16200512 ] Joan Touzet commented on COUCHDB-2995: -- "Verify CouchDB Installation" shouldn't f

Re: Trying to understand why a node gets 'frozen'

Yes, please add your observations to #745 directly. -Joan - Original Message - From: "Carlos Alonso" <carlos.alo...@cabify.com> To: user@couchdb.apache.org, "Joan Touzet" <woh...@apache.org> Sent: Wednesday, 11 October, 2017 10:11:52 AM Subject: Re: Tryi

Re: Trying to understand why a node gets 'frozen'

://i.imgur.com/Vb3Jisa.png -Joan - Original Message - From: "Carlos Alonso" <carlos.alo...@cabify.com> To: user@couchdb.apache.org, "Joan Touzet" <woh...@apache.org> Sent: Tuesday, 10 October, 2017 3:37:20 AM Subject: Re: Trying to understand why a node gets 'frozen'

[jira] [Closed] (COUCHDB-2484) replication crashes

[ https://issues.apache.org/jira/browse/COUCHDB-2484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joan Touzet closed COUCHDB-2484. Resolution: Auto Closed > replication crashes > --- > >

Re: 2.1 config files

This is all documented here: http://docs.couchdb.org/en/2.1.0/config/intro.html What you're experiencing is expected, given the override that you are using. CouchDB abandoned the "install into FHS" Linux approach with the 2.x series when we started embedding the version of Erlang that we use

Re: Trying to understand why a node gets 'frozen'

Is there more to the error? All this shows us is that the replicator itself attempted a POST and had the connection closed on it. (Remember that the replicator is basically just a custom client that sits alongside CouchDB on the same machine.) There should be more to the error log that shows why

Re: INFRA-15156: problems to send mails from Jenkins

CouchDB is still getting mails, so it's not a server-wide outage. -Joan - Original Message - From: "P. Ottlinger" To: builds@apache.org Sent: Monday, 2 October, 2017 7:00:53 PM Subject: Re: INFRA-15156: problems to send mails from Jenkins Hi, ping help - can

[jira] [Closed] (COUCHDB-3221) Shard maps for reserved database names cannot be updated

[ https://issues.apache.org/jira/browse/COUCHDB-3221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joan Touzet closed COUCHDB-3221. Resolution: Auto Closed Migrated to https://github.com/apache/couchdb/issues/858 > Shard m

[jira] [Closed] (COUCHDB-3414) Support Erlang 20.0

[ https://issues.apache.org/jira/browse/COUCHDB-3414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joan Touzet closed COUCHDB-3414. Resolution: Auto Closed Moved to https://github.com/apache/couchdb/issues/617 > Support Erl

CouchDB 2.x metrics & alerting solution is live!

Upstream netdata has merged my monitoring code. You can now install netdata live on any machine direct from the main netdata repo! Latest screenshots: https://github.com/firehol/netdata/pull/2818#issuecomment-333278334 Installation instructions are here:

CouchDB 2.x metrics & alerting solution is live!

Upstream netdata has merged my monitoring code. You can now install netdata live on any machine direct from the main netdata repo! Latest screenshots: https://github.com/firehol/netdata/pull/2818#issuecomment-333278334 Installation instructions are here:

CouchDB 2.x metrics & alerting solution is live!

Upstream netdata has merged my monitoring code. You can now install netdata live on any machine direct from the main netdata repo! Latest screenshots: https://github.com/firehol/netdata/pull/2818#issuecomment-333278334 Installation instructions are here:

Re: [Beta] New CouchDB 2.x metrics & monitoring solution

- Original Message - From: "Joan Touzet" <woh...@apache.org> To: "CouchDB Users" <user@couchdb.apache.org>, "CouchDB Developers" <d...@couchdb.apache.org> Sent: Tuesday, 26 September, 2017 3:45:13 PM Subject: [Beta] New CouchDB 2.x metr

Re: [Beta] New CouchDB 2.x metrics & monitoring solution

- Original Message - From: "Joan Touzet" <woh...@apache.org> To: "CouchDB Users" <u...@couchdb.apache.org>, "CouchDB Developers" <dev@couchdb.apache.org> Sent: Tuesday, 26 September, 2017 3:45:13 PM Subject: [Beta] New CouchDB 2.x metr

Re: Fauxton Plugin

Hi Bill, This is a CouchDB mailing list. You'll want to ask the PouchDB people about this one - the bug is related to Chrome and extensions, and nothing to do with Fauxton itself having problems. Best of luck, Joan - Original Message - From: "Bill Stephenson" To:

Re: Running CouchDB 2.1.0 on macOS High Sierra

Hi Oleg, This is an Erlang bug: https://bugs.erlang.org/browse/ERL-439 This commit fixed the problem: https://github.com/erlang/otp/commit/882c90f72ba4e298aa5a7796661c28053c540a96 If you can build Erlang from source, try applying this change and you should be good to go. CouchDB

[Beta] New CouchDB 2.x metrics & monitoring solution

Hi everyone, Looking for a monitoring solution for your CouchDB 2.x nodes? Here's a new offering that will make your day. First, some pretty graphs: https://imgur.com/a/4Gz7q This is built on netdata, an open source per-node data collection, monitoring and alerting solution. I like it because

[Beta] New CouchDB 2.x metrics & monitoring solution

Hi everyone, Looking for a monitoring solution for your CouchDB 2.x nodes? Here's a new offering that will make your day. First, some pretty graphs: https://imgur.com/a/4Gz7q This is built on netdata, an open source per-node data collection, monitoring and alerting solution. I like it because

Re: Error accessing the view in couchdb 1.6.1

Your 'couchjs' process isn't running correctly, so the views aren't being built. To confirm you can try running 'couchjs' from the command line and see what error you are getting. At a guess, you don't have the right version of SpiderMonkey installed, which should be v1.8.5. If this is Linux,

CouchDB + React, part 2 (hooray!)

So the good news is that Facebook have decided to relicense React to the MIT license as of v16. This gets us out of having to completely replace React in our code base. Our other two main dependencies that were un-usefully licensed were Flux and react-addons-transitions and velocity, which we've

Re: Docker images migrated to apache/couchdb

for whomever wants to do so: https://github.com/apache/couchdb-docker/blob/master/dev/Dockerfile You can add `-n 1` to the `dev/run` command to ensure only a single node is started up. -Joan - Original Message - From: "Joan Touzet" <woh...@apache.org> To: "Dale Harvey"

Re: Docker images migrated to apache/couchdb

for whomever wants to do so: https://github.com/apache/couchdb-docker/blob/master/dev/Dockerfile You can add `-n 1` to the `dev/run` command to ensure only a single node is started up. -Joan - Original Message - From: "Joan Touzet" <woh...@apache.org> To: "Dale Harvey"

Re: Docker images migrated to apache/couchdb

unique git hash reference can be supported, building from master should be done in a non-official image." -Joan - Original Message - From: "Dale Harvey" <d...@arandomurl.com> To: user@couchdb.apache.org, "Joan Touzet" <woh...@apache.org> Cc: "CouchDB

Re: Docker images migrated to apache/couchdb

unique git hash reference can be supported, building from master should be done in a non-official image." -Joan - Original Message - From: "Dale Harvey" <d...@arandomurl.com> To: u...@couchdb.apache.org, "Joan Touzet" <woh...@apache.org> Cc: "CouchDB

Docker images migrated to apache/couchdb

Hello everyone, The Docker images that used to live at klaemo/couchdb have now been semi-officially replaced by ones at apache/couchdb. Tags are present for 1.6.1, 1.6.1-couchperuser, 2.1.0, and latest (which is the same as 2.1.0). The 2.1.0 image can be used both as a single node, and in a

Docker images migrated to apache/couchdb

Hello everyone, The Docker images that used to live at klaemo/couchdb have now been semi-officially replaced by ones at apache/couchdb. Tags are present for 1.6.1, 1.6.1-couchperuser, 2.1.0, and latest (which is the same as 2.1.0). The 2.1.0 image can be used both as a single node, and in a

Re: (MXNet) Testing changes to the Jenkinsfile without merging to the repo.

Multibranch pipeline builds always use the Jenkinsfile in a specific branch when testing that branch. So, your changes to the Jenkinsfile pre-merge will only affect builds on that branch. Hopefully this is enough? You can always create a new multibranch pipeline build that has a filter on which

Re: [JENKINS] - Plugins update

Yup, that's the one. I see the job is back now. Phew! Going to give it a run and see if it's successful. -Joan - Original Message - From: "Gavin McDonald" <ga...@16degrees.com.au> To: builds@apache.org Cc: "Joan Touzet" <woh...@apache.org> Sent: Saturda

Re: [JENKINS] - Plugins update

Oof, I see that ours (a multibranch pipeline job) is missing. Any clue whether the job will be restored once the plugins are restored as well? -Joan - Original Message - From: "Gavin McDonald" To: builds@apache.org Sent: Saturday, 16 September, 2017 6:36:21 PM

[jira] [Commented] (COUCHDB-3319) Unable to modify cors/methods to enable HTTP OPTIONS requests

[ https://issues.apache.org/jira/browse/COUCHDB-3319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16169048#comment-16169048 ] Joan Touzet commented on COUCHDB-3319: -- There is special handling for OPTIONS - CouchDB should

Re: Custom Collation

The official answer is that CouchDB only supports UTF-8 collation order. The unofficial answer is that one or more of the workarounds posted, wherein you emit something different that collates correctly, should get you what you need. For instance, you could assign numbers to each letter in the

Re: [PROPOSAL] Disallow all merges of PRs to master that cause tests to fail

This ticket is now fixed. You should not be able to merge to master or any #.#.# branch if the tests are not passing now, and your branch is not up to date with the latest changes from master. If anyone finds different, please let me know. -Joan - Original Message - From: "Joan T

Re: [PROPOSAL] Disallow all merges of PRs to master that cause tests to fail

I have requested INFRA take the steps as outlined in this ticket: https://issues.apache.org/jira/browse/INFRA-14991 -Joan - Original Message - From: "Nick North" <nort...@gmail.com> To: dev@couchdb.apache.org, "Joan Touzet" <woh...@apache.org> Sent: Fr

Re: Mango query with $eq operator returns no results, but $regex does

Have you checked your couch.log / couchdb.log file for any errors? It's possible the index needed to be rebuilt, and adding the new document forced that operation. - Original Message - From: "Matt Cosentino" To: user@couchdb.apache.org Sent: Thursday, 24 August,

Re: CouchDB 2.1.0 Docker image

Pull requests welcome at: https://github.com/apache/couchdb-docker Please review outstanding issues and PRs on that repo to see what work has been done to date and what problems currently exist. We also are ready to move to hosting at apache/couchdb in Docker Hub whenever we publish this

Re: [DISCUSSION] Moving CouchDB off of Facebook React

Jan Lehnardt wrote yesterday: >To take a bit of pressure out of this decision making process, I want >to bring up an option that unblocks us indefinitely for making new >releases at the expense of end-user experience. > It’s a little bit of work, but not as much as anything approaching a >

Re: [DISCUSSION] Moving CouchDB off of Facebook React

cision to the Fauxton team. > > * * * > > I’d be happy to help with a recruiting drive to get more folks helping to do > the port. > > Best > Jan > — > > > > > >> On 19. Aug 2017, at 02:40, Joan Touzet <woh...@apache.org> wrote: >> &g

[DISCUSSION] Moving CouchDB off of Facebook React

devolve this thread into discussion about Facebook's decision, or why the ASF has made the policy decision that they have; such discussions lead nowhere, and CouchDB is not in a position to influence either organisation to change their decisions. On behalf of the CouchDB PMC, Joan Touzet

[PROPOSAL] Disallow all merges of PRs to master that cause tests to fail

b-pkg, since CI doesn't (yet) make sense for it. -Joan - Original Message - From: "Nick North" <nort...@gmail.com> To: "Joan Touzet" <woh...@apache.org> Cc: dev@couchdb.apache.org Sent: Friday, 18 August, 2017 12:42:19 PM Subject: Re: [DISCUSSION] Disallow a

Re: [DISCUSSION] Disallow all merges of PRs to master that cause tests to fail

I didn't realize you could review your own PR. That gives us the "escape hatch" that we need. -Joan - Original Message - From: "Nick North" <nort...@gmail.com> To: dev@couchdb.apache.org, "Joan Touzet" <woh...@apache.org> Sent: Friday, 18 August

Re: [DISCUSSION] Disallow all merges of PRs to master that cause tests to fail

c in any > way. > > Good call, Joan! > -- > ,,,^..^,,, > > > On Wed, Aug 16, 2017 at 6:46 AM, Joan Touzet <woh...@apache.org> wrote: > > Hi committers, > > > > I'd like to propose a change to our policy on version control, namely > > that no ch

Re: [DISCUSSION] Moving to a stricter quarterly release cycle?

notes were greatly improved by inclusion of direct text by Nick on the replication scheduler change. I'd love to see similar land directly in docs/src/whatsnew/X.X.rts for the ddoc_cache change or any other feature work going forward. -Joan - Original Message - From: "Joan Touzet&

Re: [DISCUSSION] Moving to a stricter quarterly release cycle?

a...@gmail.com> To: dev@couchdb.apache.org, "Joan Touzet" <woh...@apache.org> Sent: Wednesday, 16 August, 2017 11:00:00 AM Subject: Re: [DISCUSSION] Moving to a stricter quarterly release cycle? I can see all of 3, 4, and 6 month release cycles. Before committing to this I'd like to se

[DISCUSSION] Moving to a stricter quarterly release cycle?

Hi everyone, I'd like to consider moving us to a regular every-3-months release cycle. Under this plan the next CouchDB release would be on or around 1 November 2017. The next few releases would be around 1 February 2018, 1 May 2018, and 1 Aug 2018 again. The recently achieved "clean test suite"

[DISCUSSION] Disallow all merges of PRs to master that cause tests to fail

Hi committers, I'd like to propose a change to our policy on version control, namely that no check-ins be allowed on the master branch unless CI test runs against that PR are clean. We've worked hard as a group to get runs clean. We need to protect that achievement and investment in our test

Re: Workarounds for macOS 2.1.0 binary that won't start up

y" <j...@b2w.com> To: dev@couchdb.apache.org, "Joan Touzet" <woh...@apache.org> Sent: Friday, 11 August, 2017 1:43:26 AM Subject: Re: Workarounds for macOS 2.1.0 binary that won't start up Thanks again, I tried to install the new file on another mac and it lauched wi

Re: Workarounds for macOS 2.1.0 binary that won't start up

Thanks Jan! For some reason, the binaries didn't commit correctly to bintray, so I've had to re-upload them. All download links should work now. -Joan - Original Message - From: "Jan Lehnardt" <j...@apache.org> To: dev@couchdb.apache.org, "Joan Touzet"

Re: Workarounds for macOS 2.1.0 binary that won't start up

-assigned IP address and the bind address previously set is no longer valid?) -Joan - Original Message - From: "Johs Ensby" <j...@b2w.com> To: "dev@couchdb.apache.org Developers" <dev@couchdb.apache.org>, "Joan Touzet" <woh...@apache.org> Sent: T

Workarounds for macOS 2.1.0 binary that won't start up

All, We have reports from some users that they are unable to get the new macOS CouchDB 2.1.0 binary to start correctly. With the help of a user, we have two workarounds you can use to fix the problem. They are documented here:

Workarounds for macOS 2.1.0 binary that won't start up

All, We have reports from some users that they are unable to get the new macOS CouchDB 2.1.0 binary to start correctly. With the help of a user, we have two workarounds you can use to fix the problem. They are documented here:

[ANNOUNCE] Apache CouchDB 2.1.0 released

follow. A formatted version of them can be viewed at http://docs.couchdb.org/en/2.1.0/whatsnew/2.1.html On behalf of the CouchDB PMC, Joan Touzet --- Version 2.1.0 The Mango _find endpoint supports a new combination operator, $allMatch, which matches and returns all documents that contain

[ANNOUNCE] Apache CouchDB 2.1.0 released

follow. A formatted version of them can be viewed at http://docs.couchdb.org/en/2.1.0/whatsnew/2.1.html On behalf of the CouchDB PMC, Joan Touzet --- Version 2.1.0 The Mango _find endpoint supports a new combination operator, $allMatch, which matches and returns all documents that contain

[ANNOUNCE] Apache CouchDB 2.1.0 released

follow. A formatted version of them can be viewed at http://docs.couchdb.org/en/2.1.0/whatsnew/2.1.html On behalf of the CouchDB PMC, Joan Touzet --- Version 2.1.0 The Mango _find endpoint supports a new combination operator, $allMatch, which matches and returns all documents that contain

[ANNOUNCE] Apache CouchDB 2.1.0 released

follow. A formatted version of them can be viewed at http://docs.couchdb.org/en/2.1.0/whatsnew/2.1.html On behalf of the CouchDB PMC, Joan Touzet --- Version 2.1.0 The Mango _find endpoint supports a new combination operator, $allMatch, which matches and returns all documents that contain

Release process documentation updated

Hello committers, Our release process documentation was severely outdated, to the point where it lead to some difficulties in my correctly uploading the new release. This accounts for the delay in the release announcement until Monday. I have fully documented the release process as I followed it

[SCHEDULE] Apache CouchDB 2.1.0 release

Dear community, The Apache CouchDB 2.1.0 release is ready to go. I plan to make the announcement at: Monday 2017-08-07 16:00 UTC I will use these release notes: http://docs.couchdb.org/en/2.1.0/whatsnew/2.1.html Please make any necessary preparations. Thanks, Joan

[RESULT] (Was: [VOTE] Release Apache CouchDB 2.1.0-RC1)

Dear community, The vote has now closed. Thank you to everyone who participated! The results are: +1 - 4 votes +0 - 0 votes -0 - 0 votes -1 - 0 votes The vote passes. Thanks, Joan Touzet

Re: post 2.1 - gitlab or github

Hello "support-tiger", > As more of newer / outsider couch/pouch users, have to say that Gitlab > (which we really like) or Github seem to offer much more in terms of > descriptions of commits, issues, easier pull request management, ... > Idea is to make easier / incentives for

Re: 2.1 announcement blog post draft

Can't read it - it wants me to log in. I tried my personal WP login and it was still inaccessible. -Joan - Original Message - From: "Jan Lehnardt" To: "marketing" Sent: Wednesday, August 2, 2017 4:52:10 AM Subject: 2.1 announcement blog

Re: Understanding a couple replication errors

com> To: user@couchdb.apache.org, "Joan Touzet" <woh...@apache.org> Sent: Wednesday, August 2, 2017 8:40:39 AM Subject: Re: Understanding a couple replication errors Hi Joan, many thanks for your reply Why would the timeout and closed connections happen? I see it quite often on the logs TB

Re: [VOTE] Release Apache CouchDB 2.1.0-RC1

Hi Pink, Sounds like you have an outdated version of the sphinx_rtd_theme and possibly Sphinx. Try running `sudo pip install -U Sphinx sphinx-rtd-theme` and try running the docs build again. -Joan - Original Message - From: "Pink and Dangerous to Know Mad" To:

Re: [VOTE] Release Apache CouchDB 2.1.0-RC1

chdb folder >> under /var/lib >> >> g) not sure what files should be under /rel/couchdb to copy to >> /var/lib/couchdb - any suggestions here >> >> >> It seems like linux docs get less attention - this is backwards - couchdb is >> a server ba

Re: [VOTE] Release Apache CouchDB 2.1.0-RC1

trouble posting to the mailing list. Your mail headers may be causing your post to get caught for moderation. -Joan - Original Message - From: "support-tiger" <supp...@tigernassau.com> To: dev@couchdb.apache.org Cc: "Joan Touzet" <woh...@apache.org> Sent:

Re: [VOTE] Release Apache CouchDB 2.1.0-RC1

- Original Message - From: "Joan Touzet" <woh...@apache.org> To: "CouchDB Developers" <dev@couchdb.apache.org> Sent: Monday, 31 July, 2017 1:01:20 AM Subject: [VOTE] Release Apache CouchDB 2.1.0-RC1 Dear community, I would like to release Apache CouchDB 2.

Re: Understanding a couple replication errors

Hi Carlos, This issue (the {{nocatch,{mp_parser_died,noproc}}) is recently identified and patched! https://github.com/apache/couchdb/issues/574 The other error just looks like a disconnection. You may want to wait (just a couple more days!) for 2.1.0 which has all sorts of new replication

Re: [VOTE] Release Apache CouchDB 2.1.0-RC1

be removed. -Joan - Original Message ----- From: "Joan Touzet" <woh...@apache.org> To: "CouchDB Developers" <dev@couchdb.apache.org> Sent: Monday, 31 July, 2017 1:01:20 AM Subject: [VOTE] Release Apache CouchDB 2.1.0-RC1 Dear community, I would like to release Ap

[VOTE] Release Apache CouchDB 2.1.0-RC1

il 2017-08-03 @ 05:00. "Convenience binary" builds are being uploaded now; links will follow in a subsequent email. Please cast your votes now. Thanks, Joan Touzet

2.1.0 milestone progress report for 2017-07-28

Happy Friday everyone! TL;DR: Significant progress has been made towards 2.1.0. I anticipate a Release Candidate early next week. Here are the remaining issues blocking 2.1.0: https://github.com/apache/couchdb/milestone/2 Only 3 issues remain: * 1 minor feature ticket: * #593, improving

Re: Config files dir & LOCALCONFDIR

Hi Luis, Our documentation around configuration needs updating, thanks for the report. No need to change anything at build time - just at runtime. export ERL_FLAGS="-couch_ini /myinstance1/default.ini /myinstance1/local.ini" will work. You can also modify the etc/vm.args file to include these

2.1 Bug Review IRC meeting minutes

Hey everybody! Here's the logfile from today's bug meeting. In short: we are in very good shape for release candidates in the next week or so. Where possible, updates have been made to the tickets themselves, so consider this log more for posterity than anything else. Ticket count: 11 * 6 test

Re: Running a CouchDB 2.0 Cluster in Production on AWS with Docker

Hi Geoff, I describe one approach in the Chef CouchDB cookbook: https://github.com/wohali/couchdb-cookbook "One way is by downloading and extracting CouchDB's source code, changing into the dev/ directory, and running the following one-liner, replacing MYPASSWORD with your desired

IRC bug review meeting, Friday 2017-07-21, 11:00 ET / 1500 UTC

Hi everyone, To get us over the hump I'm hosting a short IRC bug review meeting this Friday, 2017-07-21, at 11AM ET / 1500 UTC. We will be on Freenode IRC in channel #couchdb-dev as usual. Please come if you can help fix these remaining bugs. If you can't attend, feel free to leave any relevant

Re: Can we fire a http request when any updation is performed in the bucket ?

CouchDB cannot call an external endpoint when changes occur, no. However, your application can subscribe to the changes feed and receive notification when a change occurs. Or, you can create a simple daemon to listen to the changes feed and call out to your HTTP application. Documentation on the

2.1.0 milestone progress report

Hi everyone, Here are the results of the progress towards the 2.1.0 milestone as captured in our issue tracking system (GitHub Issues). https://github.com/apache/couchdb/milestone/2 At present, we have just 10 of 55 tickets against the 2.1.0 milestone that remain open. Broken down: * 1

[PROPOSAL] Include replication scheduler in 2.1

Hi all, *Per the CouchDB bylaws, this is a concrete proposal that will default to lazy consensus in 72 hours (2017.07.19 ~21:00).* As we approach release candidates for v2.1 (see next email), we have one major decision left to make: whether or not to include the scheduling replicator in 2.1.

Re: How to run CouchDB 2.x on macOS

The official 2.0.0 installer for Mac is here: https://apache.bintray.com/couchdb/mac/2.0.0/Apache-CouchDB-2.0.0.zip We need to get brew updated - brew is still at 1.6.1. -Joan - Original Message - From: "Geoffrey Cox" To: user@couchdb.apache.org Sent:

CouchDB Windows maintenance release (v2.0.0.2)

, and OpenSSL to 1.0.2l. There are no other bugfixes or changes to CouchDB in this release. You may download the installer at: https://dl.bintray.com/apache/couchdb/win/2.0.0.2/couchdb-2.0.0.2.msi or from the Apache CouchDB homepage at https://couchdb.apache.org/ Best regards, Joan Touzet

CouchDB Windows maintenance release (v2.0.0.2)

, and OpenSSL to 1.0.2l. There are no other bugfixes or changes to CouchDB in this release. You may download the installer at: https://dl.bintray.com/apache/couchdb/win/2.0.0.2/couchdb-2.0.0.2.msi or from the Apache CouchDB homepage at https://couchdb.apache.org/ Best regards, Joan Touzet

Re: Introducing code owners

Cookie licking is the term I prefer, too. It's very well defined here: http://communitymgt.wikia.com/wiki/Cookie_Licking -Joan - Original Message - From: "Rich Bowen" To: dev@community.apache.org Sent: Monday, 10 July, 2017 9:03:33 AM Subject: Re: Introducing code

[jira] [Commented] (COUCHDB-3432) make fails at jiffy

[ https://issues.apache.org/jira/browse/COUCHDB-3432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16079379#comment-16079379 ] Joan Touzet commented on COUCHDB-3432: -- Weird, that got corrupted. It shouild say: the output

[jira] [Commented] (COUCHDB-3432) make fails at jiffy

[ https://issues.apache.org/jira/browse/COUCHDB-3432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16079377#comment-16079377 ] Joan Touzet commented on COUCHDB-3432: -- On my CentOS 7 machine, the output of the command "wh

Re: [PROPOSAL] Getting 2.1 out the door (was: Test Suite Stabilization)

.1. B. > On 4 Jul 2017, at 05:11, Joan Touzet <jo...@atypical.net> wrote: > > Hi everyone, > > Thanks to the help of the committer team, we've made significant strides > towards closing out many of our test case failures over the past month. > (Sorry for the la

[jira] [Closed] (COUCHDB-3431) 400 error when posting valid JSON

[ https://issues.apache.org/jira/browse/COUCHDB-3431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joan Touzet closed COUCHDB-3431. Resolution: Fixed > 400 error when posting valid J

[jira] [Commented] (COUCHDB-3431) 400 error when posting valid JSON

[ https://issues.apache.org/jira/browse/COUCHDB-3431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16078936#comment-16078936 ] Joan Touzet commented on COUCHDB-3431: -- Reopening just to note that we even state

[jira] [Reopened] (COUCHDB-3431) 400 error when posting valid JSON

[ https://issues.apache.org/jira/browse/COUCHDB-3431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joan Touzet reopened COUCHDB-3431: -- > 400 error when posting valid JSON > - > >

[jira] [Closed] (COUCHDB-3431) 400 error when posting valid JSON

[ https://issues.apache.org/jira/browse/COUCHDB-3431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joan Touzet closed COUCHDB-3431. Resolution: Invalid CouchDB is a document-oriented database, not an array-oriented database

[jira] [Closed] (COUCHDB-3431) 400 error when posting valid JSON

[ https://issues.apache.org/jira/browse/COUCHDB-3431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joan Touzet closed COUCHDB-3431. Resolution: Fixed It's whatever you're doing for encoding that is wrong. It definitely works

[jira] [Closed] (COUCHDB-3432) make fails at jiffy

[ https://issues.apache.org/jira/browse/COUCHDB-3432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joan Touzet closed COUCHDB-3432. Resolution: Works for Me > make fails at jiffy > --- > >

[jira] [Commented] (COUCHDB-3432) make fails at jiffy

[ https://issues.apache.org/jira/browse/COUCHDB-3432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16078341#comment-16078341 ] Joan Touzet commented on COUCHDB-3432: -- You are missing a build dependency. Here is what we

Re: Build CouchDB on Windows

Hi John, Sorry for the delay in replying here. I've finally gotten around to re-creating my build environment from scratch (as I do prior to every CouchDB release) and have the build running successfully as of a few hours ago. - Original Message - > In this section I believe there is an

Re: _global_changes database best practices

And as a corollary to this, we are enabling the compaction daemon by default shortly. I expect this change to be enabled for the upcoming CouchDB 2.1 release. https://github.com/apache/couchdb/pull/624 -Joan - Original Message - From: "Robert Samuel Newson" To:

[jira] [Commented] (COUCHDB-3170) Permissions are ignored in "_users" database.

[ https://issues.apache.org/jira/browse/COUCHDB-3170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16075103#comment-16075103 ] Joan Touzet commented on COUCHDB-3170: -- Pretty sure that you have to be an actual server-level

[jira] [Resolved] (COUCHDB-3170) Permissions are ignored in "_users" database.

[ https://issues.apache.org/jira/browse/COUCHDB-3170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joan Touzet resolved COUCHDB-3170. -- Resolution: Not A Problem > Permissions are ignored in "_users&q

[jira] [Closed] (COUCHDB-3344) EUnit: compaction_daemon_tests timing out

[ https://issues.apache.org/jira/browse/COUCHDB-3344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joan Touzet closed COUCHDB-3344. Resolution: Incomplete Migrated to https://github.com/apache/couchdb/issues/638 > EU

<    3   4   5   6   7   8   9   10   11   12   >