couchdb:prometheus-endpoint2

Last commit made on 2021-01-26
Get this branch:
git clone -b prometheus-endpoint2 https://git.launchpad.net/couchdb

Branch merges

Branch information

Name:
prometheus-endpoint2
Repository:
lp:couchdb

Recent commits

1b3f254... by jiangph <email address hidden>

introduce prometheus endpoint

af436c1... by Joan Touzet <email address hidden>

Goodbye 2020. Hello 2021. YES. (#3318)

df2fb67... by Robert Newson <email address hidden>

treat 408 as a retryable error condition (#3303)

be87c40... by iilyak <email address hidden>

Merge pull request #3286 from cloudant/specify-elixir-tests

Add ability to control which Elixir integration tests to run

5b8bf5a... by ILYA Khlopotov <email address hidden>

Use elixir-suite

109f74f... by ILYA Khlopotov <email address hidden>

Add ability to control which Elixir integration tests to run

New `elixir-suite` Makefile target is added. It runs a predefined set of elixir
integration tests.

The feature is controlled by two files:
- test/elixir/test/config/suite.elixir - contains list of all available tests
- test/elixir/test/config/skip.elixir - contains list of tests to skip

In order to update the `test/elixir/test/config/suite.elixir` when new tests
are added. The one would need to run the following command:

```
MIX_ENV=integration mix suite > test/elixir/test/config/suite.elixir
```

c362b1c... by =?utf-8?q?Bessenyei_Bal=C3=A1zs_Don=C3=A1t?= <email address hidden>

Add missing default headers to responses (#3279)

Add missing default headers to responses

3168a4d... by Paul J. Davis

Remove unnecessary line wraps

27e8e33... by Paul J. Davis

Minimize conflicts while building views

This flips the view indexer to grab the database update_seq outside of
the update transaction. Previously we would cosntantly refresh the
db_seq value on every retry of the transactional loop.

We use a snapshot to get the update_seq so that we don't trigger
spurious read conflicts with any clients that might be updating the
database.

0e91f2f... by Paul J. Davis

Allow specifying an end_key for fold_changes

This is useful so that read conflicts on the changes feed will
eventually be resolved. Without an end key specified a reader could end
up in an infinite conflict retry loop if there are clients updating
documents in the database.