You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ponymail.apache.org by sebbASF <gi...@git.apache.org> on 2016/10/15 10:41:42 UTC
[GitHub] incubator-ponymail issue #184: Bug: setup.py does not handle connection fail...
GitHub user sebbASF opened an issue:
https://github.com/apache/incubator-ponymail/issues/184
Bug: setup.py does not handle connection failure well
If setup.py cannot contact the elastic server, it reports multiple errors.
It should give up on the first failure.
----
----
---
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] incubator-ponymail issue #184: Bug: setup.py does not handle connection fail...
Posted by sebbASF <gi...@git.apache.org>.
Github user sebbASF commented on the issue:
https://github.com/apache/incubator-ponymail/issues/184
Oops - it looks like the multiple failure reports are caused by the urllib3 connection retry code.
However setup.py could/should intercept the failure and provide a concise error message indicating failure to connect.
At present the error output is nearly 300 lines of text.
---
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] incubator-ponymail issue #184: Bug: setup.py does not handle connection fail...
Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the issue at:
https://github.com/apache/incubator-ponymail/issues/184
---
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.
---