Skip to content

feat: implement template pipe support #526

feat: implement template pipe support

feat: implement template pipe support #526

Triggered via push October 2, 2024 14:09
Status Failure
Total duration 2m 23s
Artifacts

default.yml

on: push
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 4 warnings
Running tests on macOS-latest
Process completed with exit code 252.
Running tests on ubuntu-latest
Process completed with exit code 252.
Running tests on windows-latest
The job was canceled because "ubuntu-latest" failed.
Running tests on windows-latest
The operation was canceled.
Running tests on macOS-latest: src/WeihanLi.Common.Logging.Serilog/SerilogLogger.cs#L42
Nullability in constraints for type parameter 'TState' of method 'SerilogLogger.BeginScope<TState>(TState)' doesn't match the constraints for type parameter 'TState' of interface method 'ILogger.BeginScope<TState>(TState)'. Consider using an explicit interface implementation instead.
Running tests on macOS-latest: src/WeihanLi.Common.Logging.Serilog/SerilogLogger.cs#L42
Nullability in constraints for type parameter 'TState' of method 'SerilogLogger.BeginScope<TState>(TState)' doesn't match the constraints for type parameter 'TState' of interface method 'ILogger.BeginScope<TState>(TState)'. Consider using an explicit interface implementation instead.
Running tests on ubuntu-latest: src/WeihanLi.Common.Logging.Serilog/SerilogLogger.cs#L42
Nullability in constraints for type parameter 'TState' of method 'SerilogLogger.BeginScope<TState>(TState)' doesn't match the constraints for type parameter 'TState' of interface method 'ILogger.BeginScope<TState>(TState)'. Consider using an explicit interface implementation instead.
Running tests on ubuntu-latest: src/WeihanLi.Common.Logging.Serilog/SerilogLogger.cs#L42
Nullability in constraints for type parameter 'TState' of method 'SerilogLogger.BeginScope<TState>(TState)' doesn't match the constraints for type parameter 'TState' of interface method 'ILogger.BeginScope<TState>(TState)'. Consider using an explicit interface implementation instead.