Added the possibility to restrict the host IP address for port mappings. #55
Triggered via pull request
February 22, 2024 15:21
nscheibe
Status
Failure
Total duration
10m 28s
Artifacts
–
Annotations
1 error and 10 warnings
|
tests
Process completed with exit code 4.
|
|
tests:
src/Core/Logger.cs#L58
Cannot convert null literal to non-nullable reference type.
|
|
tests:
src/Core/GenericContainer/GenericContainerResource.cs#L67
'GenericContainerResource<TOptions>.GetComposeExports()' hides inherited member 'ContainerResource<TOptions>.GetComposeExports()'. To make the current member override that implementation, add the override keyword. Otherwise add the new keyword.
|
|
tests:
src/Core/ContainerAddress.cs#L18
Non-nullable property 'Address' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
|
tests:
src/Core/ContainerInstance.cs#L16
Non-nullable property 'Id' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
|
tests:
src/Core/ContainerInstance.cs#L21
Non-nullable property 'Name' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
|
tests:
src/Core/ContainerInstance.cs#L29
Non-nullable property 'Address' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
|
tests:
src/Core/ContainerInstance.cs#L37
Non-nullable property 'IpAddress' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
|
tests:
src/Core/ContainerPortMapping.cs#L16
Non-nullable property 'InternalPortVariableName' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
|
tests:
src/Core/ContainerPortMapping.cs#L29
Non-nullable property 'ExternalPortVariableName' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
|
tests:
src/Core/ContainerResource.cs#L125
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.
|