Namespaces changed between 2.4.0 and 2.5.0
See original GitHub issueI reported this in the webjobs sdk repo (https://github.com/Azure/azure-webjobs-sdk/issues/1619), but I wanted to bring it up here too. Between versions 2.4.0 and 2.5.0 the SamplingPercentageEstimatorSettings
class, which the webjobs AI logger uses, moved to a new namespace (I’m sure there’s many other classes that did as well).
Because of this change if you try to use version 2.1.0 of the webjobs sdk with AI 2.5.0+ it’ll compile, but crash when the AI logger starts up.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:6
- Comments:35 (19 by maintainers)
Top Results From Across the Web
Namespaces changed between 2.4.0 and 2.5.0 · Issue #727
Between versions 2.4.0 and 2.5.0 the SamplingPercentageEstimatorSettings class, which the webjobs AI logger uses, moved to a new namespace (I'm ...
Read more >Re-grant RBAC privileges to namespaces
OLM-based installations (OperatorHub.io and RedHat OpenShift) have a known issue with upgrading from version 2.4.0 to 2.5.0. This upgrade scenario revokes ...
Read more >Ubiquiti Unifi Binding Feature Discussion
There may be issues when using 2.5.0 add-ons on 2.4.0 because the XML namespaces changed from ESH to OH. See: Manual Daikin Binding...
Read more >Updating from earlier versions - MRTK 2
The instructions below describe the 2.4.0 to 2.5.0 upgrade path. ... The namespace of WindowsMixedRealityUtilities changed from Microsoft.
Read more >Migration Archive - Apache XML
The following lists the public API changes between the Xerces-C++ 2.4.0; and the Xerces-C++ 2.5.0 releases of the parser.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@xt0rted We’re going to take ownership and fix it on our end. We’re planning to release 2.6.0 in the first half of May so this makes sense to fix with that.
Just tested all of my webjobs and there were no issues, so it’s going out to production now.