Bump Microsoft.Extensions.Logging and Microsoft.Extensions.Logging.Console #385
Annotations
1 error, 10 warnings, and 1 notice
|
|
|
RDMSharpTests/RDM/PayloadObject/TestAbstractRDMPayloadObjectDataTreeObjectAttributeTestSubject.cs#L14
Dereference of a possibly null reference.
|
|
RDMSharpTests/Devices/TestRDMSendReceive_SlotOverflow.cs#L28
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.
|
|
RDMSharp/RDM/Device/AbstractRemoteRDMDevice.cs#L213
Because this call is not awaited, execution of the current method continues before the call is completed. Consider applying the 'await' operator to the result of the call.
|
|
RDMSharp/RDMSharp.cs#L22
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
RDMSharp/RDMSharp.cs#L21
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
RDMSharpTests/RDM/PayloadObject/TestAbstractRDMPayloadObjectDataTreeObjectAttributeTestSubject.cs#L14
Dereference of a possibly null reference.
|
|
RDMSharpTests/Devices/TestRDMSendReceive_SlotOverflow.cs#L28
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.
|
|
RDMSharp/RDM/Device/AbstractRemoteRDMDevice.cs#L213
Because this call is not awaited, execution of the current method continues before the call is completed. Consider applying the 'await' operator to the result of the call.
|
|
RDMSharp/RDMSharp.cs#L22
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
RDMSharp/RDMSharp.cs#L21
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|
The logs for this run have expired and are no longer available.
Loading