Upgrade Nuget #66
Annotations
1 error and 11 warnings
build-publish
Process completed with exit code 1.
|
build-publish
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-dotnet@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
build-publish:
NewLife.MQTT/Messaging/ConnectMessage.cs#L99
Non-nullable property 'WillMessage' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
|
build-publish:
NewLife.MQTT/Messaging/ConnectMessage.cs#L99
Non-nullable property 'WillMessage' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
|
build-publish:
NewLife.MQTT/Messaging/ConnectMessage.cs#L99
Non-nullable property 'WillMessage' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
|
build-publish:
NewLife.MQTT/Messaging/ConnectMessage.cs#L99
Non-nullable property 'WillMessage' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
|
build-publish:
Test/Program.cs#L148
Unreachable code detected
|
build-publish:
NewLife.MqttServer/DefaultManagedMqttClient.cs#L114
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
build-publish:
NewLife.MqttServer/DefaultManagedMqttClient.cs#L155
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
build-publish:
NewLife.MqttServer/DefaultManagedMqttClient.cs#L166
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
build-publish:
XUnitTestClient/MqttClientTests.cs#L71
Support for 'async void' unit tests is being removed from xUnit.net v3. To simplify upgrading, convert the test to 'async Task' instead. (https://xunit.net/xunit.analyzers/rules/xUnit1048)
|
build-publish:
XUnitTestClient/MqttClientTests.cs#L82
Support for 'async void' unit tests is being removed from xUnit.net v3. To simplify upgrading, convert the test to 'async Task' instead. (https://xunit.net/xunit.analyzers/rules/xUnit1048)
|