Skip to content

WebAssembly : Fixes Guard the ServicePointAccessor call in DocumentClass with IsSupported as well #5089

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 2 commits into from
Mar 26, 2025
Merged

WebAssembly : Fixes Guard the ServicePointAccessor call in DocumentClass with IsSupported as well #5089

merged 2 commits into from
Mar 26, 2025

Conversation

lewing
Copy link
Contributor

@lewing lewing commented Mar 25, 2025 •
edited
Loading

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 mentioned this pull request Mar 25, 2025
Closed
@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 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 Azure Pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@kirankumarkolli kirankumarkolli merged commit 01042b1 into Azure:master Mar 26, 2025
23 of 26 checks passed
@lewing lewing deleted the guard-other-servicepoint branch March 27, 2025 15:42
This was referenced Jul 28, 2025
Closed
Closed
Closed
This was referenced Aug 4, 2025
Open
Open
Open
Open
@dependabot dependabot bot mentioned this pull request Aug 11, 2025
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@Pilchie Pilchie Pilchie approved these changes

@kirankumarkolli kirankumarkolli kirankumarkolli approved these changes

@FabianMeiswinkel FabianMeiswinkel Awaiting requested review from FabianMeiswinkel FabianMeiswinkel is a code owner

@sboshra sboshra Awaiting requested review from sboshra sboshra is a code owner

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Failing to create CosmosClient using Blazor WASM.
3 participants
@lewing @kirankumarkolli @Pilchie