feat: social publishing + NuGet #r + move perf + mesh stability batch #95

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open

rbuergi wants to merge 583 commits into main from bug_fix

Open

feat: social publishing + NuGet #r + move perf + mesh stability batch #95

chore(diag): remove one-shot disk tracer — fix verified

Annotations

1 error and 10 warnings

Publish Test Results

This action finished successfully, but test results have status failure.

Build: test/MeshWeaver.AI.Test/ChatCommandsTest.cs#L151

Calls to methods which accept CancellationToken should use TestContext.Current.CancellationToken to allow test cancellation to be more responsive. (https://xunit.net/xunit.analyzers/rules/xUnit1051)

Build: test/MeshWeaver.AI.Test/ChatCommandsTest.cs#L135

Calls to methods which accept CancellationToken should use TestContext.Current.CancellationToken to allow test cancellation to be more responsive. (https://xunit.net/xunit.analyzers/rules/xUnit1051)

Build: test/MeshWeaver.AI.Test/ChatCommandsTest.cs#L225

Calls to methods which accept CancellationToken should use TestContext.Current.CancellationToken to allow test cancellation to be more responsive. (https://xunit.net/xunit.analyzers/rules/xUnit1051)

Build: test/MeshWeaver.AI.Test/ChatCommandsTest.cs#L200

Calls to methods which accept CancellationToken should use TestContext.Current.CancellationToken to allow test cancellation to be more responsive. (https://xunit.net/xunit.analyzers/rules/xUnit1051)

Build: test/MeshWeaver.AI.Test/ChatCommandsTest.cs#L214

Calls to methods which accept CancellationToken should use TestContext.Current.CancellationToken to allow test cancellation to be more responsive. (https://xunit.net/xunit.analyzers/rules/xUnit1051)

Build: test/MeshWeaver.AI.Test/ChatCommandsTest.cs#L186

Calls to methods which accept CancellationToken should use TestContext.Current.CancellationToken to allow test cancellation to be more responsive. (https://xunit.net/xunit.analyzers/rules/xUnit1051)

Build: test/MeshWeaver.AI.Test/ChatCommandsTest.cs#L175

Calls to methods which accept CancellationToken should use TestContext.Current.CancellationToken to allow test cancellation to be more responsive. (https://xunit.net/xunit.analyzers/rules/xUnit1051)

Build: test/MeshWeaver.AI.Test/ChatCommandsTest.cs#L164

Calls to methods which accept CancellationToken should use TestContext.Current.CancellationToken to allow test cancellation to be more responsive. (https://xunit.net/xunit.analyzers/rules/xUnit1051)

Build: test/MeshWeaver.AI.Test/ChatCommandsTest.cs#L151

Calls to methods which accept CancellationToken should use TestContext.Current.CancellationToken to allow test cancellation to be more responsive. (https://xunit.net/xunit.analyzers/rules/xUnit1051)

Build: test/MeshWeaver.AI.Test/ChatCommandsTest.cs#L135

Calls to methods which accept CancellationToken should use TestContext.Current.CancellationToken to allow test cancellation to be more responsive. (https://xunit.net/xunit.analyzers/rules/xUnit1051)