Maxim Cherednik

We are experiencing the same issue since recently. After looking into the codebase we have a guess that it is related to this line of code:  **What is happening:**...

1. Within 1 test nothing is been executed after the server is disposed. 2. We can not run those test cases sequentially. It does not make any sense for us....

> There are no problems with LibLog, exception is arising from Microsoft's log provider that was disposed. It is not a problem, it is a design limitation of the LibLog....

Any plans to replace the LibLog with the _Microsoft.Extensions.Logging_?

Was struggling with the upgrade from 6.3.0 to 7.0.0 After the upgrade the parameter of the node was double quoted by default. ```C# NodeExe($"{yarnCommand}", workingDirectory: path, logger: LogErrorAsWarning); ``` I...

>Is your suggestion that everything should just outright fail in this scenario? I guess, as a user I would prefer this. At least it would be an expectation from a...

Another, probably similar issue in that area is on this line: https://github.com/xunit/xunit/blob/3f3f6929c301db40e9d5d8ced2bb494084f57c82/src/xunit.execution/Sdk/Frameworks/Runners/XunitTestAssemblyRunner.cs#L125 I understand that this is a design decision, but I guess it is very easy to make a...

Wanted to dive into the Castle Core code base, but then realized that FakeItEasy uses slightly older version of it. Any plans to bump the dependency? Maybe the issue does...

A bit more info which might give us a lead. I was analysing the test failures and decided to compare the ones which are the same. What I found is...

I have another question(lead). I am thinking now that I might be using dummies incorrectly. I thought dummies are the cheap fakes. So if I have a dependency, but not...