SSL warnings #859
Comments
VakarisZ
added
the
Bug
|
Can't avoid that while using self signed certs. Without control over who's running the island, GC shouldn't sign a blanket cert. |
|
I agree with you, but maybe we can ignore/catch the warnings in order not to litter the log and not to confuse users. |
|
Ah, hmm. |
|
I'm having the same issue. I even tried with different environments - debian, vmware, docker. All the same. How can I use gevent to fix this? It's not clear |
|
@mxm0z You can't (unless you're running a dev version) but we will on the next release. Also, AFAIK this should not impact your usage of the tool, simply spams the logs. |
|
Still happens with gevent, let's try to catch it |
|
Since we switched to gevent, the error looks like: |
By default, gevent prints exceptions and tracebacks to stderr. This is
obnoxious as it results in large tracebacks intermixed with the output
that the logger prints to the console. This commit redirects this data
to {DATA_DIR}/gevent_exceptions.log. Unfortunately, this would mean that
the user might be left without any indication these exceptions had
occurred, unless they take the time to inspect the
gevent_exceptions.log. Therefore, when an excepion occurs, a message
with just the exception (not the traceback) is logged to WARNING.
Fixes #859
By default, gevent prints exceptions and tracebacks to stderr. This is
obnoxious as it results in large tracebacks intermixed with the output
that the logger prints to the console. This commit redirects this data
to {DATA_DIR}/gevent_exceptions.log. Unfortunately, this would mean that
the user might be left without any indication these exceptions had
occurred, unless they take the time to inspect the
gevent_exceptions.log. Therefore, when an excepion occurs, a message
with just the exception (not the traceback) is logged to WARNING.
Fixes #859
|
After spending some time with this, I don't think we should entirely suppress this warning. Since users can now provide their own certificates, this could be useful information for them. What we do need is to prevent the traceback from being displayed in the console output. PR #1298 proposes a solution. |
By default, gevent prints exceptions and tracebacks to stderr. This is
obnoxious as it results in large tracebacks intermixed with the output
that the logger prints to the console. This commit redirects this data
to {DATA_DIR}/gevent_exceptions.log. Unfortunately, this would mean that
the user might be left without any indication these exceptions had
occurred, unless they take the time to inspect the
gevent_exceptions.log. Therefore, when an excepion occurs, a message
with just the exception (not the traceback) is logged to WARNING.
Fixes #859
By default, gevent prints exceptions and tracebacks to stderr. This is
obnoxious as it results in large tracebacks intermixed with the output
that the logger prints to the console. This commit redirects this data
to {DATA_DIR}/gevent_exceptions.log. Unfortunately, this would mean that
the user might be left without any indication these exceptions had
occurred, unless they take the time to inspect the
gevent_exceptions.log. Therefore, when an excepion occurs, a message
with just the exception (not the traceback) is logged to WARNING.
Fixes #859
Describe the bug
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Should not be throwing warnings.
Tasks
References
https://stackoverflow.com/questions/66364650/catching-errors-being-thrown-within-module
The text was updated successfully, but these errors were encountered: