profile
viewpoint
Jan Lehnardt janl Neighbourhoodie Software Berlin, Germany http://neighbourhood.ie Makes @couchdb & #offlinefirst. Made @jsconfeu @greenkeeperio @hoodiehq. CEO at @neighbourh00die. Dissatisfied with the status-quo.

gr2m/CORS-Proxy 373

über-simple node.js-Proxy to enable CORS request for any website

espy/ubersicht 243

A dashboard for recent activity on all of a user's or organisation's repos

janl/awesome 175

A Redis implementation in node.js

HenrikJoreteg/human-javascript 77

Book on building sanely architected JS apps

gr2m/milestones 68

A Google GitHub backed Milestone thingy

dscape/ghcopy 49

Dead simple copy paste from your shell to github gist

greenkeeperio/website 16

:link: interwebs presence

janl/.js 10

.js

cobot/couchdb-action 3

Run CouchDB in a GitHub workflow.

issue commentapache/couchdb-docker

Set single_node using an environment variable?

ah I found this: https://github.com/apache/couchdb/discussions/2948#discussioncomment-29228

I’d be okay for “one more env var” if this was the last one, as it is a basic setup thing (kinda like admin user/pass) , but I’m equally fine with letting folks do this the proper way.

coreyfarrell

comment created time in 9 hours

issue commentapache/couchdb-docker

Set single_node using an environment variable?

Oops sorry, I must have missed those objections, where can I find them?

coreyfarrell

comment created time in 9 hours

issue commentjanl/node-jsonpointer

Setting value to undefined removes property

yeah, this is by design https://github.com/janl/node-jsonpointer/pull/27

I’d accept a PR that implements set(obj, pointer, value, {allowUndefinedValue: true}). Bonus points for a way to instantiate a set fun that has that option bound to it for each invocation.

Please file a PR directly.

danrot

comment created time in 3 days

delete branch apache/couchdb

delete branch : fix/gen-server-timeout-on-ioq-bypass

delete time in 3 days

delete branch apache/couchdb

delete branch : fix/gen-server-timeout-on-ioq-bypass-3.x

delete time in 3 days

push eventapache/couchdb

Jan Lehnardt

commit sha ace7e68951eb0cd57740cbb6086054a1174141d5

fix: set gen_server:call() timeout to infinity on ioq bypass Before the bypass existed, ioq would call `gen_server:call()` on hehalf of it calling module with the queueing logic in between. Commit e641a740 introduced a way to bypass any queues, but the delegated `gen_server:call()` there was added without a timeout parameter, leading to a default timeout of 5000ms. A problem manifests here when operations that are sent through ioq that take longer than that 5000ms timeout. In practice, these operations should be very rare and this timeout should be a help on overloaded systems. However, one sure-fire way to cause an issue on an otherwise idle machine is raise the max_document_size and store unreasonably large documents, think 50MB+ of raw JSON). Not that we recommend this, but folks have run this fine on 2.x before the ioq changes and it isn’t too hard to support here. By adding an `infinity` timeout delegated `gen_server:call()` in the queue bypasse case, this no longer applies. Thanks to Joan @woahli Touzet, Bob @rnewson Newson and Paul @davisp Davis for helping to track this down.

view details

push time in 3 days

PR merged apache/couchdb

Reviewers
fix: set gen_server:call() timeout to infinity on ioq bypass

Before the bypass existed, ioq would call gen_server:call() on hehalf of it calling module with the queueing logic in between.

Commit e641a740 introduced a way to bypass any queues, but the delegated gen_server:call() there was added without a timeout parameter, leading to a default timeout of 5000ms.

A problem manifests here when operations that are sent through ioq that take longer than that 5000ms timeout. In practice, these operations should be very rare and this timeout should be a help on overloaded systems. However, one sure-fire way to cause an issue on an otherwise idle machine is raise the max_document_size and store unreasonably large documents, think 50MB+ of raw JSON).

Not that we recommend this, but folks have run this fine on 2.x before the ioq changes and it isn’t too hard to support here.

By adding an infinity timeout delegated gen_server:call() in the queue bypasse case, this no longer applies.

Thanks to Joan @wohali Touzet, Bob @rnewson Newson and Paul @davisp Davis for helping to track this down.

+1 -1

1 comment

1 changed file

janl

pr closed time in 3 days

pull request commentapache/couchdb

fix: set gen_server:call() timeout to infinity on ioq bypass

transitive +1 via https://github.com/apache/couchdb/pull/2980

janl

comment created time in 3 days

push eventapache/couchdb

Jan Lehnardt

commit sha 0eedd8bcd4f7d2a86d5caded3a0bc0a963c24dc7

fix: set gen_server:call() timeout to infinity on ioq bypass Before the bypass existed, ioq would call `gen_server:call()` on hehalf of it calling module with the queueing logic in between. Commit e641a740 introduced a way to bypass any queues, but the delegated `gen_server:call()` there was added without a timeout parameter, leading to a default timeout of 5000ms. A problem manifests here when operations that are sent through ioq that take longer than that 5000ms timeout. In practice, these operations should be very rare and this timeout should be a help on overloaded systems. However, one sure-fire way to cause an issue on an otherwise idle machine is raise the max_document_size and store unreasonably large documents, think 50MB+ of raw JSON). Not that we recommend this, but folks have run this fine on 2.x before the ioq changes and it isn’t too hard to support here. By adding an `infinity` timeout delegated `gen_server:call()` in the queue bypasse case, this no longer applies. Thanks to Joan @woahli Touzet, Bob @rnewson Newson and Paul @davisp Davis for helping to track this down.

view details

push time in 3 days

PR merged apache/couchdb

fix: set gen_server:call() timeout to infinity on ioq bypass

Before the bypass existed, ioq would call gen_server:call() on hehalf of it calling module with the queueing logic in between.

Commit e641a740 introduced a way to bypass any queues, but the delegated gen_server:call() there was added without a timeout parameter, leading to a default timeout of 5000ms.

A problem manifests here when operations that are sent through ioq that take longer than that 5000ms timeout. In practice, these operations should be very rare and this timeout should be a help on overloaded systems. However, one sure-fire way to cause an issue on an otherwise idle machine is raise the max_document_size and store unreasonably large documents, think 50MB+ of raw JSON).

Not that we recommend this, but folks have run this fine on 2.x before the ioq changes and it isn’t too hard to support here.

By adding an infinity timeout delegated gen_server:call() in the queue bypasse case, this no longer applies.

Thanks to Joan @wohali Touzet, Bob @rnewson Newson and Paul @davisp Davis for helping to track this down.

+1 -1

0 comment

1 changed file

janl

pr closed time in 3 days

startedhimpun/platform

started time in 3 days

issue closedjanl/node-jsonpointer

The automated release is failing 🚨

:rotating_light: The automated release from the master branch failed. :rotating_light:

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.


Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two-Factor Authentication, make configure the auth-only level is supported. semantic-release cannot publish with the default auth-and-writes level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.


Good luck with your project ✨

Your semantic-release bot :package::rocket:

<!-- semantic-release:github -->

closed time in 3 days

janl

issue commentjanl/node-jsonpointer

CLI usage

:tada: This issue has been resolved in version 4.1.0 :tada:

The release is available on:

Your semantic-release bot :package::rocket:

joeyespo

comment created time in 3 days

issue commentjanl/node-jsonpointer

Does the typescript typings file work?

:tada: This issue has been resolved in version 4.1.0 :tada:

The release is available on:

Your semantic-release bot :package::rocket:

marcbachmann

comment created time in 3 days

pull request commentjanl/node-jsonpointer

Update dependencies to enable Greenkeeper 🌴

:tada: This PR is included in version 4.1.0 :tada:

The release is available on:

Your semantic-release bot :package::rocket:

greenkeeper[bot]

comment created time in 3 days

pull request commentjanl/node-jsonpointer

typings added

:tada: This PR is included in version 4.1.0 :tada:

The release is available on:

Your semantic-release bot :package::rocket:

KeeReal

comment created time in 3 days

pull request commentjanl/node-jsonpointer

chore(ci): add newer node versions explicitly

:tada: This PR is included in version 4.1.0 :tada:

The release is available on:

Your semantic-release bot :package::rocket:

janl

comment created time in 3 days

pull request commentjanl/node-jsonpointer

chore: add packge-lock and .gitignore

:tada: This PR is included in version 4.1.0 :tada:

The release is available on:

Your semantic-release bot :package::rocket:

janl

comment created time in 3 days

pull request commentjanl/node-jsonpointer

chore: add semantic release

:tada: This PR is included in version 4.1.0 :tada:

The release is available on:

Your semantic-release bot :package::rocket:

janl

comment created time in 3 days

pull request commentjanl/node-jsonpointer

Update standard to the latest version 🚀

:tada: This PR is included in version 4.1.0 :tada:

The release is available on:

Your semantic-release bot :package::rocket:

greenkeeper[bot]

comment created time in 3 days

pull request commentjanl/node-jsonpointer

Include typings in npm distribution

:tada: This PR is included in version 4.1.0 :tada:

The release is available on:

Your semantic-release bot :package::rocket:

FabianFrank

comment created time in 3 days

pull request commentjanl/node-jsonpointer

fix: prototype pollution

:tada: This PR is included in version 4.1.0 :tada:

The release is available on:

Your semantic-release bot :package::rocket:

janl

comment created time in 3 days

pull request commentjanl/node-jsonpointer

feat: re-add semantic release

:tada: This PR is included in version 4.1.0 :tada:

The release is available on:

Your semantic-release bot :package::rocket:

janl

comment created time in 3 days

release janl/node-jsonpointer

v4.1.0

released time in 3 days

created tagjanl/node-jsonpointer

tagv4.1.0

JSON Pointer implementation for Node.js

created time in 3 days

push eventjanl/node-jsonpointer

Jan Lehnardt

commit sha b67e4026a102fe98ed896b4ad271db3c131a944b

feat(docs): thank contributors

view details

push time in 3 days

created tagjanl/node-jsonpointer

tagv4.0.1

JSON Pointer implementation for Node.js

created time in 3 days

created tagjanl/node-jsonpointer

tagv1.1.0

JSON Pointer implementation for Node.js

created time in 3 days

push eventjanl/node-jsonpointer

Jan Lehnardt

commit sha ad96a94fd272555db91ab33a8927558d212ca714

feat(docs): use `npm test`

view details

push time in 3 days

created tagjanl/node-jsonpointer

tagv1.0.0

JSON Pointer implementation for Node.js

created time in 3 days

issue openedjanl/node-jsonpointer

The automated release is failing 🚨

:rotating_light: The automated release from the master branch failed. :rotating_light:

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.


Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two-Factor Authentication, make configure the auth-only level is supported. semantic-release cannot publish with the default auth-and-writes level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.


Good luck with your project ✨

Your semantic-release bot :package::rocket:

<!-- semantic-release:github -->

created time in 3 days

issue closedjanl/node-jsonpointer

Ensure RFC 6901 compliance

The README still references an early draft. Update, and ensure that we're compliant with RFC 6901.

closed time in 3 days

hildjj

issue commentjanl/node-jsonpointer

Ensure RFC 6901 compliance

Done!

hildjj

comment created time in 3 days

delete branch janl/node-jsonpointer

delete branch : feat/sr

delete time in 3 days

push eventjanl/node-jsonpointer

Jan Lehnardt

commit sha 49b7074a61a5ada60d0b26c106cb5acc7b916a74

feat: re-add semantic release

view details

Jan Lehnardt

commit sha 864f21ab9fd5e7bc80bc0775a8c5f25382f5403b

Merge pull request #48 from janl/feat/sr feat: re-add semantic release

view details

push time in 3 days

PR merged janl/node-jsonpointer

feat: re-add semantic release
+12 -0

0 comment

1 changed file

janl

pr closed time in 3 days

PR opened janl/node-jsonpointer

feat: re-add semantic release
+12 -0

0 comment

1 changed file

pr created time in 3 days

create barnchjanl/node-jsonpointer

branch : feat/sr

created branch time in 3 days

delete branch janl/node-jsonpointer

delete branch : fix/proto

delete time in 3 days

push eventjanl/node-jsonpointer

Jan Lehnardt

commit sha dc3ea9bf1414fb468104f68470d59e867953fb46

chore: update lockfile

view details

Jan Lehnardt

commit sha 234e3437019c6c07537ed2ad1e03b3e132b85e34

fix: prototype pollution for curiousity’s sake, I checked if this has any significant performance impact and it does not. Based on 10 runs before and after, all values in percent: MED AVG get first level property 0.37 0.42 get second level property 0.40 0.61 get third level property 0.26 0.41 set first level property 2.25 2.16 set second level property 1.45 1.67 set third level property 2.05 1.98 push property into array -0.41 -0.51 2.25% slowdown as a worst case is not significant.

view details

Jan Lehnardt

commit sha f5360601cc468de7724cc42435bc0fd1a19e2c62

chore: update readme, copyright, RFC link

view details

Jan Lehnardt

commit sha 82591117de41f89c23fbacbb33a4e8c8ceaab2ad

chore: remove GK lockfile and bump node versions in testing fix: update devdeps fix: drop node 6 from test matrix, we are still copmpatbile tho, this is for standard chore: ditch standard, so we can support older node versions in testing chore: use older npm version so we can support older nodes chore: master branch builds only chore: prefer npm install to npm ci https://github.com/nodejs/node/issues/29841 chore: newer npm after all chore: no node 6 then grmpf chore: re-add standard

view details

Jan Lehnardt

commit sha 19353349d627ab347dd1c9a435553ca872739b72

Merge pull request #47 from janl/fix/proto fix: prototype pollution

view details

push time in 3 days

PR merged janl/node-jsonpointer

fix: prototype pollution

For curiousity’s sake, I checked if this has any significant performance impact and it does not.

Based on 10 runs before and after, all values in percent:

                         MED    AVG
get first level property 0.37	0.42
get second level property 0.40	0.61
get third level property 0.26	0.41
set first level property 2.25	2.16
set second level property 1.45	1.67
set third level property 2.05	1.98
push property into array -0.41	-0.51

2.25% slowdown as a worst case is not significant.

+6265 -2683

0 comment

6 changed files

janl

pr closed time in 3 days

push eventjanl/node-jsonpointer

Jan Lehnardt

commit sha f5360601cc468de7724cc42435bc0fd1a19e2c62

chore: update readme, copyright, RFC link

view details

Jan Lehnardt

commit sha 82591117de41f89c23fbacbb33a4e8c8ceaab2ad

chore: remove GK lockfile and bump node versions in testing fix: update devdeps fix: drop node 6 from test matrix, we are still copmpatbile tho, this is for standard chore: ditch standard, so we can support older node versions in testing chore: use older npm version so we can support older nodes chore: master branch builds only chore: prefer npm install to npm ci https://github.com/nodejs/node/issues/29841 chore: newer npm after all chore: no node 6 then grmpf chore: re-add standard

view details

push time in 3 days

push eventjanl/node-jsonpointer

Jan Lehnardt

commit sha 3870a8a00e8eb8634419c48aad9130a06e6defc9

chore: re-add standard

view details

push time in 3 days

push eventjanl/node-jsonpointer

Jan Lehnardt

commit sha a7ad67cb1b3c1410ba4d925058eb3ae3c734dc60

chore: no node 6 then grmpf

view details

push time in 3 days

push eventjanl/node-jsonpointer

Jan Lehnardt

commit sha a2c0642beb0692dcf66dfce64a3a5267dcd97cdf

chore: newer npm after all

view details

push time in 3 days

push eventjanl/node-jsonpointer

Jan Lehnardt

commit sha de77be00eb9d356c8deb00a34689b927471d1fc9

chore: prefer npm install to npm ci https://github.com/nodejs/node/issues/29841

view details

push time in 3 days

push eventjanl/node-jsonpointer

Jan Lehnardt

commit sha c0a8ab31246a107884baeb6cfda919f0dbb81abf

chore: master branch builds only

view details

push time in 3 days

issue closedapache/couchdb-docker

Set single_node using an environment variable?

Expected Behavior

I'm looking for a way to run a temporary couchdb container with single_node=true set.

Current Behavior

single_mode=false is the default, this causes system databases to not be created and spams the log with failed access. The default be changed without mounting a volume or creating an inherited container image.

Possible Solution

Enable support for -e COUCHDB_SINGLE_NODE=true from the initialization script.

Context

I'm trying to use this container as part of an automated test suite for a daemon that will use couchdb for storage. The hope is to use the following command to start a docker container:

podman run \
  --rm \
  -e COUCHDB_USER=admin \
  -e COUCHDB_PASSWORD=admin \
  -e COUCHDB_SINGLE_NODE=true \
  -p 127.0.0.1:5984:5984 \
  docker.io/library/couchdb:3

I attempted to mount ./fixtures/couchdb to /opt/couchdb/etc/local.d with a local.ini in that folder. I received SELinux errors first then adding the :Z option to the folder mount gave an error relabeling content in /usr is not allowed (my code is under /usr/src). I then tried using mktemp -d and copying my local.ini to that temp directory. This allowed couchdb-docker to start and recognize single_node=true but unfortunately resulted in the temporary directory ownership being taken over (so removing it after the container runs would require sudo).

Your Environment

  • Version used: 3.1.0
  • Browser Name and version: None
  • Operating System and version (desktop or mobile): Fedora 32, using podman 2.0.1.
  • Link to your project: N/A

closed time in 3 days

coreyfarrell

issue commentapache/couchdb-docker

Set single_node using an environment variable?

Duplicate of https://github.com/apache/couchdb/discussions/2948

basically: PRs welcome ;)

coreyfarrell

comment created time in 3 days

push eventjanl/node-jsonpointer

Jan Lehnardt

commit sha 391b1e43154771abe00d9a6eb2e4018f7a8ea7e5

chore: use older npm version so we can support older nodes

view details

push time in 3 days

push eventjanl/node-jsonpointer

Jan Lehnardt

commit sha 1847c0800c74ae838f1a6c7d6e3dfc32ce197f00

chore: ditch standard, so we can support older node versions in testing

view details

push time in 3 days

push eventjanl/node-jsonpointer

Jan Lehnardt

commit sha 799962a665103a8b9a7c6b5900e9851010e36587

chore: ditch standard, so we can support older node versions in testing

view details

push time in 3 days

push eventjanl/node-jsonpointer

Jan Lehnardt

commit sha 4f925cc2af644c494a2b890e47d4b683bd878682

chore: update readme, copyright, RFC link

view details

push time in 3 days

push eventjanl/node-jsonpointer

Jan Lehnardt

commit sha 95b54f0a3295c4075da7565d9e0ae76adf5e70fe

fix: drop node 6 from test matrix, we are still copmpatbile tho, this is for standard

view details

push time in 3 days

issue closedjanl/node-jsonpointer

Version 10 of node.js has been released

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

  • Added the new Node.js version to your .travis.yml
  • The new Node.js version is in-range for the engines in 1 of your package.json files, so that was left alone

If you’re interested in upgrading this repo to Node.js 10, you can <a href="/janl/node-jsonpointer/compare/master...janl:greenkeeper%2Fupdate-to-node-10">open a PR with these changes</a>. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

<details> <summary>More information on this issue</summary>

Greenkeeper has checked the engines key in any package.json file, the .nvmrc file, and the .travis.yml file, if present.

  • engines was only updated if it defined a single version, not a range.
  • .nvmrc was updated to Node.js 10
  • .travis.yml was only changed if there was a root-level node_js that didn’t already include Node.js 10, such as node or lts/*. In this case, the new version was appended to the list. We didn’t touch job or matrix configurations because these tend to be quite specific and complex, and it’s difficult to infer what the intentions were.

For many simpler .travis.yml configurations, this PR should suffice as-is, but depending on what you’re doing it may require additional work or may not be applicable at all. We’re also aware that you may have good reasons to not update to Node.js 10, which is why this was sent as an issue and not a pull request. Feel free to delete it without comment, I’m a humble robot and won’t feel rejected :robot:

</details>


<details> <summary>FAQ and help</summary>

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper. </details>


Your Greenkeeper Bot :palm_tree:

closed time in 3 days

greenkeeper[bot]

push eventjanl/node-jsonpointer

Jan Lehnardt

commit sha 7cc0d3e625096bc1443e993ca013e7aff8acf54c

fix: update devdeps

view details

push time in 3 days

PR closed janl/node-jsonpointer

Update standard to the latest version 🚀 greenkeeper

Version 12.0.0 of standard was just published.

<table> <tr> <th align=left> Dependency </th> <td> <a target=_blank href=https://github.com/standard/standard>standard</a> </td> </tr> <tr> <th align=left> Current Version </th> <td> 11.0.1 </td> </tr> <tr> <th align=left> Type </th> <td> devDependency </td> </tr> </table>

The version 12.0.0 is not covered by your current version range.

If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.

It might be worth looking into these changes and trying to get this project onto the latest version of standard.

If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.


<details> <summary>Commits</summary> <p>The new version differs by 91 commits.</p> <ul> <li><a href="https://urls.greenkeeper.io/standard/standard/commit/ff1a15638853c5ab93223566238c68c7eeb6695b"><code>ff1a156</code></a> <code>authors</code></li> <li><a href="https://urls.greenkeeper.io/standard/standard/commit/17727fc20b48c8f0714f9ec6838e824c72ebd875"><code>17727fc</code></a> <code>12.0.0</code></li> <li><a href="https://urls.greenkeeper.io/standard/standard/commit/bdbd248c2ba8a1f3e2e356af923e541ca8d5f4dd"><code>bdbd248</code></a> <code>changelog</code></li> <li><a href="https://urls.greenkeeper.io/standard/standard/commit/3db3a624560a33e69e3b59fda361aefe93f40b79"><code>3db3a62</code></a> <code>https</code></li> <li><a href="https://urls.greenkeeper.io/standard/standard/commit/cf1802c945d83b7163059c5736762c619ffaea57"><code>cf1802c</code></a> <code>eslint-plugin-standard ~4.0.0</code></li> <li><a href="https://urls.greenkeeper.io/standard/standard/commit/7d779b87a25348b1fbd37b50b1f88af005f9cbf8"><code>7d779b8</code></a> <code>eslint-plugin-import ~2.14.0</code></li> <li><a href="https://urls.greenkeeper.io/standard/standard/commit/66f676b8678698b3d8c7dcea849a4dc5535c834e"><code>66f676b</code></a> <code>eslint ~5.4.0</code></li> <li><a href="https://urls.greenkeeper.io/standard/standard/commit/3933c6b778b624cb1de4de24eabcd545f17ab41e"><code>3933c6b</code></a> <code>Use npm versions of eslint shared configs</code></li> <li><a href="https://urls.greenkeeper.io/standard/standard/commit/c00dc668f3bc4fb1b7d7fa31220cf8f6309d0adb"><code>c00dc66</code></a> <code>Use ~ for eslint dep</code></li> <li><a href="https://urls.greenkeeper.io/standard/standard/commit/588d5ab541889efe93bc05a70e9bf0593bf264e0"><code>588d5ab</code></a> <code>Add links to French README translation!</code></li> <li><a href="https://urls.greenkeeper.io/standard/standard/commit/aee57b4d4dd8779b38ead873ad309193ceeaa91f"><code>aee57b4</code></a> <code>ESLint 5</code></li> <li><a href="https://urls.greenkeeper.io/standard/standard/commit/c89d5c7e77264cd92a0bd330514e6ca37531a9f6"><code>c89d5c7</code></a> <code>Merge pull request #1145 from theo4u/patch-1</code></li> <li><a href="https://urls.greenkeeper.io/standard/standard/commit/6477dbf2559552ec86d9a7375c8a97379ff361d8"><code>6477dbf</code></a> <code>Merge pull request #1184 from standard/greenkeeper/babel-eslint-9.0.0</code></li> <li><a href="https://urls.greenkeeper.io/standard/standard/commit/8792b9b3718e918cca072e57fb53c4e5980bf422"><code>8792b9b</code></a> <code>Merge pull request #1180 from standard/greenkeeper/eslint-plugin-promise-4.0.0</code></li> <li><a href="https://urls.greenkeeper.io/standard/standard/commit/ff070b8ee778c3b6f42a98b9fed77b80ac9ff4b3"><code>ff070b8</code></a> <code>Merge branch 'master' into greenkeeper/eslint-plugin-promise-4.0.0</code></li> </ul> <p>There are 91 commits in total.</p> <p>See the <a href="https://urls.greenkeeper.io/standard/standard/compare/670a3be9e96cc1808b47ecabcddb742bff49f898...ff1a15638853c5ab93223566238c68c7eeb6695b">full diff</a></p> </details>

<details> <summary>FAQ and help</summary>

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper. </details>


Your Greenkeeper bot :palm_tree:

+1 -1

14 comments

1 changed file

greenkeeper[bot]

pr closed time in 3 days

PR closed janl/node-jsonpointer

Update semantic-release to the latest version 🚀 greenkeeper

Version 11.0.2 of semantic-release was just published.

<table> <tr> <th align=left> Dependency </td> <td> semantic-release </td> </tr> <tr> <th align=left> Current Version </td> <td> 8.2.3 </td> </tr> <tr> <th align=left> Type </td> <td> devDependency </td> </tr> </table>

The version 11.0.2 is not covered by your current version range.

If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.

It might be worth looking into these changes and trying to get this project onto the latest version of semantic-release.

If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.


<details> <summary>Release Notes</summary> <strong>v11.0.2</strong>

<p><a name="user-content-11.0.2"></a></p> <h2><a href="https://urls.greenkeeper.io/semantic-release/semantic-release/compare/v11.0.1...v11.0.2">11.0.2</a> (2017-12-10)</h2> <h3>Bug Fixes</h3> <ul> <li>log plugin type in addition of path (<a href="https://urls.greenkeeper.io/semantic-release/semantic-release/commit/4053d8f">4053d8f</a>)</li> </ul> </details>

<details> <summary>Commits</summary> <p>The new version differs by 38 commits.</p> <ul> <li><a href="https://urls.greenkeeper.io/semantic-release/semantic-release/commit/4053d8f7fbca0bd985f76b6638f19b48c295d623"><code>4053d8f</code></a> <code>fix: log plugin type in addition of path</code></li> <li><a href="https://urls.greenkeeper.io/semantic-release/semantic-release/commit/88f33ec482ea469a8cccc2275db4e2b6004c4692"><code>88f33ec</code></a> <code>chore(package): update mockserver-client to version 5.1.1</code></li> <li><a href="https://urls.greenkeeper.io/semantic-release/semantic-release/commit/0761ef378a10d65d02761497c7ff9f148af3c535"><code>0761ef3</code></a> <code>style: update to prettier@1.9.0</code></li> <li><a href="https://urls.greenkeeper.io/semantic-release/semantic-release/commit/f30fb6c8af2e08aeb1f95fb2ba9faae9d552c1d7"><code>f30fb6c</code></a> <code>chore(package): update prettier to version 1.9.0</code></li> <li><a href="https://urls.greenkeeper.io/semantic-release/semantic-release/commit/0113db2e069b7bc646a04fff8b06318da3cc3fd4"><code>0113db2</code></a> <code>docs(README): add node support policy</code></li> <li><a href="https://urls.greenkeeper.io/semantic-release/semantic-release/commit/eec4e68615c75963e06bac810b2845cc4dee02dd"><code>eec4e68</code></a> <code>test: Isolate environment variables passed to semantic-release</code></li> <li><a href="https://urls.greenkeeper.io/semantic-release/semantic-release/commit/8371a03da05a907707b31380adf8cf066d86fb66"><code>8371a03</code></a> <code>test: Verify <code>Error</code> instance type and SemanticReleaseError name</code></li> <li><a href="https://urls.greenkeeper.io/semantic-release/semantic-release/commit/2491032a994b6bd5d541091f704ca6b63b4457a0"><code>2491032</code></a> <code>test: Add test to check unexpected plugin return values</code></li> <li><a href="https://urls.greenkeeper.io/semantic-release/semantic-release/commit/02ddf34f2108540a6f0794246af6869ede7961e9"><code>02ddf34</code></a> <code>Fix: Remove redundant test of commitAnalyzer plugin output</code></li> <li><a href="https://urls.greenkeeper.io/semantic-release/semantic-release/commit/685959107b39d63feb8ab39e6f6c39dfe3a6470c"><code>6859591</code></a> <code>chore: Clean up mistakenly added configs</code></li> <li><a href="https://urls.greenkeeper.io/semantic-release/semantic-release/commit/613a646363aa6343379510fd4820a43e71c5034d"><code>613a646</code></a> <code>fix: Typo in error messages</code></li> <li><a href="https://urls.greenkeeper.io/semantic-release/semantic-release/commit/d7b323dd00d54687679d67506212266714114132"><code>d7b323d</code></a> <code>fix: Accept <code>undefined</code> values for the <code>getLastRelease</code> and <code>generateNotes</code> plugins</code></li> <li><a href="https://urls.greenkeeper.io/semantic-release/semantic-release/commit/a7359bffb6ca0be7202f491f55ce4e5eae5a9118"><code>a7359bf</code></a> <code>test: Improve docker start/stop script</code></li> <li><a href="https://urls.greenkeeper.io/semantic-release/semantic-release/commit/fcb832bbe193c196dbcbb42c7863bb9986dca1be"><code>fcb832b</code></a> <code>fix: remove <code>name</code> from log as it's not an existing option anymore</code></li> <li><a href="https://urls.greenkeeper.io/semantic-release/semantic-release/commit/89f5e07408aa92ef2053be92219b38a76ed1d20f"><code>89f5e07</code></a> <code>chore(package): update ava to version 0.24.0</code></li> </ul> <p>There are 38 commits in total.</p> <p>See the <a href="https://urls.greenkeeper.io/semantic-release/semantic-release/compare/16a02e523e36e83474ebe66884cb0a5403fda24e...4053d8f7fbca0bd985f76b6638f19b48c295d623">full diff</a></p> </details>

<details> <summary>FAQ and help</summary>

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper. </details>


Your Greenkeeper bot :palm_tree:

+2549 -16

93 comments

2 changed files

greenkeeper[bot]

pr closed time in 3 days

PR closed janl/node-jsonpointer

Add toString method to compiled pointer

Hi @janl

Wondering if you would consider this PR? It provides a 'toString' method to the returned compiled pointer, such that you can retrieve the original pointer 'path' string that was compiled. E.g.

var jsonpointer = require('jsonpointer');
var obj = { foo: 1, bar: { baz: 2}, qux: [3, 4, 5]};

var pointer = jsonpointer.compile('/bar/baz') ;
pointer.toString() ; // outputs '/bar/baz'
+5 -0

3 comments

2 changed files

damoclark

pr closed time in 3 days

pull request commentjanl/node-jsonpointer

Add toString method to compiled pointer

closing because of inactivity, please reopen when fixed

damoclark

comment created time in 3 days

pull request commentjanl/node-jsonpointer

Node10

fixed some other way, sorry for the clobber!

hildjj

comment created time in 3 days

PR closed janl/node-jsonpointer

Node10

As mentioned by Greenkeeper. Fixes #40

+2560 -2031

4 comments

3 changed files

hildjj

pr closed time in 3 days

issue closedjanl/node-jsonpointer

Does the typescript typings file work?

I just saw that in the files property in the package.json we only list the jsonpointer.js file but not the jsonpointer.d.ts file. Isn't that needed in the package to get typescript working? I'm not using typescript myself, so I have no idea how to verify that.

https://github.com/janl/node-jsonpointer/blob/master/package.json#L27-L30

closed time in 3 days

marcbachmann

push eventjanl/node-jsonpointer

Fabian Frank

commit sha 77aee499023bb56bbc2594fd8d80212bc94bd790

Include typings in npm distribution

view details

Jan Lehnardt

commit sha a4c6115649e305cb173a41f72a18c54af2230478

Merge pull request #43 from FabianFrank/fix-typings feat: Include typings in npm distribution

view details

push time in 3 days

PR merged janl/node-jsonpointer

Include typings in npm distribution

fixes #36

After this change you can see that npm includes the types:

$ npm pack
[...]
npm notice === Tarball Contents ===
npm notice 974B  package.json
npm notice 699B  jsonpointer.d.ts
npm notice 2.3kB jsonpointer.js
npm notice 1.2kB LICENSE.md
npm notice 1.3kB README.md
[...]

whereas before it wasn't.

+2 -1

2 comments

1 changed file

FabianFrank

pr closed time in 3 days

PR opened janl/node-jsonpointer

fix: prototype pollution

For curiousity’s sake, I checked if this has any significant performance impact and it does not.

Based on 10 runs before and after, all values in percent:

                         MED    AVG
get first level property 0.37	0.42
get second level property 0.40	0.61
get third level property 0.26	0.41
set first level property 2.25	2.16
set second level property 1.45	1.67
set third level property 2.05	1.98
push property into array -0.41	-0.51

2.25% slowdown as a worst case is not significant.

+674 -664

0 comment

5 changed files

pr created time in 3 days

push eventjanl/node-jsonpointer

Jan Lehnardt

commit sha 787e387373fc797102635ffc378410f52fa8051c

chore: remove GK lockfile and bump node versions in testing

view details

push time in 3 days

create barnchjanl/node-jsonpointer

branch : fix/proto

created branch time in 3 days

PR opened apache/couchdb

fix: set gen_server:call() timeout to infinity on ioq bypass

Before the bypass existed, ioq would call gen_server:call() on hehalf of it calling module with the queueing logic in between.

Commit e641a740 introduced a way to bypass any queues, but the delegated gen_server:call() there was added without a timeout parameter, leading to a default timeout of 5000ms.

A problem manifests here when operations that are sent through ioq that take longer than that 5000ms timeout. In practice, these operations should be very rare and this timeout should be a help on overloaded systems. However, one sure-fire way to cause an issue on an otherwise idle machine is raise the max_document_size and store unreasonably large documents, think 50MB+ of raw JSON).

Not that we recommend this, but folks have run this fine on 2.x before the ioq changes and it isn’t too hard to support here.

By adding an infinity timeout delegated gen_server:call() in the queue bypasse case, this no longer applies.

Thanks to Joan @woahli Touzet, Bob @rnewson Newson and Paul @davisp Davis for helping to track this down.

<!-- Thank you for your contribution!

 Please file this form by replacing the Markdown comments
 with your text. If a section needs no action - remove it.

 Also remember, that CouchDB uses the Review-Then-Commit (RTC) model
 of code collaboration. Positive feedback is represented +1 from committers
 and negative is a -1. The -1 also means veto, and needs to be addressed
 to proceed. Once there are no objections, the PR can be merged by a
 CouchDB committer.

 See: http://couchdb.apache.org/bylaws.html#decisions for more info. -->

Overview

<!-- Please give a short brief for the pull request, what problem it solves or how it makes things better. -->

Testing recommendations

<!-- Describe how we can test your changes. Does it provides any behaviour that the end users could notice? -->

Related Issues or Pull Requests

<!-- If your changes affects multiple components in different repositories please put links to those issues or pull requests here. -->

Checklist

  • [ ] Code is written and works correctly
  • [ ] Changes are covered by tests
  • [ ] Any new configurable parameters are documented in rel/overlay/etc/default.ini
  • [ ] A PR for documentation changes has been made in https://github.com/apache/couchdb-documentation
+1 -1

0 comment

1 changed file

pr created time in 4 days

PR opened apache/couchdb

fix: set gen_server:call() timeout to infinity on ioq bypass

Before the bypass existed, ioq would call gen_server:call() on hehalf of it calling module with the queueing logic in between.

Commit e641a740 introduced a way to bypass any queues, but the delegated gen_server:call() there was added without a timeout parameter, leading to a default timeout of 5000ms.

A problem manifests here when operations that are sent through ioq that take longer than that 5000ms timeout. In practice, these operations should be very rare and this timeout should be a help on overloaded systems. However, one sure-fire way to cause an issue on an otherwise idle machine is raise the max_document_size and store unreasonably large documents, think 50MB+ of raw JSON).

Not that we recommend this, but folks have run this fine on 2.x before the ioq changes and it isn’t too hard to support here.

By adding an infinity timeout delegated gen_server:call() in the queue bypasse case, this no longer applies.

Thanks to Joan @woahli Touzet, Bob @rnewson Newson and Paul @davisp Davis for helping to track this down.

+1 -1

0 comment

1 changed file

pr created time in 4 days

create barnchapache/couchdb

branch : fix/gen-server-timeout-on-ioq-bypass-3.x

created branch time in 4 days

create barnchapache/couchdb

branch : fix/gen-server-timeout-on-ioq-bypass

created branch time in 4 days

delete branch apache/couchdb-documentation

delete branch : ddocID

delete time in 4 days

push eventapache/couchdb-documentation

Jonathan Hall

commit sha 2bea1dc9d8d46202ee8205a146dddc720c3642c1

Key name correction in ddoc example

view details

Jan Lehnardt

commit sha a0711348d4883df9f8854673233484c0efd3cecf

Merge branch 'master' into ddocID

view details

Jan Lehnardt

commit sha db671d2873214620366dae06b0552fcedc686067

Merge pull request #565 from apache/ddocID Key name correction in ddoc example

view details

push time in 4 days

PR merged apache/couchdb-documentation

Key name correction in ddoc example

A simple mistake in the key name in a ddoc example.

+1 -1

0 comment

1 changed file

flimzy

pr closed time in 4 days

push eventapache/couchdb-documentation

Vincentas Vienozinskis

commit sha 18e64512b386a537ba85a0787ad3e48678080cf5

How to increase connection limit

view details

Vincentas Vienozinskis

commit sha e367e8f6d8d8858dc7a78462b95e298709d61e18

Format link

view details

Vincentas Vienozinskis

commit sha 046c74e988a7f629e2d524e6bc5481b52cff805f

Format link

view details

Vincentas Vienozinskis

commit sha 388a9eb74c67e8bbff542380256aaf9fca4ea852

Format link

view details

Vincentas Vienozinskis

commit sha 4c58158b33125afbf7c7bc430a3f9f15966a0a39

Fixed grammar

view details

Jonathan Hall

commit sha 35f17738a25f3d655ced0244deb0412cd118cd4c

Merge branch 'master' into master

view details

Bessenyei Balázs Donát

commit sha 95a73b2b58b56317f53f16ccf23bd305bdfb7233

Remove unnecessary items from the PR checklist (#519) * Remove unnecessary items from the PR checklist Co-authored-by: Joan Touzet <wohali@users.noreply.github.com>

view details

natcohen

commit sha 92158c15a4a4e77d0d38d3003b260ac0d30939f7

Added setup of admin for Redhat/CentOS (#502) Co-authored-by: Joan Touzet <wohali@users.noreply.github.com>

view details

Joan Touzet

commit sha b3459e9fa3ee16c14e2f38765a57fb9bfb99a9f4

New smoosh defaults for 3.0.1 (#509)

view details

Robert Newson

commit sha 7ba6e113fb9a5345fc2148306a35c1e89e3254d0

JWT documentation

view details

Robert Newson

commit sha cac108d710544fa5f932f9556695f305cf432ca2

Update src/api/server/authn.rst Co-Authored-By: Jonathan Hall <flimzy@flimzy.com>

view details

Robert Newson

commit sha f034719ced47ebc8827ede11a6706d4a92bb730e

Apply suggestions from code review excellent stuff, thanks. Co-Authored-By: Jonathan Hall <flimzy@flimzy.com>

view details

Robert Newson

commit sha 5e701a42b8197cb5c30357e708d9aedd5920fca1

address review comments

view details

Robert Newson

commit sha 37bf7c96de78b3834885d46851a849a0fef8f9c4

address review comments

view details

Robert Newson

commit sha fc14fa631993befdf0039b996c93329a6baadced

address review comments

view details

Robert Newson

commit sha 0c1daf73d815a941809b3abb21e4a77c196a0b6b

address review comments

view details

Joan Touzet

commit sha e65a1e4afd945bd51c0a6c2f6e969da3c3e698b4

Fix line-too-long lint error

view details

Robert Newson

commit sha 382d3ab3eb573d4b9cdc5e1b9c9ecae09a980c61

line wrap

view details

Robert Newson

commit sha e35ebafa2ee04a332fc0ab99d768c5029c88b146

fix xref

view details

Joan Touzet

commit sha 77f5b61fc6a5aa06766a5342eb035106638ea526

Add 3.0.1 release notes (#526)

view details

push time in 4 days

issue commentneighbourhoodie/couch-continuum

SyntaxError: Unexpected token Issue

great, I’ll leave this open so we can tighten up the required versions

nvsajeeva

comment created time in 4 days

issue commentneighbourhoodie/couch-continuum

SyntaxError: Unexpected token Issue

I think you need at least 8, 4 is very very old.

nvsajeeva

comment created time in 4 days

issue commentneighbourhoodie/couch-continuum

SyntaxError: Unexpected token Issue

which nodes version is this

nvsajeeva

comment created time in 4 days

issue commentapache/couchdb

Per-document access control

@mehrdad-shokri absolutely no schedule, but we’re open for sponsorships for this feature to move it along faster.

wohali

comment created time in 4 days

issue commentapache/couchdb

parse_revid - Badarg error in HTTP request

I’m in favour of allowing external revs, and I’d be okay with documenting clearly that 32-byte-non-int revs are an obtuse edge-case that we’re not changing, so implementers will have to do some trickery to work around that.

In addition, whatever 4.0 limitations exist, those need documenting then too.

ronag

comment created time in 10 days

issue commentneighbourhoodie/couch-continuum

Migrate-all requires source parameter

same here cc @garbados

shammond42

comment created time in 10 days

issue commentapache/couchdb

TLS client: In state cipher received SERVER ALERT: Fatal - Unknown CA error enabling x509 cert auth for replcation

I marked it “help” — we still need to determine if it is a bug

raulmartinezr

comment created time in 11 days

issue closedapache/couchdb

TLS client: In state cipher received SERVER ALERT: Fatal - Unknown CA error enabling x509 cert auth for replcation

Description

I try to configure client certificate authentication in the following scenario with couchDB 3.1.0

"Server" -> CouchDB (single-node) "Client" -> CouchDB (single-node) where I configure bidirecctional replication, to and from server Couch DB (push+pull)

But it's failing. Messages found in logs....

Client couchdb instance (the side which manages replication)

 TLS client: In state cipher received SERVER ALERT: Fatal - Unknown CA

Server couchdb instance

 TLS server: In state certify received CLIENT ALERT: Fatal - Handshake Failure

Steps to Reproduce

  • Configure client and server couchDB instances as described in environment
  • Configure replication in client instance (bidirecctional, push and pull)
  • Replication fails

Expected Behaviour

Replication should work. I tested connectivity with curl and openssl with the same setup, and both are working

 sudo curl --url https://192.168.1.66:6984/database/  \
--key /opt/couchdb/etc/ssl/node-71.client.key.pem \
--cert /opt/couchdb/etc/ssl/node-71.client.cert.pem \
 --cacert /opt/couchdb/etc/ssl/ca-chain.cert.pem --insecure
{"error":"unauthorized","reason":"You are not authorized to access this db."}
sudo openssl s_client  -connect 192.168.1.66:6984 \
-key /opt/couchdb/etc/ssl/node-71.client.key.pem \
-cert /opt/couchdb/etc/ssl/node-71.client.cert.pem \
-CAfile /opt/couchdb/etc/ssl/ca-chain.cert.pem
CONNECTED(00000005)

Your Environment

Client

  [ssl]
  enable = true
  cert_file = /opt/couchdb/etc/ssl/node-71.server.cert.pem
  key_file = /opt/couchdb/etc/ssl/node-71.server.key.pem
  verify_ssl_certificates = true
  fail_if_no_peer_cert = false
  cacert_file = /opt/couchdb/etc/ssl/ca-chain.cert.pem
  [replicator]
  cert_file = /opt/couchdb/etc/ssl/node-71.client.cert.pem
  key_file = /opt/couchdb/etc/ssl/node-71.client.key.pem
  ;# Avoid hostanme check failed
  verify_ssl_certificates = false
  ssl_trusted_certificates_file = /opt/couchdb/etc/ssl/ca-chain.cert.pem
  ssl_certificate_max_depth = 5

Server

 [ssl]
 enable = true
 cert_file = /opt/couchdb/etc/ssl/node-66.server.cert.pem
 key_file = /opt/couchdb/etc/ssl/node-66.server.key.pem
 verify_ssl_certificates = true
 fail_if_no_peer_cert = true
 cacert_file = /opt/couchdb/etc/ssl/ca-chain.cert.pem
 [replicator]
  cert_file = /opt/couchdb/etc/ssl/node-66.client.cert.pem
  key_file = /opt/couchdb/etc/ssl/node-66.client.key.pem
  verify_ssl_certificates = false
  ssl_trusted_certificates_file = /opt/couchdb/etc/ssl/ca-chain.cert.pem
  • CouchDB version used: 3.1.0
  • Browser name and version:
  • Operating system and version: Ubuntu 18.04

Additional Context

closed time in 11 days

raulmartinezr

issue commentapache/couchdb

TLS client: In state cipher received SERVER ALERT: Fatal - Unknown CA error enabling x509 cert auth for replcation

duplicate of https://github.com/apache/couchdb/discussions/2964

raulmartinezr

comment created time in 11 days

issue commentapache/couchdb

Sporadic errors on /_all_docs with Cookie auth and system databases

@skeyby just checking, does this cause any noticeable issues for your application (✌️) or is this more inconvenient log noise (which we should still investigate of course, just trying to get a sense of urgency here)

flimzy

comment created time in 11 days

issue closedapache/couchdb

TLS client: In state cipher received SERVER ALERT: Fatal - Unknown CA error enabling x509 cert auth for replcation

Hi,

I try to configure client certificate authentication in the following scenario with couchDB 3.1.0

  • Server CouchDB
  • Client CouchDB where I configure bidirecctional replication, to and from server Couch DB (push+pull)

However, when everything seems to be well configured I see the following errors

Client side

   TLS client: In state cipher received SERVER ALERT: Fatal - Unknown CA

Server Side

    TLS server: In state certify received CLIENT ALERT: Fatal - Handshake Failure

It seems client does not trust server CA, but it should do. I reproduced the same connecttion with openssl and curl, and it's working in both cases

 sudo curl --url https://192.168.1.66:6984/database/  \
--key /opt/couchdb/etc/ssl/node-71.client.key.pem \
--cert /opt/couchdb/etc/ssl/node-71.client.cert.pem \
 --cacert /opt/couchdb/etc/ssl/ca-chain.cert.pem --insecure
{"error":"unauthorized","reason":"You are not authorized to access this db."}

sudo openssl s_client  -connect 192.168.1.66:6984 \
-key /opt/couchdb/etc/ssl/node-71.client.key.pem \
-cert /opt/couchdb/etc/ssl/node-71.client.cert.pem \
-CAfile /opt/couchdb/etc/ssl/ca-chain.cert.pem
CONNECTED(00000005)
....

Below relevant configuration in both sides, client and server Remark: all certificates are signed by same intermediate CA (all have the same validation path) and both, root and intermediate CAs are included in /opt/couchdb/etc/ssl/ca-chain.cert.pem

Client

      [ssl]
      enable = true
      cert_file = /opt/couchdb/etc/ssl/node-71.server.cert.pem
      key_file = /opt/couchdb/etc/ssl/node-71.server.key.pem
      verify_ssl_certificates = true
      fail_if_no_peer_cert = false
      cacert_file = /opt/couchdb/etc/ssl/ca-chain.cert.pem
      [replicator]
      cert_file = /opt/couchdb/etc/ssl/node-71.client.cert.pem
      key_file = /opt/couchdb/etc/ssl/node-71.client.key.pem
      ;# Avoid hostanme check failed
      verify_ssl_certificates = false
      ssl_trusted_certificates_file = /opt/couchdb/etc/ssl/ca-chain.cert.pem
      ssl_certificate_max_depth = 5

Server

     [ssl]
     enable = true
     cert_file = /opt/couchdb/etc/ssl/node-66.server.cert.pem
     key_file = /opt/couchdb/etc/ssl/node-66.server.key.pem
     verify_ssl_certificates = true
     fail_if_no_peer_cert = true
     cacert_file = /opt/couchdb/etc/ssl/ca-chain.cert.pem
     [replicator]
      cert_file = /opt/couchdb/etc/ssl/node-66.client.cert.pem
      key_file = /opt/couchdb/etc/ssl/node-66.client.key.pem
      verify_ssl_certificates = false
      ssl_trusted_certificates_file = /opt/couchdb/etc/ssl/ca-chain.cert.pem

closed time in 12 days

raulmartinezr

pull request commentapache/couchdb-www

remove slack.js and use slack join link

Nice!

garrensmith

comment created time in 14 days

delete branch apache/couchdb-www

delete branch : add-slack-join-link

delete time in 14 days

delete branch apache/couchdb

delete branch : fix/csp

delete time in 18 days

push eventapache/couchdb

Jan Lehnardt

commit sha 34baa46002a4ede723961a7d768eb25977965157

fix: send CSP header to make Fauxotn work fully Co-authored-by: Robert Newson <rnewson@apache.org>

view details

push time in 18 days

PR merged apache/couchdb

fix: send CSP header to make Fauxotn work fully
+91 -2

0 comment

3 changed files

janl

pr closed time in 18 days

push eventapache/couchdb

Jan Lehnardt

commit sha 495ea19b30e456a308031b6baaa5a172d64151c0

fix: send CSP header to make Fauxotn work fully Co-authored-by: Robert Newson <rnewson@apache.org>

view details

push time in 18 days

PR opened apache/couchdb

fix: send CSP header to make Fauxotn work fully
+1 -1

0 comment

1 changed file

pr created time in 18 days

create barnchapache/couchdb

branch : fix/csp

created branch time in 18 days

pull request commentapache/couchdb

In replicator, when rescheduling, pick only pending jobs which are not running

quick note that this is Apache CouchDB not Cloudant :)

nickva

comment created time in 19 days

issue commentapache/couchdb

Per-document access control

one thing at a time, the plan for now is do just one owner per doc in 3.x and get that out to people. Then we need to rebuild this for the 4.x architecture after which we can think about expanding what can go in _access:[]. I’ve determined that doing groups in 3.x is too hard, but I’m a little more hopeful in 4.x. But again: one thing at a time.

wohali

comment created time in 23 days

PR opened apache/couchdb

WIP: per doc access

wip, nothing to see here, just pushing so I can get a CI run

+5191 -143

0 comment

45 changed files

pr created time in 24 days

create barnchapache/couchdb

branch : feat/access-3.x

created branch time in 24 days

more