Congratulations, Garren! Glad to have you with us.
-Joan
- Original Message -
> From: "Andy Wenk"
> To: dev@couchdb.apache.org
> Sent: Monday, October 19, 2015 9:41:35 AM
> Subject: Re: [ANNOUNCE] Garren Smith joins the PMC
>
> Hey Garren,
>
> finally! welcome on board ;-)
>
> All the
What a climb, Michelle! Super stoked to have you in the PMC.
-Joan
- Original Message -
> From: "Andy Wenk"
> To: dev@couchdb.apache.org
> Sent: Monday, October 19, 2015 9:42:15 AM
> Subject: Re: [ANNOUNCE] Michelle Phung joins the PMC
>
> Hey Michell - cool to have you on board ;-) Let
Hi Robert,
I'm presently migrating our one Makefile left in couchdb to a Windows
NMakefile, which uses a different syntax.
git shell works but has enough problems that I don't want to rely on
it. Sometimes it's almost as much work to debug a GNU Makefile running
under cygwin as it is to rewrite t
- Original Message -
> From: "Harald Kisch"
> To: dev@couchdb.apache.org
> Sent: Tuesday, October 20, 2015 11:45:18 AM
> Subject: Re: [PROPOSAL] Allow rewrites to be JS function
>
> Extendability and Upgradability with npm - what could be more
> extendable
> and more flexible?
Then run n
> -2. still doesn’t solve that `function() {}` is not valid JavaScript
> and doesn’t work in newer SpiderMonkeys or other engines. But that
> might be out of scope.
IMO if you're going to tweak anything in the query definitions, you HAVE
to fix this - it's a bridge to us using any other engine and
Hi Robert,
I've been thinking about this one for the week or so, and I have a
simple suggestion:
Add the query parameter slow=true to enable this behaviour.
This meets all the original requirements:
1. It is not default behaviour
2. You can grep the log files for the word 'slow' and find evi
nly in
> >>>> production" is a good thing to move towards.
> >>>>
> >>>> Perhaps something like adding a key to the returned data along the
> >>>> lines of "_slow_warning": "This query is going to be slow on la
I agree we should avoid re-introducing autoconf to the build process.
Hopefully we can fix this with a simple set of #ifdefs in a header file
somewhere that defines ssize_t (or anything else we need) appropriately,
or dig into the MS SDK for any references available and include compat
header files
I've not been following this message trail carefully, but I have a question.
Does the docker image run 3 instances within the same image, or is it a
single node version? The reason I ask is that, in deployment, which is
where I would expect docker to shine, you'd **NEVER** want to run 3
nodes on t
Jumping on the bandwagon a bit late butHappy Happy!
-Joan
- Original Message -
> From: "Garren Smith"
> To: dev@couchdb.apache.org
> Cc: andyw...@apache.org, "Garren Smith"
> Sent: Friday, February 12, 2016 12:27:05 PM
> Subject: Re: Happy Birthday Garren!!
>
> Thanks everyone for
Hey Mike,
As mentioned on IRC I'd like to see some test cases in our suite
to help ensure we don't regress on this in the future. Specifically,
I think it'd be good to ensure consistent revs on a handful of
indicative docs.
There's nothing saying we can't change how we do this in the future,
but
Agreed, good enough for now.
- Original Message -
> From: "Jan Lehnardt"
> To: "dev@couchdb.apache.org Developers"
> Sent: Wednesday, March 30, 2016 3:57:01 PM
> Subject: make
>
> Hey all,
>
> last year I endeavoured to make the 2.0 build system to behave as
> close to 1.x as possible
Garren, correct me if I'm wrong but Fauxton depends on a large number
of JS dependencies that we don't keep copies of, correct? Or is it just
for the build process?
-Joan
- Original Message -
> From: "Alexander Shorin"
> To: dev@couchdb.apache.org
> Sent: Wednesday, April 13, 2016 2:08:2
Based on this information, are we in violation of ASF requirements? Can
anyone clarify for me what we actually need to be doing here?
-Joan
- Original Message -
> From: "Garren Smith"
> To: dev@couchdb.apache.org, "Joan Touzet"
> Sent: Thursday, April 14,
Congrats!
- Original Message -
> From: "Jan Lehnardt"
> To: "dev@couchdb.apache.org Developers"
> Sent: Friday, April 15, 2016 4:50:10 AM
> Subject: Adam Kocoloski is now an IBM Fellow
>
> Hey all,
>
> our own Adam made IBM Fellow! He’s now one of only 267* individuals
> who’ve been aw
Windows port. If the test suite is finally stable we'll do another
pass of getting this to work - sans the Win 10 bash stuff since a)
that's still in private release and b) Win 10 stinks.
-Joan
- Original Message -
> From: "Jan Lehnardt"
> To: dev@couchdb.apache.org
> Sent: Friday, April
Congrats, Nolan!
- Original Message -
> From: "Robert Kowalski"
> To: dev@couchdb.apache.org
> Sent: Tuesday, April 19, 2016 12:04:22 PM
> Subject: Re: [ANNOUNCE] Nolan Lawson elected as CouchDB committer
>
> Whohoo, congrats Nolan! :)
>
> On Tue, Apr 19, 2016 at 5:21 PM, Darío Cravero
Also +1, except for the work to get the Windows port running correctly.
-Joan
- Original Message -
> From: "Michelle Phung"
> To: dev@couchdb.apache.org
> Sent: Thursday, May 26, 2016 7:23:46 AM
> Subject: Re: 2.0 Code Freeze or branching 2.1?
>
> +1
>
> - Michelle
>
> > On May 26, 20
As I said on IRC...congratulations! Long overdue.
-Joan
- Original Message -
> From: "Benjamin Bastian"
> To: dev@couchdb.apache.org
> Sent: Thursday, June 16, 2016 8:42:19 PM
> Subject: Re: [ANNOUNCE] Nick Vatamaniuc elected as CouchDB committer
>
> Congratulations, Nick!
>
> On Thu,
Hi Ben, did anyone ever get back to you on this? I know that the
core developers have a LOT of reservations about the _replicator database,
primarily the fact that the backing store for a _replicator endpoint
probably shouldn't be a database itself (though it could conceivably present
a similar API
Hello everyone,
I'd like to update the community on the status of the 2.0 port to Microsoft
Windows. There are three parts to this email: the build tools/chain themselves,
support in CouchDB for the Windows build process, and testing results. I'll
cover them in that order.
-Joan
Build Tools/C
A small update on the testing front. I've tried replicating the animaldb from
Cloudant to my local server, and things looked very ugly:
https://gist.github.com/anonymous/f2a94234195f007c3049e27d942482c1
I've yet to dig into this failure; I'm posting it here in case anyone has the
time to analyze
No objection from me, if it makes things easier for you - as long as you
are aware that you may get requests from customers saying "Hey, I see
you used my bug tracker ticket id # in a CouchDB commit..." ;)
-Joan
- Original Message -
From: "Ilya Khlopotov"
To: dev@couchdb.apache.org
Sent:
Replying to my own email: dev/run is using the wrong path slashes for
the path to the javascript/coffeescript view servers. I've submitted a PR
and will merge if no one complains.
Here is the latest set of test results if anyone still wants to volunteer
to help me review them (both Eunit and JS, s
ot;Nick North"
> To: dev@couchdb.apache.org, "Joan Touzet"
> Sent: Saturday, June 18, 2016 3:37:50 AM
> Subject: Re: 2.0 & Windows: status update
>
> Hi Joan. This sounds like an improvement on my last Windows build
> attempt,
> which still had a couple of
*facepalm* :) Nothing private, just...didn't want to clutter the list.
Sorry!
- Original Message -
> From: "Joan Touzet"
> To: dev@couchdb.apache.org
> Sent: Saturday, June 18, 2016 3:56:50 AM
> Subject: Re: 2.0 & Windows: status update
>
> Replying off list.
[SNIP]
- Original Message -
> Couch 1.x and Couch 2.x will choke as soon as the indexer tries to
> process a too large document that was added. The indexing stops and
> you have to manually remove the doc. In the best case you built an
> automatic process around the process. The automatic process
hat last message. And I meant
>> > to
>> > > sign my name correctly.
>> > >
>> > > Nick
>> > >
>> > > On Sun, 19 Jun 2016 at 16:56 Nick North wrote:
>> > >
>> > > > I'm trying these tests now, and find that there are still a lo
ok at this one? (Paul?)
-Joan
- Original Message -----
From: "Joan Touzet"
To: dev@couchdb.apache.org
Sent: Tuesday, July 12, 2016 6:02:12 PM
Subject: Re: 2.0 & Windows: status update
Thanks, Paul. I'm starting to look at this today.
In better news, current Windows JS tes
Trimming the long thread for readability...
Good news, everyone! As of the latest checkin to master, CouchDB 2.0
builds correctly on Windows 64-bit! All eunit and javascript tests
pass (or are skipped intentionally).
This is a huge milestone! I especially want to thank Nick North and
Dave Cottle
lease be sure you have the latest tarball to look at,
or if you know how to use git, cloned from our apache/couchdb repository
(master branch). We've recently fixed a couple of failing tests and you
may be seeing issues we've already resolved.
Best,
Joan Touzet
b_2.0/README.md
This repository will be moved into ASF infrastructure shortly.
Enjoy,
Joan Touzet
Hi Jenn,
I'll write about Release Candidates, as long as I can get a sentence
or two in about the Windows port I just completed. :) I won't be
available to write the post until August, though.
Thanks,
Joan
- Original Message -
> From: "Jenn Turner"
> To: market...@couchdb.apache.org
> C
; Week 1
> Jul 25: The Road to CouchDB 2.0, Jan Lehnardt
> Jul 27: Feature: Fauxton, Garren Smith
>
> Week 2
> Aug 1: The CouchDB 2.0 Architecture, Robert Newson
> Aug 3: Feature: Mango query, Tony Sun
>
> Week 3
> Aug 8: Release Candidates, Joan Touzet
> Aug 10: Featur
Presently, CouchDB 2.0 logs only to stderr. I have opened a PR
to switch this behaviour to log to the ./var/log/couchdb.log
release-local file by default:
https://github.com/apache/couchdb/pull/435
This behaviour is easily overridden in the default.ini/local.ini
files if desired.
I'm not sure
:
>>
>> Seems reasonable to me. I wonder if we should add a stdout log line that
>> indicates where logs are going? Would be easy to add that as a module
>> callback so it would work for stderr, file, and syslog.
>>
>>> On Aug 2, 2016, at 2:36 PM, Joan Touz
to add that as a module
> callback so it would work for stderr, file, and syslog.
>
>> On Aug 2, 2016, at 2:36 PM, Joan Touzet wrote:
>>
>> Presently, CouchDB 2.0 logs only to stderr. I have opened a PR
>> to switch this behaviour to log to the ./var/log/couchdb.
. Until then,
if you want the latest installer, you can build it yourself :)
All the best,
Joan
- Original Message -
From: "Joan Touzet"
To: dev@couchdb.apache.org
Sent: Friday, July 15, 2016 6:58:39 PM
Subject: Re: 2.0 & Windows: status update (all tests passing)
Trimming t
Windows build is ready!
https://atypical.net/mm/couchdb-2.0.0-rc3.msi
Also have one failing test in couch_log_writer_file_test, have reported it
as COUCHDB-3092.
-Joan
- Original Message -
From: "Jan Lehnardt"
To: dev@couchdb.apache.org
Sent: Thursday, August 4, 2016 9:56:14 AM
Subjec
runcate.
> > It
> > checks every 30s or so to see if the inode for its path changed and
> > re-opens and starts writing to a new file if it has.
> >
> > On Tue, Aug 2, 2016 at 3:37 PM, Joan Touzet
> > wrote:
> > > Yeah, I understand these reservations. I a
Looks like from the code your POST body should contain a
'queries' list or a 'keys' key-value pair. Here's an example
of the latter that should now work under CouchDB 2.0 (see the
answer, not the question):
http://stackoverflow.com/questions/27327140/how-to-combine-multiple-couchdb-queries-into-a-
Replying to my own email with more detail.
The format of the 'queries' POST doc should look like:
{
"queries" : [
{ "startkey": "a", "endkey": "c"},
{ "startkey": "q", "endkey": "s"
; The format of the 'queries' POST doc should look like:
> >
> > {
> > "queries" : [
> > { "startkey": "a", "endkey": "c"},
> > { "startkey": "q", "endkey": "s"
Testing a CouchDB 2.0 feature
> > > >
> > > > Replying to my own email with more detail.
> > > >
> > > > The format of the 'queries' POST doc should look like:
> > > >
> > > > {
> > > > "queries&
Hi Nolan, you state that it's 'failing for known reasons.' Is that
reasons in PouchDB or anything you need to push back on us? We'd like
to know ASAP as we're very, very close to releasing 2.0 now.
I have zero PouchDB knowledge so I'm hoping you can give us a short
summary of what you think is wr
today?
-Joan
- Original Message -
> From: "Will Holley"
> To: dev@couchdb.apache.org, "Joan Touzet"
> Sent: Friday, September 2, 2016 4:43:48 AM
> Subject: Re: Getting libraries to test RCs
>
> Assuming nothing's changed in the last few weeks, th
update the bug myself
shortly.
-Joan
- Original Message -
> From: "Joan Touzet"
> To: dev@couchdb.apache.org
> Sent: Friday, September 2, 2016 5:15:00 AM
> Subject: Re: Getting libraries to test RCs
>
> Hi Will,
>
> Neither of these are currently tagge
Jan said:
> we are tantalisingly close to shipping 2.0. There are a few docs
> items that I hope we can wrap up tomorrow, but I think we are ready
> to start a vote on a real release tarball any day now.
Personal priorities prevented me from working on these today. I hope
to have some time tomorro
Hi Joey,
Erlang itself has parameters you will want to adjust. Place these
lines in your etc\vm.args file:
-kernel inet_dist_listen_min
-kernel inet_dist_listen_max
Ports within this range will be used for communication across the
distributed Erlang cluster. If you set them both to the same nu
Hi Joey,
I'm going to oversimplify a bit here to make the explanation easier.
If you check the process manager/top on each node, do you see couchjs
responsible for that 100% CPU?
Remember that views are not replicated, only documents. So if you have
design documents that you replicated, those v
Hi dev@,
I keep getting these messages, even though I know we have a clean
build on Linux and Windows. Who's responsible for our Jenkins setup?
-Joan
- Forwarded Message -
From: "Apache Jenkins Server"
Sent: Friday, September 9, 2016 11:16:53 AM
Subject: CouchDB - Build # 163 - Still Fa
I don't know, a simple view with 100 documents should build quickly
unless your view code is unusual.
I would recommend replicating the database to a UNIX-based 2.0 cluster
to see if the problem is Windows-specific.
Sorry that I don't have any other ideas at the moment.
-Joan
- Original Mes
Hi there,
About 3 weeks ago eiri added new tests to the couchdb_os_proc_pool
suite. Unfortunately, I haven't run the test suite since then, so it is
only at this late date that I discover two of the tests are failing on
Windows, blocking my ability to declare the build clean.
You can view sample
rom: "Eli Stevens (Gmail)"
To: "CouchDB Developers" , "Joan Touzet"
Sent: Sunday, September 11, 2016 1:41:37 AM
Subject: Re: 2.0 blocker: new failing tests on Windows
FWVLIW, I'd rather keep the tests active, and have the release happen
with not all tests passi
All,
Sadly the build is broken on Windows. A change just yesterday to
how we populate the version number into the build wasn't tested,
and the approach is inoperative on Windows.
I am investigating the problem today and hope to have a fix in a
few hours.
Until then please keep testing the releas
.1/apache-couchdb-2.0.0.msi
https://dist.apache.org/repos/dist/dev/couchdb/binary/win/2.0.0/rc.1/apache-couchdb-2.0.0.msi.md5
Please note this build is based on Erlang 17.5.
-Joan
- Original Message -
From: "Joan Touzet"
To: dev@couchdb.apache.org
Sent: Monday, September 12, 20
ta," but it'll take more experience
and more repeatable bugs at the very least - and active CouchDB Windows
developers with performance tuning experience at best.
-Joan
- Original Message -----
> From: "Joey Samonte"
> To: dev@couchdb.apache.org, "Joan Touze
also recommend you use a minimum of 3 nodes for a cluster of q=8 (the
default).
- Original Message -
> From: "Joey Samonte"
> To: dev@couchdb.apache.org, "Joan Touzet"
> Sent: Wednesday, September 14, 2016 12:04:04 AM
> Subject: Re: High CPU usage ca
Hi Nick,
- Original Message -
>- Windows did not trust the installer, which might put cautious
>users
>off.
Interesting. The installer is signed by Symantec. You should be able to
verify this by opening the Properties dialog on the installer file itself.
Not sure what more we
r/src/couch_httpd_misc_handlers.erl#L33-L42
Presumably we've left out the UUID because it would change all
the time in a load-balanced cluster configuration.
I'll vote +1 as well.
-Joan
- Original Message -
> From: "Joan Touzet"
> To: dev@couchdb.apache.o
uster setup script does the
right thing w.r.t. UUIDs as well.
I annotated this as a concern in COUCHDB-3147.
-Joan
>
> B.
>
> > On 14 Sep 2016, at 22:53, Joan Touzet wrote:
> >
> > And of course my turn to vote:
> >
> > Windows 7 SP1. MD5 OK.
> >
Issue!default.jspa
selecting CouchDB as the project.
-Joan
- Original Message -
> From: "Joey Samonte"
> To: dev@couchdb.apache.org, "Joan Touzet"
> Sent: Wednesday, September 14, 2016 6:59:12 AM
> Subject: Re: High CPU usage caused by clustering
Hi Sebastian,
> minor thing (at most): install-Dir „C:\CouchDB20“ will be ignored –
> uses
> C:\CouchDB
This is fixed in master/2.0.x branches and just requires me to upload
a new build at this point.
-Joan
I'd like to see us move to Rebar 3 as well. Challenges will be compiling
the NIF stuff, especially in a cross-platform stable way.
GitHub notifications tells me davisp started in on a little thing:
https://github.com/davisp/erlang-native-compiler
Perhaps you can make use of this / talk to Paul a
Thanks for all the great feedback, everyone! I'm so happy to see
continued enthusiasm for our little project. :)
I don't have a lot of great ideas of things I'd like to see implemented
in CouchDB itself, but I wanted to turn the clock back to the last time
we went through this exercise: events fol
Welcome, Ben! Glad to have you officially in the team.
-Joan
- Original Message -
> From: "Robert Samuel Newson"
> To: dev@couchdb.apache.org
> Sent: Tuesday, November 1, 2016 3:46:36 PM
> Subject: [ANNOUNCE] Benjamin Anderson elected as CouchDB committer
>
> Dear community,
>
> I am p
What other possibilities are there?
We could set a max recursion depth, perhaps.
couchjs has a limit on max stack size; a recursion depth limit would be
similar in spirit.
If nothing else is possible I'm happy for this change as a last-ditch effort.
-Joan
- Original Message -
> From: "
The Windows build process is not 100% automatable right now, nor
has it ever been. There's a bunch more work necessary to make that
happen. Ideally, someone would offer to help me with this.
The actual *publish* of an approved final build should still be a
manually invoked process, especially beca
Looks like you need to install a C++ compiler, such as g++.
Try: sudo yum groupinstall "Development Tools"
- Original Message -
> From: "angelo piersanti"
> To: dev@couchdb.apache.org
> Sent: Monday, January 2, 2017 4:57:35 PM
> Subject: Make Release Issue for 2.0 on RHEL 7
>
> I am hit
Congrats! Welcome Michael.
- Original Message -
> From: "Robert Kowalski"
> To: dev@couchdb.apache.org
> Sent: Thursday, January 5, 2017 2:02:52 PM
> Subject: [ANNOUNCE] Michael Hall elected as CouchDB committer
>
> Dear community,
>
> I am pleased to announce that the CouchDB Project M
- Original Message -
> From: "Eli Stevens (Gmail)"
> To: "CouchDB Developers"
> Sent: Thursday, January 26, 2017 5:40:01 PM
> Subject: Re: Publisher account for CouchDB snap
>
> Are issues with and troubleshooting of the previously-provided
> CouchDB
> 2.0 snap files on topic for dev?
Just to clarify here:
- Original Message -
> > Are issues with and troubleshooting of the previously-provided
> > CouchDB
> > 2.0 snap files on topic for dev?
Yes, absolutely. If you can't get the snaps to run, or have a
problem where CouchDB compiled from scratch works but the snap
does
Hi Chris,
Replied on the ticket. Thanks again for your help here!
-Joan
- Original Message -
> From: "Chris Thistlethwaite"
> To: dev@couchdb.apache.org
> Sent: Monday, February 6, 2017 10:20:41 AM
> Subject: Re: couchdb-vm.apache.org
>
> Just wanted to bump this thread again. I'd like
Hi everyone,
I'd like to propose dropping the PDF and texinfo targets from our
documentation build, or at the very least, having them not be part of
the default target / not standard deliverables for the project.
We'd continue to build HTML documentation as part of the workflow,
naturally, as wel
ds
>
> +1. Please use fire.
>
> > On 18 Mar 2017, at 17:44, Robert Kowalski wrote:
> >
> > good idea, +1
> >
> >> On Sat, Mar 18, 2017 at 9:14 AM, Jan Lehnardt wrote:
> >>
> >> +1
> >>
> >> Cheers
> >> Jan
...for now. I'm trying to get us to the point where we don't
have PRs open on repos for more than a year unless absolutely
necessary. It's especially bad form when the PR is from
a non-committer, bordering on rude especially when there are
no comments from committers on the PR!
If you had an old P
Hello,
I've been getting our CI workflows cleaned up a bit, including
re-enabling our OS matrix builds on Apache's Jenkins. Today, I finally
got my first all-green build on Jenkins and Travis at the same time. It
was a LOT harder than it should have been.
Why? Because our test suite (and build pr
d if there are any solid numbers to compare
> downloads of different formats of the docs via [2].
>
> [1] https://media.readthedocs.org/pdf/couchdb/latest/couchdb.pdf
> [2] http://docs.couchdb.org/en/2.0.0/download.html
>
>
>
> Am Sat, 18 Mar 2017 00:55:43 -0400 (EDT)
> sch
hat it
> > > might be
> > an
> > > older npm or there is some connection issues with npm.
> > > We use node 6 with Travis and haven't seen this issue. Is it
> > > possible to
> > > cache npm installs locally, that will speed up your build time
Thanks for the info Jay!
Erlangers, I still need your help addressing the remaining eunit
failures.
-Joan
- Original Message -
> From: "Jay Doane"
> To: dev@couchdb.apache.org, "Joan Touzet"
> Sent: Monday, March 20, 2017 2:59:12 AM
> Subject: Re:
work_queue_tests.erl, line 182)
**error:{badmatch,timeout}
Never seen this one before.
- Original Message -
> From: "Joan Touzet"
> To: dev@couchdb.apache.org
> Sent: Wednesday, March 22, 2017 6:02:55 PM
> Subject: Re: Stabilizing our automated builds -
Replying to my original email with an update.
Reminder:
The goal here is to get CI builds useful for everyone. That means stable
builds with no test failures, so that when a status turns from passing
to failed, it actually means something. Your help to get us there is
*very much appreciated*. :D
Another update to my original email.
TL;DR: 3 more sporadic failures in the test suite have shown up, and the
build issue on CentOS 6 has been ironed out. Help still needed!
I decided to move to JIRA tickets for everything, but don't let this
fool you: these test cases need some tender loving car
Hi everyone,
It looks like the CouchDB build is broken, by Fauxton. It appears
the failure started fairly recently, though I can't pinpoint it as
having come from Michelle's latest checkin, though, because the
build at that time succeeded:
https://travis-ci.org/apache/couchdb/builds/215332021
Monday update: we have 2 new test failures, 1 test harness failure,
and 1 resolved issue (Thanks Jay Doane!)
# New Issues
COUCHDB-3345: JS: stats.js silent failure
The test simply shows 'fail' with no tracebacks or further info.
Silent failures are troubling.
COUCHDB-3346: JS: reduce.js "JSO
e shell
has a different locale set than the non-interactive shell inside
Docker, and the latter was trying to decode it to ASCII (and failing).
- Original Message -
> From: "Joan Touzet"
> To: dev@couchdb.apache.org
> Sent: Monday, March 27, 2017 4:26:46 PM
> Subjec
Hi Jan,
It's still failing, I'm afraid. While I can get through 'make dist' now,
the tarball result of that make dist is unbuildable. Here's the log:
https://paste.apache.org/DknB
-Joan
- Original Message -
> From: "Jan Lehnardt"
> To: dev@couchdb.apache.org
> Sent: Friday, March 31
Hi everyone,
Time for the weekend update, now that the monorepo merge has landed.
# TL;DR
1 new ticket filed for a recurring issue. No help has materialized
in helping get rid of currently failing tests :( Please help!
# New Issues
COUCHDB-3352: JS: couchjs SIGSEGVs
Seen this one before but d
All,
I wanted to express a concern with my CouchDB PMC hat on.
There is some great work being merged by Cloudant here. But I'm not
seeing the Review-Then-Commit pattern being followed in a significant
number of these PRs coming through to any of our repos.
Take as an example this one, which is o
Hi Jan, I didn't see an INFRA ticket on this so I've filed a new one:
https://issues.apache.org/jira/browse/INFRA-13754
-Joan
- Original Message -
> From: "Jan Lehnardt"
> To: dev@couchdb.apache.org
> Sent: Friday, March 17, 2017 9:53:37 AM
> Subject: Re: Commits to the wrong list?
>
>
Whoops, wrong link:
https://issues.apache.org/jira/browse/INFRA-13809
-Joan
- Original Message -
> From: "Joan Touzet"
> To: dev@couchdb.apache.org
> Sent: Monday, April 3, 2017 6:20:19 PM
> Subject: Re: Commits to the wrong list?
>
> Hi Jan, I didn'
Message -
> From: "Joan Touzet"
> To: dev@couchdb.apache.org
> Sent: Monday, April 3, 2017 6:21:04 PM
> Subject: Re: Commits to the wrong list?
>
> Whoops, wrong link:
>
> https://issues.apache.org/jira/browse/INFRA-13809
>
> -Joan
>
> -
> On 04/03/2017 05:17 PM, Joan Touzet wrote:
> > All,
> >
> > I wanted to express a concern with my CouchDB PMC hat on.
> >
> > There is some great work being merged by Cloudant here. But I'm not
> > seeing the Review-Then-Commit pattern being follo
Hi everyone,
Bit late on my updates to this, been a busy last 3 weeks.
# TL;DR
* 6 new failures: 2 JS, 4 EUnit.
* Recurrences of 4 previously reported bugs.
* Cloudant has offered to look at a few of the EUnit failures.
* Lack of help on these issues is now directly impacting our ability to
aut
Hello everyone,
Time for more great news - Debian & Ubuntu couchdb 2.0.0 packages are
ready for BETA testing. These packages support full auto-configuration
and upgrades from CouchDB 1.x.
*Developers*: Please see https://github.com/apache/couchdb-pkg/pull/4 for
the nitty gritty details.
*Users*:
Hi everyone,
Now that the initial Debian/Ubuntu packaging is done, my attention turns
to our test suite full time. I won't automate building of packages until
we have a reliable test suite.
# TL;DR
* 3 new failures: 1 JS, 2 EUnit.
* Total issues open: *18*
* Recurrences of 3 previously reported
Hey everyone,
I had a brief private exchange with Garren about Docker, and figured it
would be better if everyone could benefit from the email chain. So here
it is!
The couchdb-docker repository has a self-contained, ready-to-run CouchDB
configuration. The intent for this is to be used in develop
- Original Message -
> From: "Daniel Munch"
>
> Now for me it feels a little as if couchdb could go into the same
> direction. While couchdb-ci has already all the necessary build and
> test steps, those are sort of duplicated in couchdb-docker, only that
> in the latter it's a little har
Hi everyone,
I just wasted half an hour debugging a Fauxton build problem
on one of my machines. Turns out I hadn't updated npm on it to
v3 (which comes with nodejs 6.x).
We no longer are able to build Fauxton with npm 2 (node 4.x).
Upgrade your dependencies. The Fauxton readme has been updated
t
Hi Nasser,
Thank you for the report.
Are you running against a single node or a clustered CouchDB 2.0
install? If clustered, how many nodes, and are they all running on
the same machine, or different machines? Have you changed any
settings in the ini files?
What sort of database do you have? Doe
1 - 100 of 942 matches
Mail list logo
