| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
This allows to keep features on config process restart
|
| |
|
|
|
|
| |
Remove couch_compaction_daemon and related tests too.
|
| |
|
|
|
|
| |
This fixes inability to set keys with regex symbols in them
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It has a fix to revert user socket buffer size to 8192 and also
allow setting this buffer values directly (not necessarily
via {recbuf, ...}).
Fixes #1810
Warning:
2.19.0 blacklists a series of OTP releases: 21.2, 21.2.1, 21.2.2
This is done via a runtime check of the ssl application version.
The blacklist seems valid as there is a bug which prevents data from
being delivered on TSL sockets. That could affect either CouchDB
server side (chttpd) or replication client side (ibrowse).
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Move couch_event and mem3 modules earlier in the list of SubDirs to
suppress behaviour undefined warnings.
This has the side effect of running the tests in the new order, which
induces failures in couch_index tests. Those failures are related to
quorum, and can be traced to mem3 seeds tests leaving a _nodes db
containing several node docs in the tmp/data directory, ultimately
resulting in badmatch errors e.g. when a test expects 'ok' but gets
'accepted' instead.
To prevent test failures, a cleanup function is implemented which
deletes any existing "nodes_db" left after test completion.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
This fixes a memory bug:
https://github.com/apache/couchdb-snappy/commit/2038ad13b1d6926468f25adea110028e3c0b4b0c
|
|
|
|
| |
Fixes #1396
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
This reverts commit 817b2b6f5f0883092df60c1ec8ec7ec6d6094a23.
|
| |
|
| |
|
| |
|
|
|
|
| |
Issue #1396
|
| |
|
| |
|
|
|
|
|
|
| |
Flag `debug_info` auto-propagated from rebar,
so there are no need to set it manually or we'll
end up with a double entry in opts.
|
|
|
|
| |
This reverts commit b58021e6d9751fa36a4164974664e86248d444fd.
|
|
|
|
|
|
|
|
|
|
|
| |
This introduces a new builtin reduce function, which uses a HyperLogLog
algorithm to estimate the number of distinct keys in the view index. The
precision is currently fixed to 2^11 observables andtherefore uses
approximately 1.5 KB of memory.
It also introduces a finalize step which can be used to improve the
efficiency of other builtin reduce functions going forward.
Closes COUCHDB-2971
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Key tree module is a candidate to use property tests on as it mostly deals with
manipulating a single data structure and functions are referentially
transparent, that is, they aren't many side-effects like IO for example.
The test consists of two main parts - generators and properties.
Generators generate random input, for example revision trees, and properties
check that certain properties hold, for example that after stemming all the
leaves are still present in the revtree.
To run the test:
make eunit apps=couch suites=couch_key_tree_prop_tests
|
| |
|
|
|
|
| |
This adds fixes to handle non-persistent set_integer/set_boolean values
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
As discussed in
http://erlang.org/doc/efficiency_guide/binaryhandling.html, the
bin_opt_info option can have the compiler print information about
binary optimizations. Typically, it issues warnings about code that
can not be optimized. For example, with the option enabled, it warns
about this line of code (among many others) like this:
src/chttpd/src/chttpd_auth_cache.erl:183:
Warning: NOT OPTIMIZED: sub binary is used or returned
Not only should having this option enabled draw awareness to existing
sub-optimal binary constructs, it should help developers avoid
creating new ones.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
To fix random compatibility issue
|
|
|
|
| |
Folsom depended on 0.8.2 as well so had to update folsom and bump its tag.
|
| |
|
| |
|
| |
|