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/09/27 23:01:13 UTC
[GitHub] couchdb-chttpd pull request #142: Fix eventsource timeout handling
GitHub user rnewson opened a pull request:
https://github.com/apache/couchdb-chttpd/pull/142
Fix eventsource timeout handling
COUCHDB-3164
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/cloudant/couchdb-chttpd 3164-eventsource-timeout
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/couchdb-chttpd/pull/142.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 #142
----
commit 297493f29978d6effd9ae865b5822f54261c6955
Author: Robert Newson <rn...@apache.org>
Date: 2016-09-27T22:44:54Z
Fix eventsource timeout handling
COUCHDB-3164
----
---
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 #142: Fix eventsource timeout handling
Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:
https://github.com/apache/couchdb-chttpd/pull/142
---
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 issue #142: Fix eventsource timeout handling
Posted by abhishiv <gi...@git.apache.org>.
Github user abhishiv commented on the issue:
https://github.com/apache/couchdb-chttpd/pull/142
Just hit this bug.
On jira i see this path is scheduled for 2.1.0. Any chances to slip this in with the next 2.0.0-rc?
---
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.
---