Release: prepare v2025.1.0 #1057
Annotations
21 warnings
|
Tests:
rd-net/Test.Lifetimes/Lifetimes/LifetimeTest.cs#L235
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Tests:
rd-net/Test.Lifetimes/Lifetimes/LifetimeTest.cs#L260
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.
|
|
Tests:
rd-net/Test.Lifetimes/Lifetimes/LifetimeTest.cs#L235
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Tests:
rd-net/Test.Lifetimes/Lifetimes/LifetimeTest.cs#L260
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.
|
|
Tests:
rd-net/Test.RdFramework/Components/TestWire.cs#L20
'WireBase.WireBase(IScheduler)' is obsolete
|
|
Tests:
rd-net/Test.RdFramework/RdTaskTest.cs#L256
'RdCall<int, string>.Set(Func<Lifetime, int, RdTask<string>>, IScheduler?, IScheduler?)' is obsolete: 'This is an internal API. It is preferable to use SetSync or SetAsync extension methods'
|
|
Tests:
rd-net/Test.RdFramework/RdTaskTest.cs#L250
The variable 'entity_id' is assigned but its value is never used
|
|
Tests:
rd-net/Test.RdFramework/RdTaskTest.cs#L281
'RdCall<int, string>.Set(Func<Lifetime, int, RdTask<string>>, IScheduler?, IScheduler?)' is obsolete: 'This is an internal API. It is preferable to use SetSync or SetAsync extension methods'
|
|
Tests:
rd-net/Test.RdFramework/RdTaskTest.cs#L274
The variable 'entity_id' is assigned but its value is never used
|
|
Tests:
rd-net/Test.RdFramework/Reflection/ProxyGeneratorCancellationTest.cs#L82
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Compile:
rd-net/Test.Lifetimes/Lifetimes/LifetimeTest.cs#L235
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Compile:
rd-net/Test.Lifetimes/Lifetimes/LifetimeTest.cs#L260
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.
|
|
Compile:
rd-net/Test.Lifetimes/Lifetimes/LifetimeTest.cs#L235
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Compile:
rd-net/Test.Lifetimes/Lifetimes/LifetimeTest.cs#L260
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.
|
|
Compile:
rd-net/Test.RdFramework/Components/TestWire.cs#L20
'WireBase.WireBase(IScheduler)' is obsolete
|
|
Compile:
rd-net/Test.RdFramework/Reflection/ProxyGeneratorCancellationTest.cs#L82
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Compile:
rd-net/Test.RdFramework/RdTaskTest.cs#L256
'RdCall<int, string>.Set(Func<Lifetime, int, RdTask<string>>, IScheduler?, IScheduler?)' is obsolete: 'This is an internal API. It is preferable to use SetSync or SetAsync extension methods'
|
|
Compile:
rd-net/Test.RdFramework/RdTaskTest.cs#L250
The variable 'entity_id' is assigned but its value is never used
|
|
Compile:
rd-net/Test.RdFramework/RdTaskTest.cs#L281
'RdCall<int, string>.Set(Func<Lifetime, int, RdTask<string>>, IScheduler?, IScheduler?)' is obsolete: 'This is an internal API. It is preferable to use SetSync or SetAsync extension methods'
|
|
Compile:
rd-net/Test.RdFramework/RdTaskTest.cs#L274
The variable 'entity_id' is assigned but its value is never used
|
|
The following artifacts were uploaded using a version of actions/upload-artifact that is scheduled for deprecation: "macOS.test-results".
Please update your workflow to use v4 of the artifact actions.
Learn more: https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions/
|
Loading