[BUG]Eventhubs namespace update notifications can cause MCP tool timeouts
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 3.7k
- Forks
- 624
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 220
Description
Describe the bug
The EventHubs namespace update (and any other LRO) may take several minutes to complete. Currently LRO tools and the WaitForLroCompletionAsync call in the service base class don't emit progress notifications to the MCP client, which can cause the client to time out the request when it's just taking a long time to complete.
Expected behavior
Long running operations shouldn't trigger a timeout if they are still ongoing.
Actual behavior
Long running operations can trigger timeouts in clients.
Reproduction Steps
Start a long running operation that's going to take more than 5 minutes to complete.
Environment
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the LRO tools and the WaitForLroCompletionAsync call in the service base class, then reproduce an operation that takes more than five minutes. Check how MCP clients receive progress notifications while the operation remains active; done means an ongoing long-running operation no longer causes the client request to time out.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100