Skip to content

Conversation

@BrennanConroy
Copy link
Member

Fixes #15085

Before, we were running users options first then running our options setup. This would override null values because we treat those as uninitialized. However, in cases like MaximumReceiveMessageSize, null can also mean no-limit.

Now, we run users options second. And for MaximumReceiveMessageSize we track if the user sets the value so we don't accidentally use the global value if they set it to null in the hub type specific options.

@Pilchie for 3.1 bug fix approval.

@BrennanConroy BrennanConroy added the area-signalr Includes: SignalR clients and servers label Oct 17, 2019
@BrennanConroy BrennanConroy added this to the 3.1.0-preview2 milestone Oct 17, 2019
@halter73
Copy link
Member

@anurse Should we put the Servicing-Consider label on this or something?

@analogrelay analogrelay removed the area-signalr Includes: SignalR clients and servers label Oct 17, 2019
@BrennanConroy BrennanConroy added the area-signalr Includes: SignalR clients and servers label Oct 17, 2019
Copy link
Member

@halter73 halter73 left a comment

Choose a reason for hiding this comment

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

Nice!

@analogrelay
Copy link
Contributor

Approved in the issue, as per: #15085 (comment)

@analogrelay analogrelay added the Servicing-approved Shiproom has approved the issue label Oct 22, 2019
@BrennanConroy BrennanConroy merged commit 1ea47f1 into release/3.1 Oct 22, 2019
@BrennanConroy BrennanConroy deleted the brecon/options branch October 22, 2019 16:53
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.

4 participants