Skip to content

Fix the problem with chathistory repeating items #16

Fix the problem with chathistory repeating items

Fix the problem with chathistory repeating items #16

Triggered via push December 27, 2023 11:59
Status Success
Total duration 22s
Artifacts
Fit to window
Zoom out
Zoom in

Annotations

13 warnings
build
The following actions uses node12 which is deprecated and will be forced to run on node16: battila7/get-version-action@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
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: src/skUnit/Asserts/SemanticKernelAssert_Function.cs#L48
Possible null reference argument for parameter 'input' in 'Task IKernelAssertion.Assert(Semantic semantic, string input)'.
build: src/skUnit/Asserts/SemanticKernelAssert_Function.cs#L127
Possible null reference argument for parameter 'input' in 'Task IKernelAssertion.Assert(Semantic semantic, string input)'.
build: src/skUnit/Asserts/SemanticKernelAssert_Initialize.cs#L53
Possible null reference argument for parameter 'obj' in 'void Action<string>.Invoke(string obj)'.
build: src/skUnit/Asserts/SemanticKernelAssert_Kernel.cs#L64
Possible null reference argument for parameter 'input' in 'Task IKernelAssertion.Assert(Semantic semantic, string input)'.
build: src/skUnit/Asserts/SemanticKernelAssert_Kernel.cs#L150
Possible null reference argument for parameter 'input' in 'Task IKernelAssertion.Assert(Semantic semantic, string input)'.
build: src/skUnit/Scenarios/Parsers/Assertions/NotEmptyAssertion.cs#L18
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.
build: src/skUnit/Scenarios/Parsers/Assertions/ContainsAllAssertion.cs#L23
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.
build: src/skUnit/Scenarios/Parsers/Assertions/ContainsAnyAssertion.cs#L23
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.
build: src/skUnit/Scenarios/Parsers/Assertions/EmptyAssertion.cs#L23
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.
build: src/skUnit/Scenarios/Parsers/Assertions/EqualsAssertion.cs#L28
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.