dotnet-core

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 translate Convert<int>(string), but we could also translate x.Parse on the various primitive types (int, long...), as they're a common .NET API. We'd only support the simple overloads accepting a string, nothing more.

Originally raised in dotnet/efcore#28282 (comment)

Expected Behavior / New Feature

Support sticky sessions for ServiceDiscoveryProviders

Actual Behavior / Motivation for New Feature

When using websockets with ocelot in a distributed system, problem can arise since ocelot, as far as i know, doesn't support sticky sessions when working with service discovery providers.

The functionality could be great if it could work with both consul

Take example on https://docs.orchardcore.net/en/latest/docs/getting-started/theme/ and adapt it for a module.

Good first issue: Add a comment if you want to work on it and make to your first documentation contribution.

The built in --help and --version outputs are printed to stderr instead of stdout, you have to redirect them to use the commands properly.

test --version returns the version number, but on stderr not stdout.

e.g.
test --version 2>nul returns no output.
test --version 2>&1 prints the version to stdout as expected.

Let's add MinVer and on successful builds generate a release.