ValidateDotNetAssembly outer catch logs with fileData.FileName. If fileData itself is null (or the failure path NRE'd before assignment), the catch throws a second NullReferenceException instead of returning FileValidationResult.Failure.
Repro
Pinned characterization: FileValidationServiceTests.ValidateDotNetAssembly_NullFileData_ThrowsInsteadOfFailing on PR #454 / test/coverage-wave-2026-07.
Fix
Use null-conditional in the log (fileData?.FileName) and/or guard fileData is null at method entry.
Impact
Unexpected null DTO crashes the call site instead of a structured validation failure.
## Summary
`ValidateDotNetAssembly` outer `catch` logs with `fileData.FileName`. If `fileData` itself is null (or the failure path NRE'd before assignment), the catch throws a second `NullReferenceException` instead of returning `FileValidationResult.Failure`.
## Repro
Pinned characterization: `FileValidationServiceTests.ValidateDotNetAssembly_NullFileData_ThrowsInsteadOfFailing` on PR #454 / `test/coverage-wave-2026-07`.
## Fix
Use null-conditional in the log (`fileData?.FileName`) and/or guard `fileData is null` at method entry.
## Impact
Unexpected null DTO crashes the call site instead of a structured validation failure.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
ValidateDotNetAssemblyoutercatchlogs withfileData.FileName. IffileDataitself is null (or the failure path NRE'd before assignment), the catch throws a secondNullReferenceExceptioninstead of returningFileValidationResult.Failure.Repro
Pinned characterization:
FileValidationServiceTests.ValidateDotNetAssembly_NullFileData_ThrowsInsteadOfFailingon PR #454 /test/coverage-wave-2026-07.Fix
Use null-conditional in the log (
fileData?.FileName) and/or guardfileData is nullat method entry.Impact
Unexpected null DTO crashes the call site instead of a structured validation failure.