CommandAppTester.Output will produce MemoryOverflow when capturing a Rule output

[MrBogomips]

Information

• OS: MacOS
• Version: Darwin 22.3.0
• Terminal: iTerm

Describe the bug
I was testing a command that produces some Rules.
Accessing to CommandAppResult.Output will produce a MemoryOverflow.

To Reproduce
Supposing your Command Under Test will write a Rule on the output, it would suffice to assert. For example:

// Arrange
var sut = GetCommandAppTester();

// Act
var result = sut.Run("ThisDemoDoesntExist");

// Assert
result.ExitCode.Should().Be(-1);
result.Output.Should().Contain("no demo found matching your criteria.");  // Throws

Expected behavior
Simply works as expected :)

Additional context
Removing the Rule all the tests worked.

---

Please upvote 👍 this issue if you are interested in it.

[Blackbaud-CameronBeacham]

Any update on this? I just had to remove the usage of Rule from my app because the CommandAppTester breaks.