-adding support for appending single data point/timestamp to a new or… #867
Annotations
1 error and 13 warnings
Build
Process completed with exit code 1.
|
Build
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
Build
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
Build:
Dynamic/PlantSimulator/PlantSimulator.cs#L454
The variable 'lookBackIndex' is assigned but its value is never used
|
Build:
Dynamic/Identification/ClosedLoopGainGlobalSearchResults.cs#L24
Field 'ClosedLoopGainGlobalSearchResults.pidLinearProcessGainList' is never assigned to, and will always have its default value null
|
Build:
Dynamic/TimeDelay/TimeDelaySamples.cs#L19
The field 'TimeDelaySamples.timeBase_s' is never used
|
Build:
Dynamic/TimeDelay/TimeDelaySamples.cs#L20
The field 'TimeDelaySamples.timeDelay_s' is never used
|
Build:
TimeSeriesAnalysis.Tests/Test/PlantSimulations/GainSchedSimulateTests.cs#L445
The variable 'tolerance' is assigned but its value is never used
|
Build:
Dynamic/PlantSimulator/PlantSimulator.cs#L454
The variable 'lookBackIndex' is assigned but its value is never used
|
Build:
Dynamic/Identification/ClosedLoopGainGlobalSearchResults.cs#L24
Field 'ClosedLoopGainGlobalSearchResults.pidLinearProcessGainList' is never assigned to, and will always have its default value null
|
Build:
Dynamic/TimeDelay/TimeDelaySamples.cs#L19
The field 'TimeDelaySamples.timeBase_s' is never used
|
Build:
Dynamic/TimeDelay/TimeDelaySamples.cs#L20
The field 'TimeDelaySamples.timeDelay_s' is never used
|
Build:
TimeSeriesAnalysis.Tests/Test/PlantSimulations/GainSchedSimulateTests.cs#L445
The variable 'tolerance' is assigned but its value is never used
|
Build
.NET 6.0 is no longer supported and will not receive security updates in the future. Please refer to https://aka.ms/dotnet-core-support for more information about the .NET support policy.
|