Skip to content
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

Distributed tracing update #1611

Merged
merged 210 commits into from
Jul 31, 2020
Merged

Conversation

ewertons
Copy link
Contributor

Checklist

  • I have read the [contribution guidelines] (https://github.com/Azure/azure-iot-sdk-c/blob/master/.github/CONTRIBUTING.md).
  • I added or modified the existing tests to cover the change (we do not allow our test coverage to go down).
  • If this is a modification that impacts the behavior of a public API
    • I edited the corresponding document in the devdoc folder and added or modified requirements.
  • I submitted this PR against the correct branch:
    • This pull-request is submitted against the master branch.
    • I have merged the latest master branch prior to submission and re-merged as needed after I took any feedback.
    • I have squashed my changes into one with a clear description of the change.

Reference/Link to the issue solved with this PR (if any)

Description of the problem

public-preview branch hasn't been updated for months, lacking critical fixes.

Description of the solution

massand and others added 30 commits September 23, 2019 16:49
release_2019_10_07_after_bump_version
Move longhaul timeoutInSeconds to correct place in yml, change to a snug 800-min limit
* Check correct timeout time

* Fix MQTT timeout issues

Fix regression introduced on overly aggressive MQTT timeouts.

To fix and cleanup code a bit:
* Remove concept of enqueue time and instead have a message creation time.
* Set this message creation time ALWAYS, regardless of whether it's a PUT or GET.
* Check this publish time on timeouts.
* Create a common function to create TWIN requests and cleanup some dup'd code.

On test side:
* Fix up UT's required of course
* Change the default timer that UT uses to start at 30 minutes, not 0 minutes.
  If we had done this it would've caught initial bug where a message creation time was never init'd but close enough to 0 to have tests pass.
…tforms

The longhaul tests on Windows have been cancelled by devops after 12h, because not all Windows LH tests run in parallel.
There are 10 tests, but on our scripts we restrict the max number of parallel tests to 8.
We could fix this in different ways, but this is the cheapest and most straightforward.
Also, on Linux we run up to 16 tests in parallel, so increasing by that much on Windows should be acceptable.
Fix the cancellation of the longhaul jobs in the gate for Windows platforms
Handle unexpected states in dev provisioning messagesender and messagereceiver state cb (issue #1254)
#1274)

* added a define that can be used as an option to reduce memory footprint on embedded devices Note: esp8266 may run out of memory without this define.

Add in #defines for loading only specific certs.

* Update linux_c_option_test.sh
Added option to test build with -Duse_baltimore_cert=ON

* Update certs.c
Update to certificate descriptions.

Name conventions set.

* Update CMakeLists.txt
pass cert defines down to compiler
Remove incorrect const qualifier in serializer methodreturn
Updating references from Device Explorer to Azure IoT Explorer and some minor documentation changes.
… treated (gh#1309)

Explicitly explain how the memory used by IOTHUB_MESSAGE_HANDLE is copied by the *_SendEventAsync function,
allowing the calling application to destroy the message argument right after the *_SendEventAsync function returns.
Improve *SendEventAsync documentation about how the message handle is treated (gh#1309)
ttins and others added 21 commits June 30, 2020 17:03
RIoT Update to utilize new Crypto lib
IoTHub has changed the convention for indicating a device's ModelId.

Instead of passing `digital-twin-model-id`, we now pass `model-id`.

This succeeds on latest canary deployments.
Implement a simple PnP thermometer sample that implements the interface defined [here](https://github.com/Azure/opendigitaltwins-dtdl/blob/master/DTDL/v2/samples/Thermostat.json).
* sendPendingGetTwinRequests only after the suback is received

* Update unit tests for fix on MQTT transport/sendPendingGetTwinRequests

Co-authored-by: Ewerton Scaboro da Silva <ewertons@microsoft.com>
* Add TemperatureController model for a more complex PnP sample.
* Expand the common library specifically with PnP parsing helpers.
* Fix up fit and finish issues in the already checked in simple thermostat, so it's a bit more inline stylistically with rest of files under `./samples/pnp`.
* Update arduino-esp.yml for Azure Pipelines

* Update esp_arduino_uart_interface.py

* Update serial_connect.py

* Delete mxchip_settings.py

* try save env variable

* ok ok ok

* Update azure_test_firmware_errors.py
release_2020_07_19_after_bump_version
Update Long Term Support information
Fix format string passed to strftime to use desired format. Matches what was already in the more complex component sample and embedded C samples.
Fix incorrect handle name in telemetry sample (#1599)
Adds DPS support to PnP temperature controller sample.
Naming functions and file name with `helper` wasn't particularly helpful.  Cleaning up.
Further cleanup of PNP samples, most importantly returning an empty JSON blob on commands (hub/explorer aren't happy otherwise the way C SDK works).
@ericwolz ericwolz merged commit 2ba7e79 into distributed_tracing Jul 31, 2020
@ewertons ewertons deleted the distributed_tracing-update branch December 16, 2020 21:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.