Repository navigation
Expose file import log processing diagnostics #335
pullrequest.yml
on: pull_request
Build and Test Pull Requests
1m 0s
Annotations
6 errors, 13 warnings, and 1 notice
|
Build and Test Pull Requests
No test report files were found
|
|
Build and Test Pull Requests
Process completed with exit code 1.
|
|
Build and Test Pull Requests:
FileProcessor.Client/FileProcessorClient.cs#L216
Argument 1: cannot convert from 'System.Collections.Generic.List<FileProcessor.DataTransferObjects.Responses.FileImportLog>' to 'System.Collections.Generic.IEnumerable<FileProcessor.Models.FileImportLog>'
|
|
Build and Test Pull Requests:
FileProcessor.Client/FileProcessorClient.cs#L198
'FileImportLog' is an ambiguous reference between 'FileProcessor.Models.FileImportLog' and 'FileProcessor.DataTransferObjects.Responses.FileImportLog'
|
|
Build and Test Pull Requests:
FileProcessor.Client/FileProcessorClient.cs#L216
Argument 1: cannot convert from 'System.Collections.Generic.List<FileProcessor.DataTransferObjects.Responses.FileImportLog>' to 'System.Collections.Generic.IEnumerable<FileProcessor.Models.FileImportLog>'
|
|
Build and Test Pull Requests:
FileProcessor.Client/FileProcessorClient.cs#L198
'FileImportLog' is an ambiguous reference between 'FileProcessor.Models.FileImportLog' and 'FileProcessor.DataTransferObjects.Responses.FileImportLog'
|
|
Build and Test Pull Requests
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/setup-dotnet@v4, actions/upload-artifact@v4, dorny/test-reporter@v1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Build and Test Pull Requests
No files were found with the provided path: **/TestResults/*. No artifacts will be uploaded.
|
|
Build and Test Pull Requests
No file matches path **/TestResults/*.trx
|
|
Build and Test Pull Requests:
FileProcessor.BusinessLogic.Tests/FileProcessingManagerTests.cs#L341
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Build and Test Pull Requests:
FileProcessor.BusinessLogic.Tests/FileProfileDirectorySynchronizerTests.cs#L27
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Build and Test Pull Requests:
FileProcessor.BusinessLogic.Tests/FileProcessingManagerTests.cs#L71
The variable 'context' is assigned but its value is never used
|
|
Build and Test Pull Requests:
FileProcessor.Tests/ModelFactoryTests.cs#L161
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Build and Test Pull Requests:
FileProcessor.Tests/ModelFactoryTests.cs#L131
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Build and Test Pull Requests:
FileProcessor/Program.cs#L92
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Build and Test Pull Requests:
FileProcessor/Common/Extensions.cs#L34
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Build and Test Pull Requests:
FileProcessor.BusinessLogic/Managers/FileProcessorManager.cs#L81
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Build and Test Pull Requests:
FileProcessor.FileProfileAggregate/FileProfileAggregate.cs#L305
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Build and Test Pull Requests:
FileProcessor.FileProfileAggregate/FileProfileAggregate.cs#L161
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Build and Test Pull Requests
"The ubuntu-latest label will migrate to Ubuntu 26 beginning October 19, 2026. For more information, see https://github.com/actions/runner-images/issues/14748"
|