Skip to content

[Backport] Add CancelInvocation support to MsgPack in TS client #7404

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 our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Feb 14, 2019

Conversation

BrennanConroy
Copy link
Member

@BrennanConroy BrennanConroy commented Feb 8, 2019

Backport of #7224
Issue #7157

Description

The @aspnet/signalr-protocols-msgpack addition to the Javascript client would throw when sending a new message that was added to the SignalR protocol in the 2.2 release. This change adds the serializing for that new message so it no longer throws for correct behavior.

Customer Impact

Customers will no longer get exceptions for using this correct behavior.

Regression?

None, this is a new feature that was added and was missed getting added to the @aspnet/signalr-protocols-msgpack npm package.

Risk

Very low, adding a serialized response on the client when it would incorrectly throw before.

cc @muratg

@BrennanConroy BrennanConroy added the area-signalr Includes: SignalR clients and servers label Feb 8, 2019
@muratg muratg added this to the 2.2.x milestone Feb 9, 2019
@muratg muratg added the Servicing-approved Shiproom has approved the issue label Feb 9, 2019
@muratg
Copy link
Contributor

muratg commented Feb 9, 2019

@Eilon could you bar-check this one please?

@Eilon
Copy link
Contributor

Eilon commented Feb 12, 2019

  1. Why is it already marked servicing-approved?
  2. Does this only affect the npm package? This doesn't ship in any NUPKG or installers/templates right? If so, this seems reasonable to me and we should get shiproom approval.

@mikaelm12 mikaelm12 added Servicing-consider Shiproom approval is required for the issue and removed Servicing-approved Shiproom has approved the issue labels Feb 12, 2019
@mikaelm12
Copy link
Contributor

  1. Why is it already marked servicing-approved?

I'm pretty sure that was an off by one. I just updated it to consider.

  1. Does this only affect the npm package? This doesn't ship in any NUPKG or installers/templates right?

This is correct.

@Eilon
Copy link
Contributor

Eilon commented Feb 12, 2019

Cool. Can send shiproom mail for it. BTW I recommend updating the shiproom template to indicate it ships as OOB because it's an NPM package, not NuGet.

@BrennanConroy
Copy link
Member Author

indicate it ships as OOB

We try not to do that and build/ship at the same time the nupkgs do.

@Eilon
Copy link
Contributor

Eilon commented Feb 13, 2019

Yeah I get we ship as part of the build, and I don't want to do a one-off, but it's less scary when it's not in a NUPKG 😄

@muratg
Copy link
Contributor

muratg commented Feb 13, 2019

Thanks! (It was my mistake to mislabel this.)

I'll get this to the shiproom tomorrow.

@vivmishra vivmishra added Servicing-approved Shiproom has approved the issue and removed Servicing-consider Shiproom approval is required for the issue labels Feb 14, 2019
@vivmishra vivmishra modified the milestones: 2.2.x, 2.2.3 Feb 14, 2019
@vivmishra
Copy link

Approved for 2.2.3

Copy link
Contributor

@muratg muratg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved in shiproom. Let's get this in asap (before EOD please.)

@BrennanConroy
Copy link
Member Author

/azp run AspNetCore-ci

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@BrennanConroy BrennanConroy merged commit 9fda946 into release/2.2 Feb 14, 2019
@BrennanConroy BrennanConroy deleted the brecon/msgpackCancelBP branch February 14, 2019 21:49
@muratg
Copy link
Contributor

muratg commented Feb 14, 2019

@dougbu FYI this is in.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-signalr Includes: SignalR clients and servers Servicing-approved Shiproom has approved the issue
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants