-
Notifications
You must be signed in to change notification settings - Fork 258
[V1] New Release with updated submodules? #596
Comments
Hi @villepalo , We are working on that, however we don't have a date on when we are going to release V1 again. Let us know, We will let you know once we release, Angelo Ribeiro. |
I have tried to update submodules myself but for some reason iot-edge build system is not compatible with newer submodules:
|
Thanks for trying @villepalo , @darobs , Do you have an idea how he can fix it? |
I guess it's time to do the submodule dance. :) I'll see if I can get the LTS branch of the C SDK updated into a branch and push it. |
Any news on this issue? |
Thank you for the reminder. I got slowed down by some build issue and then got busy with V2 work. I put this back on my list. |
Hello everyone, I ran into some problems with the Jan, 2018 LTS build. I'm updating the submodules to current master in anticipation of the next LTS release, which should be soon. I did still have to make a PR against the c-shared submodules to allow a build. |
There is new lts_10_2018 (https://github.com/Azure/azure-iot-sdk-c/commits/lts_10_2018) branch in iot-sdk-c. Could we update submodules now? |
Using lst_10_2018 iot-sdk-c rebuilding deps fails:
Also running unit test fails
|
@darobs Any news on this? Is this new LTS going to be pulled into iot-edge-v1? |
Solved the problem by cherry-picking those memory leaks and segfault fixes to submodule forks and iot-edge fork. Now the system seems to work ok. |
Description of the issue:
Do you have any plans for the next V1 release? Current version is not usable at all if one uses AMQP or MQTT and internet connection is not stable enough. AMQP leaks memory (#409) and mqtt segfaults after connection break (#520 ) . Both of these bugs are fixed in the latest iot-sdk-c library.
The text was updated successfully, but these errors were encountered: