Add code fix for MSTEST0040 — AvoidUsingAssertsInAsyncVoidContext by Copilot · Pull Request #7892 · microsoft/testfx

Copilot · 2026-04-28T07:01:55Z

MSTEST0040 warns when Assert calls appear inside async void methods, local functions, or delegates, but offered no automated remediation. This adds a code fix that converts async void to async Task.

Changes

New fixer AvoidUsingAssertsInAsyncVoidContextFixer.cs:
- Offers "Change return type to 'Task'" for async void methods and async void local functions
- No fix is offered for override methods, virtual methods (changing would break derived-class overrides with CS0508), or explicit interface implementations (changing would break the interface contract with CS0539)
- No fix for async lambda/anonymous function cases — the delegate type itself would also need changing, which is too invasive for a single-step fix
- Fix is offered for Assert calls inside non-async lambdas nested within an async void method/local function — the walk correctly skips non-async lambdas and finds the enclosing context
- Automatically adds using System.Threading.Tasks; if absent, inserted after existing System.* usings and before non-System usings
- Correctly handles global::System.Threading.Tasks and namespace-scoped using directives (no duplicate import inserted)
- Alias directives (using Tasks = System.Threading.Tasks;) and static imports are not treated as satisfying the System.Threading.Tasks import
Resource string AvoidUsingAssertsInAsyncVoidContextFix added to CodeFixResources.resx
Test coverage includes:
- Method and local function fix (with and without an existing System.Threading.Tasks using)
- Assert inside a non-async lambda nested in an async void method
- No-fix cases: override, virtual, explicit interface implementation, async delegate/lambda
- Multiple Assert calls in one method (batch fix via BatchFixer)
- Namespace-scoped using System.Threading.Tasks; — no spurious file-level import added

Example

// Before (MSTEST0040)
[TestMethod]
public async void TestMethod()
{
    await Task.Delay(1);
    Assert.Fail(""); // ← diagnostic here
}

// After applying fix
[TestMethod]
public async Task TestMethod()
{
    await Task.Delay(1);
    Assert.Fail("");
}

[!WARNING]

Adds AvoidUsingAssertsInAsyncVoidContextFixer that offers 'Change return type to Task' for async void methods and async void local functions that contain Assert calls. Lambda/delegate cases are not fixable by this fixer since they require changing the delegate type as well. Also updates the test file to use the new fixer and adds expected fixed code for the fixable test cases. Agent-Logs-Url: https://github.com/microsoft/testfx/sessions/d94e25ce-ce83-4da5-9989-a4d9d8e0b41b Co-authored-by: Evangelink <11340282+Evangelink@users.noreply.github.com>

…Task Also improve using insertion order (System namespaces before non-System) Agent-Logs-Url: https://github.com/microsoft/testfx/sessions/d94e25ce-ce83-4da5-9989-a4d9d8e0b41b Co-authored-by: Evangelink <11340282+Evangelink@users.noreply.github.com>

Address code review feedback: - Use SyntaxFactory.ElasticCarriageReturnLineFeed instead of hardcoded \r\n - Simplify using insertion logic with clearer default Agent-Logs-Url: https://github.com/microsoft/testfx/sessions/d94e25ce-ce83-4da5-9989-a4d9d8e0b41b Co-authored-by: Evangelink <11340282+Evangelink@users.noreply.github.com>

Copilot

Pull request overview

Adds an MSTest analyzer code fix for MSTEST0040 to automatically remediate Assert usage in async void contexts by changing async void methods/local functions to async Task, plus the necessary localized code-fix title resources and unit test updates.

Changes:

Introduces AvoidUsingAssertsInAsyncVoidContextFixer to convert async void methods and local functions to async Task and ensure System.Threading.Tasks is imported.
Adds the code-fix title string to CodeFixResources.resx and propagates it to the .xlf localization files.
Updates analyzer unit tests to use the new code fix provider and validate fixed output for method/local-function scenarios.

Show a summary per file

File	Description
test/UnitTests/MSTest.Analyzers.UnitTests/AvoidUsingAssertsInAsyncVoidContextAnalyzerTests.cs	Switches verifier to the new fixer and adds fixed-code expectations for method/local-function cases.
src/Analyzers/MSTest.Analyzers.CodeFixes/AvoidUsingAssertsInAsyncVoidContextFixer.cs	New code fix provider that changes `async void` to `async Task` and injects a `System.Threading.Tasks` using when needed.
src/Analyzers/MSTest.Analyzers.CodeFixes/CodeFixResources.resx	Adds localized string key for the new code fix title.
src/Analyzers/MSTest.Analyzers.CodeFixes/xlf/CodeFixResources.cs.xlf	Adds localization entry for the new code fix title (state=new).
src/Analyzers/MSTest.Analyzers.CodeFixes/xlf/CodeFixResources.de.xlf	Adds localization entry for the new code fix title (state=new).
src/Analyzers/MSTest.Analyzers.CodeFixes/xlf/CodeFixResources.es.xlf	Adds localization entry for the new code fix title (state=new).
src/Analyzers/MSTest.Analyzers.CodeFixes/xlf/CodeFixResources.fr.xlf	Adds localization entry for the new code fix title (state=new).
src/Analyzers/MSTest.Analyzers.CodeFixes/xlf/CodeFixResources.it.xlf	Adds localization entry for the new code fix title (state=new).
src/Analyzers/MSTest.Analyzers.CodeFixes/xlf/CodeFixResources.ja.xlf	Adds localization entry for the new code fix title (state=new).
src/Analyzers/MSTest.Analyzers.CodeFixes/xlf/CodeFixResources.ko.xlf	Adds localization entry for the new code fix title (state=new).
src/Analyzers/MSTest.Analyzers.CodeFixes/xlf/CodeFixResources.pl.xlf	Adds localization entry for the new code fix title (state=new).
src/Analyzers/MSTest.Analyzers.CodeFixes/xlf/CodeFixResources.pt-BR.xlf	Adds localization entry for the new code fix title (state=new).
src/Analyzers/MSTest.Analyzers.CodeFixes/xlf/CodeFixResources.ru.xlf	Adds localization entry for the new code fix title (state=new).
src/Analyzers/MSTest.Analyzers.CodeFixes/xlf/CodeFixResources.tr.xlf	Adds localization entry for the new code fix title (state=new).
src/Analyzers/MSTest.Analyzers.CodeFixes/xlf/CodeFixResources.zh-Hans.xlf	Adds localization entry for the new code fix title (state=new).
src/Analyzers/MSTest.Analyzers.CodeFixes/xlf/CodeFixResources.zh-Hant.xlf	Adds localization entry for the new code fix title (state=new).

Copilot's findings

Files reviewed: 16/16 changed files
Comments generated: 3

github-actions

Summary

Workflow: Test Expert Reviewer 🧪
Date: 2026-04-29
Repository: microsoft/testfx

Key Findings

The code fix logic, fixer structure, and diagnostic tests are well-organized. The existing tests do verify the happy paths: async void method → async Task, async void local function → async Task, and no-fix for delegate/lambda contexts. The test names follow the established {AssertType}In{Context}_[No]Diagnostic convention.

However, there is one significant coverage gap — a core code path in the fixer is completely untested:

Untested import-addition branch — EnsureSystemThreadingTasksImportAsync has two branches: (a) early-return when the import exists, and (b) insert the using System.Threading.Tasks; when absent. Every diagnostic test already includes the import in the input, so branch (b) is never exercised. This means the primary new functionality of the code fix (auto-inserting the missing using) has no test coverage.
Untested using-insertion ordering — The fixer specifically places the new using after System.* usings but before non-System.* usings. The only test with mixed usings (UseCollectionAssertMethodInAsyncVoidMethod_Diagnostic) already has System.Threading.Tasks, so this ordering code is never reached.

Recommendations

Add at least one test where the input code has no using System.Threading.Tasks; (just using Microsoft.VisualStudio.TestTools.UnitTesting;) and verify the fixer adds it in the correct position.
This single test would cover both the import-addition path and the insertion-ordering logic.

Generated by Test Expert Reviewer

🧪 Test quality reviewed by Test Expert Reviewer 🧪

github-actions

Summary

Workflow: Expert Code Reviewer 🧠
Date: 2026-04-29
Repository: microsoft/testfx

Key Findings

[Correctness — Critical] override async void methods are not guarded against. Applying the fix to a method with the override modifier changes its return type from void to Task, breaking the override relationship and producing CS0115 ("no suitable method found to override"). The resulting code does not compile. Fix: add !methodDeclaration.Modifiers.Any(SyntaxKind.OverrideKeyword) to the precondition in RegisterCodeFixesAsync.
[Correctness — Important] EnsureSystemThreadingTasksImportAsync only inspects the file's own compilationUnit.Usings, missing global using System.Threading.Tasks; from other files and SDK implicit usings. On .NET 6+ projects this silently adds a redundant using directive that triggers CS8019 / IDE0005. When warnings are treated as errors the fixed code fails to build.
[Correctness — Minor] The using-insertion loop places System.Threading.Tasks after all System.* usings rather than at the correct alphabetical position. This creates an SA1210 violation (e.g. if System.Threading.Tasks.Extensions is already present), which can become a build error in strict stylecop configurations.

Positive Observations

The overall architecture is clean and follows the existing Roslyn fixer patterns in this repository.
The deliberate decision to not fix lambdas/anonymous functions is well-reasoned and correctly implemented via an explicit AnonymousFunctionExpressionSyntax guard.
ConfigureAwait(false) is correctly applied throughout all async paths.
The trivia-preservation via .WithTriviaFrom(...) ensures the fix doesn't corrupt surrounding whitespace.
Test coverage is thorough, exercising Assert, StringAssert, and CollectionAssert across both methods and local functions.

Generated by Expert Code Reviewer

🧠 Reviewed by Expert Code Reviewer 🧠

Evangelink · 2026-04-29T05:11:42Z

@copilot address review comments

…extFixer - Only stop at async AnonymousFunctionExpressionSyntax (not non-async lambdas), so Assert inside a non-async lambda nested in async void method gets a fix offer - Exclude alias directives and static usings when checking for System.Threading.Tasks import - Add tests for missing using import and non-async lambda inside async void method Agent-Logs-Url: https://github.com/microsoft/testfx/sessions/a9cefeaa-bf7a-40c5-83e2-0f17e9b91190 Co-authored-by: Evangelink <11340282+Evangelink@users.noreply.github.com>

Copilot · 2026-04-29T05:17:27Z

@copilot address review comments

Addressed all three review comments in d780534:

Non-async lambda inside async void method: The fixer now only stops walking when it hits an async AnonymousFunctionExpressionSyntax. Non-async lambdas are transparent, so an Assert inside a () => { ... } nested in an async void method will correctly offer the fix on the enclosing method.
Alias directive false positive: The import check now requires u.Alias is null && !u.StaticKeyword.IsKind(SyntaxKind.StaticKeyword), so using Tasks = System.Threading.Tasks; no longer counts as satisfying the import.
Missing test coverage: Added two new tests — one that verifies using System.Threading.Tasks; is inserted in the correct position when absent, and one that verifies the fix is offered for Assert calls inside non-async lambdas nested in async void methods.

…, and tests - Skip code fix for 'override async void' methods (would break override relationship) - Fix using insertion to respect alphabetical ordering within System.* block (SA1210) - Add test for override async void method (no fix offered) - Add test for missing System.Threading.Tasks using (insertion from scratch) - Add test for alphabetical ordering of System.* usings

Evangelink

Summary

Workflow: Test Expert Reviewer 🧪
Date: 2026-04-30
Repository: microsoft/testfx

Key Findings

The new test coverage is well-structured overall — the switch from EmptyCodeFixProvider to the real fixer is correct, the no-fix delegate/lambda cases are properly verified, and the using-insertion ordering tests (WithoutTaskUsing, UsingsOrderedAlphabetically, MissingTasksUsing) give good confidence in the alphabetical insertion logic.

Three coverage gaps were identified:

Local function + missing using — All local function tests already carry using System.Threading.Tasks;. The EnsureSystemThreadingTasksImportAsync path that adds the using when fixing a local function is never exercised.
virtual async void behavior is unspecified — The fixer excludes override methods but not virtual ones. The existing UseAssertMethodInOverrideAsyncVoidMethod_NoCodeFix test places a diagnostic only on the override, leaving the virtual base method's fixability completely unverified. Changing a virtual async void to virtual async Task has downstream implications (derived class overrides would break), so this path deserves an explicit test.
Multi-diagnostic (multiple Assert calls) in one async void method — The BatchFixer is registered but never exercised with more than one diagnostic per method. A single method with two Assert calls should be tested to verify the batch fix coalesces correctly.

Recommendations

Add a local function test case without using System.Threading.Tasks; to cover the using-insertion path for local functions.
Add a test for virtual async void methods to document and enforce whether the fix applies or is intentionally suppressed.
Add a test with multiple Assert calls in a single async void method to validate BatchFixer behaviour.

Generated by Test Expert Reviewer

🧪 Test quality reviewed by Test Expert Reviewer 🧪

Copilot

Copilot's findings

Files reviewed: 16/16 changed files
Comments generated: 4

Evangelink

Summary

Workflow: Expert Code Reviewer
Date: 2026-04-30
Repository: microsoft/testfx

Key Findings

[Correctness – High] virtual methods are not excluded from the fix (line 51). Changing a virtual async void method to virtual async Task without touching its overrides causes CS0508 compile errors across all derived classes. The override guard is present but the symmetric virtual guard is missing.

[Correctness – High] Explicit interface implementations are not excluded (lines 47–51). A method like async void IFoo.Bar() has no override modifier, so the fix will be offered and applied. Changing the return type to Task for a void-returning interface member produces CS0539, silently breaking compilation.

[Correctness – Medium] EnsureSystemThreadingTasksImportAsync only inspects compilationUnit.Usings (file-level directives), missing using directives placed inside a namespace block. Files using namespace-scoped usings will have a duplicate using System.Threading.Tasks; inserted at file scope, changing file style and potentially triggering duplicate-usings warnings.

Positive Observations

The override exclusion is a good safety guard; the two issues above are close analogues that were missed.
Walking ancestors and breaking cleanly at AnonymousFunctionExpressionSyntax (async) is correct and avoids the hard lambda/delegate type-change problem.
The alphabetical using insertion logic is well-tested and handles the common cases correctly.
BatchFixer is the right FixAllProvider and the shared equivalenceKey ensures idempotent Fix All behavior.

Recommendations

Add !methodDeclaration.Modifiers.Any(SyntaxKind.VirtualKeyword) to the guard on lines 49–51.
Add methodDeclaration.ExplicitInterfaceSpecifier is null to the same guard.
Extend EnsureSystemThreadingTasksImportAsync to also check namespace-scoped usings before inserting at file scope.

Generated by Expert Code Reviewer

🧠 Reviewed by Expert Code Reviewer 🧠

…tFixer - Skip fix for virtual methods (changing breaks derived-class overrides with CS0508) - Skip fix for explicit interface implementations (changing breaks contract with CS0539) - Check namespace-scoped usings to avoid inserting duplicate System.Threading.Tasks import - Handle global:: prefix in using names (avoid duplicates for global::System.Threading.Tasks) - Fix StartsWith("System") → exact "System" or StartsWith("System.") to avoid matching SystemWeb etc. - Add tests: local function + missing using, virtual method (no fix), explicit interface impl (no fix), multi-diagnostic batch fix, namespace-scoped using (no extra import added) Agent-Logs-Url: https://github.com/microsoft/testfx/sessions/4811f646-4f80-4580-9500-cfe4e273c943 Co-authored-by: Evangelink <11340282+Evangelink@users.noreply.github.com>

…espace helper Agent-Logs-Url: https://github.com/microsoft/testfx/sessions/4811f646-4f80-4580-9500-cfe4e273c943 Co-authored-by: Evangelink <11340282+Evangelink@users.noreply.github.com>

Copilot · 2026-04-30T14:39:02Z

Summary

Workflow: Test Expert Reviewer 🧪...

Addressed all findings in 44e8a77 and f6c0efc:

Added UseAssertMethodInAsyncVoidLocalFunction_MissingTasksUsing_AddsUsing covering the local function + missing using path
Added UseAssertMethodInVirtualAsyncVoidMethod_NoCodeFix — virtual methods are now guarded (no fix offered)
Added UseAssertMultipleTimesInAsyncVoidMethod_BatchFix — exercises BatchFixer with two diagnostics in one method
Added UseAssertMethodInExplicitInterfaceImplAsyncVoidMethod_NoCodeFix — explicit interface impl is now guarded

Summary

Workflow: Expert Code Reviewer...

All three high/medium findings addressed in 44e8a77:

virtual guard added alongside override — !methodDeclaration.Modifiers.Any(SyntaxKind.VirtualKeyword)
ExplicitInterfaceSpecifier is null guard added
EnsureSystemThreadingTasksImportAsync now iterates all NamespaceDeclarationSyntax descendants and checks their Usings before inserting at file scope

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

x3yvsblobprodcus370.vsblob.vsassets.io
- Triggering command: /home/REDACTED/work/testfx/testfx/artifacts/bin/MSTest.Analyzers.UnitTests/Debug/net8.0/MSTest.Analyzers.UnitTests /home/REDACTED/work/testfx/testfx/artifacts/bin/MSTest.Analyzers.UnitTests/Debug/net8.0/MSTest.Analyzers.UnitTests --diagnostic --diagnostic-output-directory /home/REDACTED/work/testfx/testfx/artifacts/log/Debug --diagnostic-file-prefix MSTest.Analyzers.UnitTests_net8.0_Debug_x64 --diagnostic-verbosity trace --crashdump --hangdump --hangdump-timeout 15m --report-azdo --coverage --coverage-settings /home/REDACTED/work/testfx/testfx/test/coverage.config --coverage-output MSTest.Analyzers.UnitTests_net8.0_Debug_x64.coverage --filter AvoidUsingAssertsInAsyncVoidContext (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

Configure Actions setup steps to set up my environment, which run before the firewall is enabled
Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Copilot

Copilot's findings

Files reviewed: 16/16 changed files
Comments generated: 2

+        // Check file-level usings and namespace-scoped usings for an existing System.Threading.Tasks import.
+        if (HasSystemThreadingTasksUsing(compilationUnit.Usings))
+        {
+            return document;
+        }
+
+        foreach (NamespaceDeclarationSyntax ns in compilationUnit.DescendantNodes().OfType<NamespaceDeclarationSyntax>())
+        {
+            if (HasSystemThreadingTasksUsing(ns.Usings))
+            {
+                return document;
+            }
+        }
+


+        string code = """
+            using System.Collections;
+            using System.Web;
+            using Microsoft.VisualStudio.TestTools.UnitTesting;
+


…ompat Addresses two outstanding review comments on PR #7892: 1. Multi-namespace bug (review comment #3233748306): The previous `EnsureSystemThreadingTasksImportAsync` returned early on the first namespace declaration that already contained `using System.Threading.Tasks;`, even when the method being fixed was in a *different* namespace without that import — producing uncompilable code. Replace the manual namespace-walking + import-name string matching with a semantic-model-based check: `LookupNamespacesAndTypes(position, "Task")` correctly resolves whether `Task` is in scope at the method's location, uniformly handling file-scoped, namespace-scoped, global, and SDK-implicit usings (including `global::System.Threading.Tasks` and aliases). When not in scope, the using is added to the smallest enclosing block-scoped namespace, falling back to file scope when none exists (covering the file-scoped namespace case, which the build-time Roslyn 3.11 package doesn't expose syntax APIs for). Detect `global using` directives textually so the build-time package doesn't need to expose `UsingDirectiveSyntax.GlobalKeyword`, ensuring the new non-global using is never inserted before existing globals. 2. Test using `System.Web` (review comment #3233748376): `System.Web` is not present in the `ReferenceAssemblies.Net.Net80` test harness. Replace with `System.Xml`. Adds tests pinning: - multi-namespace scope fix (the new behavior), - file-scoped namespace fallback, - BatchFixer across namespaces, - global-using ordering. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Initial plan

0d18f9d

Copilot AI assigned Copilot and Evangelink Apr 28, 2026

Copilot AI requested review from Copilot and removed request for Copilot April 28, 2026 07:01

Copilot started work on behalf of Evangelink April 28, 2026 07:01 View session

Copilot AI linked an issue Apr 28, 2026 that may be closed by this pull request

Add code fix for MSTEST0040 — AvoidUsingAssertsInAsyncVoidContext #7891

Open

Copilot AI requested review from Copilot and removed request for Copilot April 28, 2026 07:17

Copilot AI requested review from Copilot and removed request for Copilot April 28, 2026 07:24

Copilot AI requested review from Copilot and removed request for Copilot April 28, 2026 07:26

Copilot AI changed the title ~~[WIP] Add code fix for MSTEST0040 — Avoid using asserts in async void context~~ Add code fix for MSTEST0040 — AvoidUsingAssertsInAsyncVoidContext Apr 28, 2026

Copilot finished work on behalf of Evangelink April 28, 2026 07:26

Copilot AI requested a review from Evangelink April 28, 2026 07:26

Evangelink marked this pull request as ready for review April 29, 2026 04:43

Copilot AI review requested due to automatic review settings April 29, 2026 04:43

Copilot started reviewing on behalf of Evangelink April 29, 2026 04:43 View session

Copilot AI reviewed Apr 29, 2026

View reviewed changes

github-actions Bot reviewed Apr 29, 2026

View reviewed changes

Comment thread test/UnitTests/MSTest.Analyzers.UnitTests/AvoidUsingAssertsInAsyncVoidContextAnalyzerTests.cs

Comment thread test/UnitTests/MSTest.Analyzers.UnitTests/AvoidUsingAssertsInAsyncVoidContextAnalyzerTests.cs

github-actions Bot requested changes Apr 29, 2026

View reviewed changes

microsoft-github-policy-service Bot added the Needs: Author Feedback label Apr 29, 2026

Copilot started work on behalf of Evangelink April 29, 2026 05:11 View session

microsoft-github-policy-service Bot added Needs: Attention 👋 and removed Needs: Author Feedback labels Apr 29, 2026

Copilot finished work on behalf of Evangelink April 29, 2026 05:18

Evangelink added 2 commits April 30, 2026 15:58

Merge main into copilot/fix-asserts-in-async-void-context

e83ec4a

Copilot AI review requested due to automatic review settings April 30, 2026 14:05

Copilot started reviewing on behalf of Evangelink April 30, 2026 14:08 View session

Evangelink reviewed Apr 30, 2026

View reviewed changes

Copilot AI reviewed Apr 30, 2026

View reviewed changes

Evangelink requested changes Apr 30, 2026

View reviewed changes

Copilot started work on behalf of Evangelink April 30, 2026 14:26 View session

microsoft-github-policy-service Bot added the Needs: Author Feedback label Apr 30, 2026

Copilot AI and others added 2 commits April 30, 2026 14:36

refactor: simplify namespace usings iteration and extract IsSystemNam…

f6c0efc

…espace helper Agent-Logs-Url: https://github.com/microsoft/testfx/sessions/4811f646-4f80-4580-9500-cfe4e273c943 Co-authored-by: Evangelink <11340282+Evangelink@users.noreply.github.com>

Copilot AI requested review from Copilot and removed request for Copilot April 30, 2026 14:38

microsoft-github-policy-service Bot removed the Needs: Author Feedback label Apr 30, 2026

Copilot finished work on behalf of Evangelink April 30, 2026 14:40

Copilot AI requested a review from Evangelink April 30, 2026 14:40

Merge branch 'main' into copilot/fix-asserts-in-async-void-context

0de07bb

Copilot AI review requested due to automatic review settings May 13, 2026 11:19

Copilot started reviewing on behalf of Evangelink May 13, 2026 11:20 View session

Copilot AI reviewed May 13, 2026

View reviewed changes

Conversation

Copilot AI commented Apr 28, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Changes

Example

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Copilot's findings

Uh oh!

Uh oh!

Uh oh!

Uh oh!

github-actions Bot left a comment

Choose a reason for hiding this comment

Summary

Key Findings

Recommendations

Uh oh!

Uh oh!

Uh oh!

github-actions Bot left a comment

Choose a reason for hiding this comment

Summary

Key Findings

Positive Observations

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Evangelink commented Apr 29, 2026

Uh oh!

Copilot AI commented Apr 29, 2026

Uh oh!

Evangelink left a comment

Choose a reason for hiding this comment

Summary

Key Findings

Recommendations

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Copilot's findings

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Evangelink left a comment

Choose a reason for hiding this comment

Summary

Key Findings

Positive Observations

Recommendations

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Copilot AI commented Apr 30, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Summary

I tried to connect to the following addresses, but was blocked by firewall rules:

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Copilot's findings

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Copilot AI commented Apr 28, 2026 •

edited

Loading

Copilot AI commented Apr 30, 2026 •

edited

Loading