don't build for csharp codeql #69
Annotations
2 errors and 20 warnings
Publish results to testspace
Process completed with exit code 1.
|
Integration tests (.NET)
Process completed with exit code 1.
|
Dotnet build:
backend/FixFwData/Program.cs#L1
The variable 'doNothing' is assigned but its value is never used
|
Dotnet build:
backend/MiniLcm/InMemoryApi.cs#L195
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.
|
Dotnet build:
backend/MiniLcm/InMemoryApi.cs#L214
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.
|
Dotnet build:
backend/FwDataMiniLcmBridge/Api/FwDataMiniLcmApi.cs#L167
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.
|
Dotnet build:
backend/FwDataMiniLcmBridge/Api/FwDataMiniLcmApi.cs#L175
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.
|
Dotnet build:
backend/FwDataMiniLcmBridge/Api/FwDataMiniLcmApi.cs#L255
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.
|
Dotnet build:
backend/FwDataMiniLcmBridge/LcmUtils/LcmThreadedProgress.cs#L10
The event 'LcmThreadedProgress.Canceling' is never used
|
Dotnet build:
backend/FwDataMiniLcmBridge/Api/UpdateProxy/UpdateSenseProxy.cs#L89
Observe the awaitable result of this method call by awaiting it, assigning to a variable, or passing it to another method (https://github.com/Microsoft/vs-threading/blob/main/doc/analyzers/VSTHRD110.md)
|
Dotnet build:
backend/FwDataMiniLcmBridge/Api/UpdateProxy/UpdateEntryProxy.cs#L38
Observe the awaitable result of this method call by awaiting it, assigning to a variable, or passing it to another method (https://github.com/Microsoft/vs-threading/blob/main/doc/analyzers/VSTHRD110.md)
|
Dotnet build:
backend/LexData/SeedingData.cs#L18
Parameter 'logger' is unread.
|
Integration tests (.NET)
The "--output" option isn't supported when building a solution. Specifying a solution-level output path results in all projects copying outputs to the same directory, which can lead to inconsistent builds.
|
Integration tests (.NET):
backend/LcmCrdt/LcmCrdtKernel.cs#L4
The using directive for 'Crdt' appeared previously in this namespace
|
Integration tests (.NET):
backend/LcmCrdt/CrdtLexboxApi.cs#L14
Parameter 'timeProvider' is unread.
|
Integration tests (.NET):
backend/LcmCrdt/Changes/RemoveSemanticDomainChange.cs#L11
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.
|
Integration tests (.NET):
backend/LcmCrdt/Changes/CreateSemanticDomainChange.cs#L16
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.
|
Integration tests (.NET):
backend/LcmCrdt/Changes/CreatePartOfSpeechChange.cs#L15
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.
|
Integration tests (.NET):
backend/LexData/SeedingData.cs#L18
Parameter 'logger' is unread.
|
Integration tests (.NET):
backend/LfClassicData/LfClassicLexboxApi.cs#L191
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.
|
Integration tests (.NET):
backend/FwDataMiniLcmBridge/Api/FwDataMiniLcmApi.cs#L167
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.
|
Integration tests (.NET):
backend/FwDataMiniLcmBridge/Api/FwDataMiniLcmApi.cs#L175
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.
|
Loading