.NET

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

JS SignalR Client version: 6.0.7

/** The version of the SignalR client. */
const VERSION = "6.0.7";

Overview.

Using standard SignalR reconnection mechanism, and in case connection was not finally established, the number of reconnection attempts is incorrectly logged. T

What's the Problem?

No response

Solution/Idea

Alternatives

NA

Priorities

Please describe your bug

When the server is stopped it sends a notification to all connected WebSocket clients, the message looks like this:

{"MessageType":"ServerShuttingDown","MessageId":"d9fbbca3037344b689490d35ec2d4ed7","Data":""}

(id is unique)

Unfortunately it then just stops the server, ending the connection abruptly. It would be nice if the clients get properl

The "src" directory contains a number of JS files that are added to the base copy of RN. It is not a complete source tree itself. Renaming to "patches" would increase clarity of intent, and follow OSS "patch-package" conventions.

When writing the endpoint address of the packet received from the socket, we do not verify the output buffer is allocated, and has enough space to hold the endpoint address. We should verify sockAddrOutSize is non-zero at a minimum. Additionally, IPEndpoint can represent either an IPv4 address or an IPv6 address. If the socket receives a packet from an IPv6 address, but the client has only all

We can build much smaller Mono runtime for .NET Core purposes by simply removing code we don't need in this configuration. We did a few easy initial steps but we can go much further.

This list is not comprehensive but parts like

• Culture Data
• Any PAL related code
• Unused icalls

MonoGame has a very long history of tutorials, some are as old as a decade and some even are still based on XNA (which is compatible with MonoGame for the most part, but different in regard to how to start a project).

Also, MonoGame is a stable API with a policy of "no breaking changes" when possible, which means that even very old tutorials

Typo under the description: Returns a containing. Returns a what?

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: d2dc315d-96d7-e54f-6e90-fec6ed09481c
• Version Independent ID: ab5d0a68-35d6-ef5f-786e-d89e7fee8034
• Content: [DataFrameColumn.Info Method (Microsoft.Data.Analysis)](https://docs.microsoft.com/e

Various characters (e.g. |) if used in a Params will end up invalidating the generated markdown, causing it to render incorrectly. It'd be helpful if benchmarkdotnet could escape the markdown output, e.g. output \| instead of |.