Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v2, actions/setup-dotnet@v1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-dotnet@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

Nullability of type of parameter 'existingValue' doesn't match overridden member (possibly because of nullability attributes).

Nullability of type of parameter 'value' doesn't match overridden member (possibly because of nullability attributes).

Nullability of type of parameter 'existingValue' doesn't match overridden member (possibly because of nullability attributes).

Nullability of reference types in type of parameter 'value' of 'void BinanceFileCommunicator.Name.set' doesn't match implicitly implemented member 'void IWebsocketClient.Name.set' (possibly because of nullability attributes).

Nullability of reference types in type of parameter 'value' of 'void BinanceFileCommunicator.MessageEncoding.set' doesn't match implicitly implemented member 'void IWebsocketClient.MessageEncoding.set' (possibly because of nullability attributes).

Nullability of type of parameter 'existingValue' doesn't match overridden member (possibly because of nullability attributes).

Non-nullable property 'Headers' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.

Non-nullable property 'Headers' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.

Non-nullable property 'Headers' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.

Non-nullable property 'Message' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.

Nullability of reference types in type of parameter 'value' of 'void BinanceFileCommunicator.Name.set' doesn't match implicitly implemented member 'void IWebsocketClient.Name.set' (possibly because of nullability attributes).

Nullability of reference types in type of parameter 'value' of 'void BinanceFileCommunicator.MessageEncoding.set' doesn't match implicitly implemented member 'void IWebsocketClient.MessageEncoding.set' (possibly because of nullability attributes).

Nullability of type of parameter 'existingValue' doesn't match overridden member (possibly because of nullability attributes).

Nullability of type of parameter 'value' doesn't match overridden member (possibly because of nullability attributes).

Nullability of type of parameter 'existingValue' doesn't match overridden member (possibly because of nullability attributes).

Nullability of type of parameter 'existingValue' doesn't match overridden member (possibly because of nullability attributes).

Non-nullable property 'Symbol' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.

Possible null reference argument for parameter 'response' in 'bool AggregatedTradeResponse.TryHandle(JObject response, ISubject<AggregatedTradeResponse> subject)'.

Non-nullable property 'Message' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.