Skip to content

Conversation

@lewing
Copy link
Contributor

@lewing lewing commented Mar 25, 2025

Pull Request Template

Second fix for #5029

Description

This adds an additional guard in the other (previously missed) location where service point is used

Type of change

Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)
  • [] New feature (non-breaking change which adds functionality)
  • [] Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • [] This change requires a documentation update

Closing issues

To automatically close an issue: closes #5029

@lewing lewing changed the title guard the servicpoint call here too Guard the servicepoint call in DocumentClass with ServicePointAccessor.IsSupported as well Mar 25, 2025
@lewing lewing changed the title Guard the servicepoint call in DocumentClass with ServicePointAccessor.IsSupported as well Guard the ServicePointAccessor call in DocumentClass with ServicePointAccessor.IsSupported as well Mar 25, 2025
@lewing lewing changed the title Guard the ServicePointAccessor call in DocumentClass with ServicePointAccessor.IsSupported as well Guard the ServicePointAccessor call in DocumentClass with IsSupported as well Mar 25, 2025
@kirankumarkolli
Copy link
Member

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@kirankumarkolli kirankumarkolli changed the title Guard the ServicePointAccessor call in DocumentClass with IsSupported as well ServicePointAccessor : Fixes Guard the ServicePointAccessor call in DocumentClass with IsSupported as well Mar 26, 2025
@kirankumarkolli kirankumarkolli changed the title ServicePointAccessor : Fixes Guard the ServicePointAccessor call in DocumentClass with IsSupported as well WebAssembly : Fixes Guard the ServicePointAccessor call in DocumentClass with IsSupported as well Mar 26, 2025
@kirankumarkolli
Copy link
Member

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

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.

Failing to create CosmosClient using Blazor WASM.

3 participants