cloudant_bigcouch.git/apps/couch, branch debian

Invoke couch_view_updater with the proper arguments

2012-03-20T04:53:45+00:00

This fixes stale=update_after.

Fix previous commit

2012-01-31T21:59:28+00:00

Fix bug in replicator request piplining

2012-01-31T19:37:53+00:00

A replication with both an HTTP source and target on the same host and
port could end up in a dead lock due to ibrowse replication pipelining
when attachments are present on the source. The ibrowse http worker
would end up forming a multipart/mime body using anonymous reader
functions for attachment stubs. When the attachment stub functions are
executed it is possible that they end up assigned to the same ibrowse
worker.

This is a bit of a long path but then end result is equivalent to
calling gen_server:call(self(), Args, infinity) from a gen_server
callback.

A quick work around for users is to set up a DNA alias (possibly in
/etc/hosts) or to use a combination of hostname and ip address so that
ibrowse assigns the requests to different pools.

Minor bug getting the reduce_limit setting

2012-01-24T09:29:40+00:00

Revert use of spawn_monitor

2012-01-18T13:40:02+00:00

As Filipe correctly points out, we want the parent to die if the child dies.

Only set the process dictionary if exit was ok

2012-01-16T22:11:20+00:00

Use spawn_monitor to await process completion

2012-01-16T19:03:03+00:00

BugzID: 13133

Conditionally apply JSON encoding to update_seq values

2011-11-09T19:30:11+00:00

BigCouch 0.3 cannot parse requests of the form /db/_changes?since="123-foo" so
the recent ?JSON_ENCODE addition to Since in two places causes 0.3 <-> 0.4
replication to fail with json_encode/badterm errors.

This patch applies JSON encoding only when the Since value is not already a
binary (i.e, when it's a [integer(), binary()]) and interop is restored.

BugzID: 12833

Merge commit '1.1.1' into 0.4.x

2011-10-31T18:54:51+00:00

Conflicts:
	acinclude.m4.in
	configure.ac
	couchjs/c_src/http.c
	src/erlang-oauth/Makefile.am
	src/erlang-oauth/oauth.app.in
	src/erlang-oauth/oauth_hmac_sha1.erl
	src/erlang-oauth/oauth_http.erl
	src/erlang-oauth/oauth_plaintext.erl
	src/etap/etap_web.erl

Fix retrieval of headers larger than 4k

2011-10-31T17:13:59+00:00

Our headers start with a <<1>> and then four bytes indicating the length
of the header and its checksum. When the header is larger than 4090
bytes it will be split across multiple blocks in the file and will need
to be reassembled on read. The reassembly consists of stripping out
<<0>> from the beginning of each subsequent block in the
remove_block_prefixes/2 function. The bug here is that we tell
remove_block_prefixes that we're starting 1 byte into the current block
instead of 5, so it ends up removing one good byte from the header and
injecting one or more random <<0>>s.

Headers larger than 4k are very rare and generally require a view group
with a huge number of indexes or indexes with fairly large reductions,
which explains why this bug has gone undetected until now.

Closes COUCHDB-1319.