-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TLS certification failed #25
Comments
I'm having the same problem. I managed to fix it (temporarily) by changing the def handle_response(self, conn, response):
self.logger.debug('[%s] response: %s', conn, response)
if response == nsq.OK:
result = self._response_queues[conn].popleft()
result.set(response)
self.on_response.send(self, response=response) To this: def handle_response(self, conn, response):
self.logger.debug('[%s] response: %s', conn, response)
if response == nsq.OK:
if conn in self._response_queues:
result = self._response_queues[conn].popleft()
result.set(response)
self.on_response.send(self, response=response) |
herberthamaral
added a commit
to herberthamaral/gnsq
that referenced
this issue
Sep 5, 2019
herberthamaral
added a commit
to herberthamaral/gnsq
that referenced
this issue
Sep 5, 2019
bgeisberger
pushed a commit
to bgeisberger/gnsq
that referenced
this issue
Nov 12, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When I use the TLS cerification of gnsq, the code raised a exception.
The Traceback of the exception is
It seems that the self._response_queues of conn is missing, because the value of self._response_queues is {} when running at the last exception code.
The NSQD(v1.1.0) is run by the following command:
where, the certs folder is generated by the official command of nsq.
The Python code to connect to the nsqd is shown as following:
The text was updated successfully, but these errors were encountered: