summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Merge branch 'master' into elixir-suiteelixir-suiteJoan Touzet2018-11-0761-301/+907
|\
| * #1705 Add UUID attribute to welcome message (#1708)Ryan Gordon2018-11-072-1/+20
| |
| * Use mainline rebar (v2) (#1680)lag-linaro2018-11-071-1/+1
| |
| * Fix initial view compaction task status (#1672)Paul J. Davis2018-11-071-1/+3
| | | | | | | | | | | | | | | | This is a minor consistency issue. Currently when a view compaction starts it doesn't include the `total_changes` and `changes_done` fields until the first task status update. This is easy to miss as every other task type includes those fields from the initial task definition. The obvious trivial fix is both obvious and trivial.
| * Copy _security object in couchup; python3 fix (#1721)Joan Touzet2018-11-071-1/+29
| |
| * Fix link in contributing doc (#1608)Marc Abbyad2018-11-071-1/+1
| |
| * port experimental change that came up in the elixir test suite branch (#1614)Jan Lehnardt2018-11-071-1/+3
| |
| * Merge pull request #1709 from apache/113045-case-clause-mangoPeng Hui Jiang2018-11-063-1/+48
| |\ | | | | | | Support out-of-sync between db and index in mango
| | * Support out-of-sync in mango when doc is deletedjiangph2018-11-063-1/+48
| |/ | | | | | | | | | | | | | | | | - under situation where the document is deleted while the mrview index for this document is not updated, the returned value from mrview is {doc,null}. There is no such consideration in Mango to cause case_clause error. This fix is to consider out-of-sync between documents in database and their index and not to cause 500 when the _find endpoint is called.
| * Merge pull request #1683 from cloudant/fix-_local-_bulk_docsEric Avdey2018-10-294-107/+212
| |\ | | | | | | Fixes for _local doc update and _bulk_docs operations with new_edits false
| | * Extend generation of missing id to a bulk operation with new_edits falseEric Avdey2018-10-291-13/+8
| | |
| | * Write local docs in a correct tree on a bulk operation with new_edits falseEric Avdey2018-10-292-69/+115
| | |
| | * Remove extra spaces from a test moduleEric Avdey2018-10-291-3/+3
| | |
| | * Handle an exception on an invalid rev in a local doc updateEric Avdey2018-10-291-22/+86
| |/
| * Merge pull request #1681 from apache/COUCHDB-3326-get_minimum_purge_seqPeng Hui Jiang2018-10-251-11/+13
| |\ | | | | | | Fix in get_minimum_purge_seq/1
| | * Fix get_minimum_purge_seq/1COUCHDB-3326-get_minimum_purge_seqjiangph2018-10-251-11/+13
| |/ | | | | | | | | | | | | | | - should pass DbName instead of db record to validate client, and also display error when client doesn't exist, and mem3:dbname/1 to get DbName for get_design_docs/1 COUCHDB_3326
| * Merge pull request #1677 from apache/COUCHDB-3326-mixed-clusterPeng Hui Jiang2018-10-242-2/+38
| |\ | | | | | | Allow to return with accepted for mixed nodes in cluster
| | * Allow to return with accepted for mixed nodes in clusterCOUCHDB-3326-mixed-clusterjiangph2018-10-242-2/+38
| |/ | | | | | | | | | | | | | | | | - for mixed nodes in cluster, i.e. nodes with different releases, it is possible that "accepted" result is returned instead of ok when purge request is sent. This commit is used to address badmatch error where "accepted" returned result is not considered. COUCHDB-3326
| * Fix JS/Python test harness for Python 2.6 (#1674)Joan Touzet2018-10-231-1/+1
| |
| * expose is_system_db_nameGarren Smith2018-10-232-7/+8
| | | | | | | | | | Expose is_system_db_name as a way to verify if a binary string is the name of a system database.
| * Hard code hypothesis to avoid master versions breaking buildsNick Vatamaniuc2018-10-231-1/+1
| |
| * Remove explicit python version for dev/run (for now)Joan Touzet2018-10-221-1/+1
| |
| * couchjs: show default runtime SIZE limit on help messageIblis Lin2018-10-201-0/+1
| |
| * Update snappy dependency to CouchDB-1.0.2Nick Vatamaniuc2018-10-181-1/+1
| | | | | | | | | | | | This fixes a memory bug: https://github.com/apache/couchdb-snappy/commit/2038ad13b1d6926468f25adea110028e3c0b4b0c
| * Merge pull request #1655 from cloudant/fix-lru_optsiilyak2018-10-181-18/+15
| |\ | | | | | | Fix ets_lru configuration in chttpd application
| | * Fix ets_lru configuration in chttpd applicationILYA Khlopotov2018-10-181-18/+15
| |/ | | | | | | | | The code was incorect in a sense that it was using is_integer guard, while `config:get` cannot return integer.
| * Avoid crashing if a mango query is reducedNick Vatamaniuc2018-10-181-4/+4
| | | | | | | | | | | | Previously returning null from mango native proc lead to case clause error in couch_query_servers. Instead return a proper shape but with null results for each reduction.
| * Improve restart resilience of couch_log applicationNick Vatamaniuc2018-10-181-1/+1
| | | | | | | | | | | | Previously it was too easy to crash the whole node when any of couch_log's children restarted. To improve resiliency, let couch_log application restart a few more times before taking down the whole node with it.
| * Do not crash couch_log application when gen_* servers send extra argsNick Vatamaniuc2018-10-182-23/+112
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | gen_server, gen_fsm and gen_statem might send extra args when terminating. This is a recent behavior and not handling these extra args could lead to couch_log application crashing and taking down the whole VM with it. There are two improvements to fix the issue: 1) Handle the extra args. Format them and log as they might have useful information included. 2) Wrap the whole `format` function in a `try ... catch` statement. This will avoid any other cases where the logger itself if crashing when attepting to format error events.
| * Merge pull request #1660 from apache/fix-upgrade_v5_testPeng Hui Jiang2018-10-171-2/+2
| |\ | | | | | | Fix test failure on upgrade_v5_test
| | * Fix test failure on upgrade_v5_testjiangph2018-10-171-2/+2
| |/ | | | | | | COUCHDB-3326
| * Merge pull request #1657 from apache/COUCHDB-3326-upgrade-users-dbPeng Hui Jiang2018-10-172-3/+20
| |\ | | | | | | Upgrade disk version to 7/latest for databases generated prior to clustered purge builds
| | * Upgrade disk version to 7 for databasesCOUCHDB-3326-upgrade-users-dbjiangph2018-10-162-3/+20
| |/ | | | | | | | | | | | | | | - for databases generated before this code base, the disk version needs to be upgraded to 7 or higher so that it can match the db_header with purge_tree and purge_seq_tree COUCHDB-3326
| * Merge pull request #1654 from apache/fix_exceed_limitRobert Newson2018-10-151-12/+12
| |\ | | | | | | Test correct condition for exceed_limit error
| | * Test correct condition for exceed_limit errorfix_exceed_limitRobert Newson2018-10-151-12/+12
| |/ | | | | | | | | | | | | | | | | | | | | | | | | Previously we were testing if Pos + TotalBytes exceeded the pread limit. This is the wrong logic entirely. We are trying to prevent an attempted call to file:pread/3 where the third parameter, the number of bytes to read, is a very large number (due to a corruption elsewhere, say). Instead we throw exceed_limit as soon as a file gets above a certain size. I switched this to an if statement to make it clear that the "read past EOF" and "try to read too many bytes" checks are quite distinct from each other.
| * Merge pull request #1649 from apache/COUCHDB-3326-metrics-docs-purgesPeng Hui Jiang2018-10-122-2/+14
| |\ | | | | | | Add document_purges counter for stats
| | * Add document_purges counter for statsCOUCHDB-3326-metrics-docs-purgesjiangph2018-10-122-2/+14
| |/ | | | | | | COUCHDB-3326
| * Merge pull request #1652 from cloudant/restrict-active_tasks-to-server-adminEric Avdey2018-10-111-0/+1
| |\ | | | | | | Restrict access to `_active_tasks` to server admin
| | * Restrict access to _active_tasks to server adminEric Avdey2018-10-111-0/+1
| |/
| * Merge pull request #1650 from apache/bulk_get_users_dbRobert Newson2018-10-112-2/+4
| |\ | | | | | | Pass user_ctx in _bulk_get
| | * Pass user_ctx in _bulk_getRobert Newson2018-10-112-2/+4
| |/ | | | | | | This fixes _bulk_get for _users db and probably others I don't know
| * Merge pull request #1647 from cloudant/validate-prefix-for-systemdbsiilyak2018-10-101-3/+12
| |\ | | | | | | Validate database prefix against DBNAME_REGEX for system dbs
| | * Validate database prefix against DBNAME_REGEX for system dbsILYA Khlopotov2018-10-101-3/+12
| |/ | | | | | | | | | | | | | | | | Previously we only checked that the suffix of the database is matching one of the predefined system databases. We really should check the prefix against DBNAME_REGEXP to prevent creation of illegally named databases. This fixes #1644
| * Update rebar.config.script and travis CIPaul J. Davis2018-10-042-2/+3
| | | | | | | | Fixes #1396
| * Fix use of process_info(Pid, monitored_by)Paul J. Davis2018-10-043-8/+12
| | | | | | | | | | | | | | | | | | This can now return references that are from NIFs monitoring the process. This is important for the new file IO NIFs that monitor the controlling process. For now we'll just take the easy way out by filtering the references from our returned monitor lists. Fixes #1396
| * Fix couch_log eunit testsPaul J. Davis2018-10-043-6/+11
| | | | | | | | Fixes #1396
| * Enable parameterized module callsPaul J. Davis2018-10-0418-0/+43
| | | | | | | | | | | | | | | | | | | | This is a temporary bandaid to allow us to continue using parameterized modules with Erlang 21. We'll have to go back and modify every one of these files to avoid that as well as figuring out how to upgrade mochiweb to something that doesn't use parameterized modules by the time they are fully removed from Erlang. Fixes #1396
| * Do not crash replicator on VDU function failureNick Vatamaniuc2018-10-021-1/+57
| | | | | | | | | | | | | | | | | | | | | | | | | | Previously a user could insert a VDU function into one of the _replicator databases such that it prevents the replicator application from updating documents in that db. Replicator application would then crash and prevent replications from running on the whole cluster. To avoid crashing the replicator when saving documents, log the error and return `{ok, forbidden}`. The return might seem odd but we are asserting that forbidden is an OK value in this context and explicitly handling it. This shape of the return also conforms to the expected `{ok, _Rev}` result, noticing that `_Rev` is never actually used.
| * add test for 1612ermouth2018-10-021-4/+12
| |
| * js rewrite send bodyermouth2018-10-021-1/+8
| | | | | | | | Fixes #1612