You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have some code that successfully subscribes to an MQTT broker, and that logs messages to the screen, using as:start-event-loop.
But since this takes over everything, I wanted to run the event loop in a secondary thread. I put the call to as:start-event-loop into a call to bordeaux-threads:make-thread. But now, when I try to run that code, I get a constant stream of warning messages like this:
and no logging messages are ever printed. My understanding is that it should be possible to run the cl-async event loop in a thread. I don't understand what it is about an MQTT client that would make running in a thread different from running in the main process. It seems that somehow a timeout is being triggered, but the client code does not set a timeout anywhere.
The text was updated successfully, but these errors were encountered:
I have some code that successfully subscribes to an MQTT broker, and that logs messages to the screen, using
as:start-event-loop
.But since this takes over everything, I wanted to run the event loop in a secondary thread. I put the call to
as:start-event-loop
into a call tobordeaux-threads:make-thread
. But now, when I try to run that code, I get a constant stream of warning messages like this:and no logging messages are ever printed. My understanding is that it should be possible to run the
cl-async
event loop in a thread. I don't understand what it is about an MQTT client that would make running in a thread different from running in the main process. It seems that somehow a timeout is being triggered, but the client code does not set a timeout anywhere.The text was updated successfully, but these errors were encountered: