-
Notifications
You must be signed in to change notification settings - Fork 158
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
Fixes for non-blocking with larger payload and improvements to the test and examples #373
Conversation
…e middle of variable would not correctly process for large messages.
…e override of `MAX_BUFFER_SIZE` in examples.
5518e4a
to
97cb820
Compare
FYI: I can reproduce the error locally. Getting a disconnected due to protocol error from broker, which for some reason leaves the local broker instance running still:
Will investigate on Friday. |
…f the non-blocking is allowed.
Tests with TLS and non-block are failing due to this bug -> wolfSSL/wolfssl#7001 |
…gine requires an SSL_Write that returns WANT_WRITE to be called with the same buffer/sz, not a different one, even if no data was sent. If user wants to enable the feature anyways they can use `WOLFMQTT_ALLOW_NODATA_UNLOCK`. Only the write that has this logic as the issue doesn't exist for an SSL_Read.
…hile data has partially been written.
…r trying to send multiple publishes in the same thread.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Update - needed to update wolfSSL first!
-----Ignore----
Seeing failures with
./configure --enable-mt --enable-nonblock CFLAGS="-DWOLFMQTT_TEST_NONBLOCK"
ASS: scripts/client.test
FAIL: scripts/multithread.test
PASS: scripts/firmware.test
PASS: scripts/awsiot.test
FAIL: scripts/nbclient.test
PASS: scripts/azureiothub.test
Customer is fully happy. No outstanding issues. This PR is ready for merge. |
-f [file]
option with examples.MAX_BUFFER_SIZE
in examples.ZD 16769