Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Update dependency to fix OOM bug (#6689)
Fixes #6630. DotNetty has an OOM bug that is fixed in v0.7.5. Two components in Edge Hub have a transitive dependency on DotNetty: * Microsoft.Azure.Devices.Edge.Hub.Core via Microsoft.Azure.Devices.Client * Microsoft.Azure.Devices.Edge.Hub.Mqtt via Microsoft.Azure.Devices.ProtocolGateway.Core. The best approach is for our dependencies to update their reference to DotNetty, then we update our dependencies. In the meantime, we'll make explicit references to override the transitive versions. I used `dotnet list package --include-transitive` before and after the change to verify that the transitive dependency is replaced by the explicit dependency in the two updated projects, and that transitive packages are at 0.7.5 throughout the rest of Edge Hub. It would work to _only_ add explicit references in Microsoft.Azure.Devices.Edge.Hub.Core since Microsoft.Azure.Devices.Edge.Hub.Mqtt depends on Core but adding explicit references at the site of each dependency should help avoid surprises. Changes to Edge Hub connectivity can have far-reaching impacts, so I'm running end-to-end, nested end-to-end, connectivity, and long-haul pipelines to test this change. ## Azure IoT Edge PR checklist:
- Loading branch information