| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
| |
This primarily wraps long lines and removes trailing whitespace in the
README.md and TODO.md files. In `test/README.md`, it updates the default
admin username and password used by `dev/run`.
|
| | |
|
| |
|
|
|
|
|
|
| |
Tests based on class `UsersDbTests` don't clean up the user docs it
puts in the `_users` db. This uses the classmethod `tearDownClass` to
delete those docs.
(cherry picked from commit 3d559eb14fd709662d3eb5cda8afe9a45687c3b1)
|
| |
|
|
|
|
|
|
|
| |
After mango python tests are run, a bunch of dbs are typically left
around, e.g. `mango_test_048b290b574d4039981893097ab71912`
This deletes those test dbs after they are no longer in use.
(cherry picked from commit e05e3cdc8d16d88e7c7af8fbcc4b671b81ac2693)
|
| |
|
|
|
|
|
|
|
| |
(#2596)
* Port _design_docs tests from js to elixir
* Port design_options and design_paths tests from js to elixir
|
| | |
|
| |\
| |
| | |
doc: link README-DEV in README
|
| |/ |
|
| |\
| |
| | |
Port form_submit.js test to Elixir
|
| | | |
|
| |/ |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
There's a race between the meck:wait call in setup and killing the
config_event process. Its possible that we could kill and restart the
config_event process after meck:wait returns, but before
gen_event:add_sup_handler is called. More likely, we could end up
killing the config_event gen_event process before its fully handled the
add_sup_handler message and linked the notifier pid.
This avoids the race by waiting for config_event to return that it has
processed the add_sup_handler message instead of relying on meck:wait
for the subscription call.
|
| | |
|
| |\
| |
| |
| |
| | |
dottorblaster/upgrade-credo-to-1.2.0-disable-legacy-checks
Upgrade credo to 1.2.0 disable legacy checks
|
| | | |
|
| |/ |
|
| |\
| |
| | |
Port changes.js test suite into elixir
|
| |/ |
|
| | |
|
| |
|
|
| |
This reverts commit 91ecf6777cc5fff93483b8e92c8daadd7ff33fdc.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
I found a .view file with a db_header in production (cause unknown but
I'm hoping it's manual intervention).
This patch means we'll reset the index if we find something other than
a view header when looking for one.
|
| |
|
|
|
|
|
|
|
| |
It can be desirable in some cases for decoded JSON to e.g. return
maps instead of the default data structure, which is not currently
possible.
This exposes a new function `couch_util:decode/2`, the second
parameter being a list of options passed to `jiffy:decode/2`.
|
| | |
|
| |
|
|
| |
Port reduce_false.js and reduce_builtin.js to Elixir
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Allows `configure.ps1` to correctly pull and build `rebar` on Windows
* Removes the static declarations in `rebar.config.script` on
specific, pre-determined paths to various includes/libraries
necessary for NIFs and external binaries (expectation is these are
passed in env vars INCLUDE, LIB and LIBPATH)
* fixes the SM60 `couchjs` build by telling `windows.h` not to
redefine min and max as macros through a `#define`
* fixes the `make eunit` target on Windows
* Adds the missing `EXE_LINK_CXX_TEMPLATE` that our rebar doesn't have,
but `enc` has today, which is also causing a failed `couchjs` (C++)
build on Windows
* Causes `make python-black` to correctly cause failure in `make check`
if it finds problems
* fixes Mango tests on Python 3.8 by bumping the hypothesis dependency
* fixes one Elixir test on Windows (incorrect calculation of `now(:ms)`
due to Erlang clock precision difference)
* a little bit of python black cleanup (mango tests)
|
| | |
|
| |
|
|
|
|
|
|
|
| |
Observed on FreeBSD Jenkins test runner:
```
function couch_replicator_clustering:setup/0 (src/couch_replicator_clustering.erl, line 257)
**error:{badmatch,{error,{already_started,<0.3165.0>}}} in module 'couch_replicator_clustering'
```
|
| |
|
|
|
|
| |
This changes the couchjs OOM test so that it will trigger more reliably
on SpiderMonkey 60. It appears that newer SpiderMonkeys are better at
conserving memory usage which takes this test longer to trigger.
|
| | |
|
| |
|
|
| |
This fixes builds on Windows and CentOS.
|
| |
|
|
|
|
|
|
|
|
| |
Since the backend port is closed by default, remove the cache service
since it was shown to cause monitor leaks, and it just consumes resources
running in the background when almost nobody uses it. The few utility scripts
that might use the backend port can just get the auth docs directly from the
db.
Issue: https://github.com/apache/couchdb/issues/2493
|
| | |
|
| | |
|
| |\
| |
| | |
Fix highlight_post_tag parsing from json request body
|
| | | |
|
| |/
|
|
| |
Fixes #2520
|
| | |
|
| |
|
|
|
|
|
| |
The CouchDB API defines the warning field returned by _find to be
a string (and this is what Fauxton expects). 5d55e289 was missing
a string conversion and returned the warning(s) as an array. This
restores the intended behaviour.
|
| | |
|
| | |
|
| |
|
|
| |
It just needed a few clauses in send and recv_loop it turns out.
|
| | |
|
| |
|
|
|
| |
Jiffy changed its exception type in 1.0 to match the standard Erlang
style for exceptions that cross an API boundary.
|
| |
|
|
|
| |
* b64url 1.0.1 -> 1.0.2
* jiffy CouchDB-0.14.11-2 -> CouchDB-1.0.1-1
|
| | |
|
| | |
|
| | |
|
| | |
|
