microsoft / microsoft/durabletask-dotnet
No cache invalidation on options change
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 193
- Forks
- 60
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 4
Description
gRPC channels are cached per configuration (endpoint, task hub, credential type, etc.). If options are changed after the first channel is created (e.g. via IOptionsMonitor.OnChange or options reload), the cached channel is not updated and will keep using the original configuration until the process restarts or the service provider is disposed.
Contributor guide
No contributing guide indexed for this repository
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 where gRPC channels are cached per configuration and how IOptionsMonitor.OnChange or options reload flows through that path. Check the behavior after options change and define completion as cached channels no longer retaining the original configuration until process restart or service-provider disposal.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, grpc
- Domain
- backend-api-design
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100