Closed evedon closed 3 years ago
@evedon thank you for raising this issue.Please take a look at the following comments:
We cannot automatically identify a release based on the version of Mbed OS that you have provided. Please provide either a single valid sha of the form #abcde12 or #3b8265d70af32261311a06e423ca33434d8d80de or a single valid release tag of the form mbed-os-x.y.z . E.g. 'mbed-os-6.3.0,' has not been matched as a valid tag or sha. NOTE: If there are fields which are not applicable then please just add 'n/a' or 'None'.This indicates to us that at least all the fields have been considered. Please update the issue header with the missing information, the issue will not be mirroredto our internal defect tracking system or investigated until this has been fully resolved.
@evedon it has been 5 days since the last reminder. Could you please update the issue header as previously requested?
Please provide either a single valid sha of the form #abcde12 or #3b8265d70af32261311a06e423ca33434d8d80de or a single valid release tag of the form mbed-os-x.y.z . E.g. 'mbed-os-6.3.0,' has not been matched as a valid tag or sha.
@adbridge It seems the script didn't re-parse the version after the PR description was fixed?
@evedon it has been 5 days since the last reminder. Could you please update the issue header as previously requested?
@evedon it has been 5 days since the last reminder. Could you please update the issue header as previously requested?
Thank you for raising this detailed GitHub issue. I am now notifying our internal issue triagers. Internal Jira reference: https://jira.arm.com/browse/IOTOSM-2951
Closing this one as we have switched to the new AWS client
Description of defect
There is a race condition on closing the MQTT connection which causes the peer to close the connection first and triggers error handling in MQTT library and error messages in mbedTLS:
This race condition manifests itself when using a low baud rate (9600).
This does not prevent the example to successfully run through completion.
Target(s) affected by this defect ?
Tested on DISCO_L475VG_IOT01A
Toolchain(s) (name and version) displaying this defect ?
Tested with GCC_ARM
What version of Mbed-os are you using (tag or sha) ?
mbed-os-6.3.0
What version(s) of tools are you using. List all that apply (E.g. mbed-cli)
N/A
How is this defect reproduced ?
Run the example at 9600 baud rate