Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

[release/9.0] [SignalR] Don't throw for message headers in Java client#62783

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
wtgodbe merged 1 commit intorelease/9.0frombackport/pr-62739-to-release/9.0
Aug 6, 2025

Conversation

@github-actions
Copy link
Contributor

@github-actionsgithub-actionsbot commentedJul 17, 2025
edited by BrennanConroy
Loading

Backport of#62739 to release/9.0

/cc@BrennanConroy

[SignalR] Don't throw for message headers in Java client

Description

If a Java client connects to a SignalR server that is writing "headers" (SignalR protocol concept), then the connection will close with an error.

This happened when Azure SignalR Service (ASRS) added some distributed tracing information to messages and broke a bunch of customer apps. The change has since been reverted by ASRS, but we would like to fix the Java clients to allow this feature to be readded in the future.

Fixes#62713

Customer Impact

Customer client apps broken by server upgrade. Issue linked above shows many customers hit by this.

Regression?

  • Yes
  • No

Risk

  • High
  • Medium
  • Low

Unused code currently. In the future it may be used, and it's fairly simple code with a couple tests added for it.

Verification

  • Manual (required)
  • Automated

Packaging changes reviewed?

  • Yes
  • No
  • N/A

@dotnet-policy-servicedotnet-policy-servicebot added this to the9.0.x milestoneJul 17, 2025
@dotnet-policy-servicedotnet-policy-servicebot added the pending-ci-rerunWhen assigned to a PR indicates that the CI checks should be rerun labelJul 25, 2025
@BrennanConroyBrennanConroy added Servicing-considerShiproom approval is required for the issue Servicing-approvedShiproom has approved the issue and removed Servicing-considerShiproom approval is required for the issue labelsAug 4, 2025
@wtgodbewtgodbe removed the pending-ci-rerunWhen assigned to a PR indicates that the CI checks should be rerun labelAug 6, 2025
@wtgodbewtgodbe merged commit649cf21 intorelease/9.0Aug 6, 2025
23 of 25 checks passed
@wtgodbewtgodbe deleted the backport/pr-62739-to-release/9.0 branchAugust 6, 2025 16:13
@dotnet-policy-servicedotnet-policy-servicebot modified the milestones:9.0.x,9.0.9Aug 6, 2025
This was referencedSep 9, 2025
This was referencedNov 24, 2025
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

@wtgodbewtgodbewtgodbe approved these changes

@BrennanConroyBrennanConroyAwaiting requested review from BrennanConroyBrennanConroy is a code owner

@halter73halter73Awaiting requested review from halter73halter73 is a code owner

Assignees

No one assigned

Labels

Servicing-approvedShiproom has approved the issue

Projects

None yet

Milestone

9.0.9

Development

Successfully merging this pull request may close these issues.

3 participants

@wtgodbe@BrennanConroy

[8]ページ先頭

©2009-2025 Movatter.jp