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 was playing with your demo code, all just fine. Then I noticed that calling a publish shortly after a subscribe seems to prevent a publish from within the subscribe callback from being run.
In your demo, the subscribe command triggers the subscribe callback which then runs code that publishes "abcde" to the test channel. When I add a publish line:
the "abcde" as well as the debug messages from the subscribe callback never get run.
However, when I send messages to the subscribed channel, the data comes in and gets processed like it should. So it looks like it's subscribed properly, but the feedback (pub and log messages) just don't work.
I would start to dig into the timings of all this, but I think that you are much more familiar with the code at this point. :)
The text was updated successfully, but these errors were encountered:
The reason is sending thread write multiple message in the same time, and receiving thread only know last message (with msg_pending_id and msg_pending_type). I'm thinking simple way.
Hiya Tuan,
Awesome work!
I was playing with your demo code, all just fine. Then I noticed that calling a publish shortly after a subscribe seems to prevent a publish from within the subscribe callback from being run.
In your demo, the subscribe command triggers the subscribe callback which then runs code that publishes "abcde" to the test channel. When I add a publish line:
the "abcde" as well as the debug messages from the subscribe callback never get run.
However, when I send messages to the subscribed channel, the data comes in and gets processed like it should. So it looks like it's subscribed properly, but the feedback (pub and log messages) just don't work.
I would start to dig into the timings of all this, but I think that you are much more familiar with the code at this point. :)
The text was updated successfully, but these errors were encountered: