Forum member

arkiaconsulting

55 posts

Posts by arkiaconsulting

  1. Rebuild with restore MCP ability

    Forget about it, I'll review my harness before making such assumption. Thanks for the release.

  2. Rebuild with restore MCP ability

    LGTM, thanks @Remco PS: would be a good thing if the agent had a way to make sure that there were restores since its last changes. Maybe a 'restored' property or so ?

  3. Rebuild with restore MCP ability

    Thanks Remco, will test this release today. I'm working in a quite large solution with several application components those days, and package upgrade is often needed for various reasons (new library, new library version, vulnerabilities in existing libraries...). In terms of frequency, I would sa…

  4. Rebuild with restore MCP ability

    Each time an agent changes an existing package version, the nCrunch build fails. It's cache is probably out-of-date. The MCP server should provide a way for the agent to trigger a restore or a full build with restore. For now the only solution is to stop and recreate a new nCrunch session. PS:…

  5. MCP server suddenly failed to reply to ping

    Thanks Remco, no immediate problem.

  6. MCP server suddenly failed to reply to ping

    Thanks Remco, installed and tested. No more ping issue, but the console no longer logs anything. Is it expected ?

  7. MCP server suddenly failed to reply to ping

    Today I don't reproduce the tools unavailability on Copilot restart, probably a transient failure somewhere... However, the ping unsupported method is still there. (Copilot Cli updated to 1.0.93-1)

  8. MCP server suddenly failed to reply to ping

    Hi @Temco, starting from September 5th, the MCP server started to issue the following in response to the keep-alive ping RPC request: [quote] System.InvalidOperationException: Unsupported method: ping at NCrunch.MCP.McpJsonRpcServer.HandleRequest(JsonRpcRequest request) at NCrunch.MCP…

  9. Console tool does not handle long paths

    Thanks @Remco. I just found it weird that nCrunch (VS 2026) was able to build, whereas nCrunch (console) wasn't.

  10. Console tool does not handle long paths

    I'm using nCrunch console and MCP from my AI agent client, by using git worktrees. when in a worktree, I get a System.IO.PathTooLongException. [quote] System.IO.PathTooLongException: The path 'D:\WK\11480\51\.worktrees\feat-worktree-cuddly-goggles\<long_path_that_i_cannot_sorten>\MyClass.g.cs' …

  11. MCP Server - WaitForEngineWorkCompleted times out

    When trying to launch the tests of a whole test class, the agent tries to call [b]RunTests[/b] with the following payload: [code] { "categories": [ "Unit" ], "fixtureName": "RollbackBackupsPageTests", "sessionId": "03485b9c440f4b2787f5279626e59098" } [/code] That results with…

  12. MCP Server - WaitForEngineWorkCompleted times out

    Thanks @Remco. The agent succeeded in finding the covering tests at first try.

  13. MCP Server - WaitForEngineWorkCompleted times out

    About [b]GetTestsCoveringLine[/b], my agent cannot use it correctly. Here is what it says: [quote] **Root cause: an nCrunch MCP tool-contract defect, not a test coverage issue.** - `GetFileDetails` confirms that `RollbackBackups.razor.cs:280` is covered by one test. - `GetTestsCoveringLine` …

  14. MCP Server - WaitForEngineWorkCompleted times out

    Thanks for always kind support !

  15. MCP Server - WaitForEngineWorkCompleted times out

    For instance, it fails on the following test method: [code] [Fact(DisplayName = "GetRollbackOperations returns persisted rollback operations indexed by instance")] public async Task Test03() ... [/code]

  16. MCP Server - WaitForEngineWorkCompleted times out

    I observed 2 pitfalls in the way the agent is using RunTests. [b]RunTests[/b] To run a test, it first tries by method name [code]"fullNameRegex": "^My\\.Project\\.Namespace\\.TestClass\\.<test_method_name>$"[/code] but it get an error saying that no test were found. So it's forced to run GetTe…

  17. MCP Server - WaitForEngineWorkCompleted times out

    Thanks Remco, looks better. My agents says the bug is fixed ^^ Do we agree that the following response is expected, for instance when child projects do not build ? [code] {"CurrentState":"Idle","SolutionFilePath":"<redacted>","LoadedProjectCount":54,"BuildFailureCount":1,"ProcessedTaskCount"…

  18. MCP Server - WaitForEngineWorkCompleted times out

    Install in progress

  19. MCP Server - WaitForEngineWorkCompleted times out

    Hi @Remco, Question: how is it possible that this tool `WaitForEngineWorkCompleted` reports being Idle whereas some tasks are still processing/unprocessed ? [code] {"CurrentState":"Idle","SolutionFilePath":"<redacted>","LoadedProjectCount":54,"BuildFailureCount":0,"ProcessedTaskCount":46,"Tas…

  20. MCP Server - WaitForEngineWorkCompleted times out

    I think that I found the reason. When working with the console MCP, when the agent starts a new session, all the tests are launched which in my case is a long running task as I also have integration tests. So I changed the console tool configuration file adding the flag [quote]<TestsToExecuteAut…