Euripedes
Euripedes
@AlexMihai1804 could you provide the logs for the crash and a decoded backtrace, so I can try to identify the issue? Even better if you can provide a reproducer.
@AlexMihai1804 I'm closing this one, feel free to reopen, adding the reproducer.
@AlexMihai1804 could you provide a reproducer? I would suggest you to take the SSL example and change the certificate used to verify that your certificate format is correct.
Closing. Feel free to reopen with added information.
Hi, @tajnymag this is the expected behavior. When the received message is bigger than the buffer multiple data events are dispatched to deliver the message and the user is responsible...
Hi @tajnymag, you are correct that only the first event contains the topic, all the subsequent events are dispatched immediately, so should be dispatched to the same handler. We are...
Hi @michaelboeding could you point the scenario where you are getting the memory leak? Please share some reproducer and the configuration used for the MQTT client.
@michaelboeding could you add the code for your `checkHeapSize` and `getOutboxSize` functions? In the `publish` we'll have a copy to the outbox and wait for the broker `PUBACK` control message...
Hi @bryghtlabs-richard thanks for the request. You are right, we need to set it in the transport level. We are already introducing the possibility to tcp_transport and will made it...
@bryghtlabs-richard the approach we went here was to "open" the transport layer, giving user access to the socket. So you can get the socket and apply the settings there. I...