You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@couchdb.apache.org by rnewson <gi...@git.apache.org> on 2016/07/12 12:25:43 UTC
[GitHub] couchdb-chttpd pull request #132: 3054 invalidate promptly 2
GitHub user rnewson opened a pull request:
https://github.com/apache/couchdb-chttpd/pull/132
3054 invalidate promptly 2
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/cloudant/couchdb-chttpd 3054-invalidate-promptly-2
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/couchdb-chttpd/pull/132.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #132
----
commit fc7287a9eddca2f1d114853bc555b07c0a6ea3f8
Author: Robert Newson <rn...@apache.org>
Date: 2016-07-12T09:21:24Z
Don't end changes feed listener on heartbeat
There's no need to end and restart the changes feed listener on every
heartbeat, so don't do that.
COUCHDB-3054
commit 5e3bf1f5e2e96841ce0d2b26606c7f590c067bdc
Author: Robert Newson <rn...@apache.org>
Date: 2016-07-12T12:23:05Z
Tolerate failure of ensure_auth_ddoc_exists call
ensure_auth_ddoc_exists can crash if _users db does not exist, so move
it to the spawned listen_for_changes process where we already tolerate
the possibility of a crash (and have logic to restart after 5 seconds)
COUCHDB-3054
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] couchdb-chttpd pull request #132: 3054 invalidate promptly 2
Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:
https://github.com/apache/couchdb-chttpd/pull/132
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---