Refresh emulator inactivity timeout on SDK-retried responses (blocked on SDK enhancement)
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
Read the shell's OperationProgressHandler implementation and how it is registered with the Cosmos SDK; the issue does not name file paths. First check whether the SDK enhancement Azure/azure-cosmos-dotnet-v3#6178 is available, since this work is explicitly blocked on it. Once available, implement per-attempt timeout refresh while excluding synthesized timeouts, then add a test with repeated 429 responses exceeding the timeout and verify the command completes.
由索引模型根据 Issue 内容生成。
描述
Summary
OperationProgressHandler (added in #264) restarts the local-emulator inactivity timeout whenever the emulator returns a response. It is registered as a Cosmos SDK custom handler, and the SDK places custom handlers before its RetryHandler, so the handler sees only the final response of an operation, not the intermediate responses the SDK retries (for example 429).
Impact
A throttled operation against the local emulator can stay inside the SDK retry loop for longer than the 10-second inactivity limit. With the SDK's default rate-limit policy (up to 9 retries, up to 30 seconds of waiting), the shell can cancel the command and disconnect even though the emulator answered every attempt. Earlier writes remain committed. This only affects local-emulator connections; Azure accounts have no inactivity timeout.
Plan
- Request a supported per-attempt response notification from the SDK (Gateway and Direct, without changing custom-handler semantics): Azure/azure-cosmos-dotnet-v3#6178.
- Once it ships, use it in the shell to restart the inactivity timeout on each real response, still excluding SDK-synthesized timeouts, so stalled requests keep timing out.
- Add a test that simulates repeated 429 responses longer than the timeout and verifies the command completes.
This does not block current releases; integrate it in the first shell release after the SDK change is available.
- 主要语言
- C#
- 星标
- 4
- 派生
- 7
- 平均合并
- 2 天 2 小时
- 30 天内合并 PR
- 24
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
Azure/CosmosDBShell 的其他 Issue
-
[bug-bash] print maps a missing item's HTTP 404 to exit 1 instead of documented not-found exit 5未关闭bug bug-bash
难度 2/5 1-3 小时 新手友好度 78/100
Azure/CosmosDBShell#279 ·
维护者通常 1 天内回复
-
bug bug-bash
难度 3/5 1-2 天 新手友好度 75/100
Azure/CosmosDBShell#281 ·
维护者通常 1 天内回复
-
bug bug-bash
难度 3/5 1-2 天 新手友好度 68/100
Azure/CosmosDBShell#280 ·
维护者通常 1 天内回复
-
[bug-bash] edit and theme failures silently return exit 1 without a machine-readable stderr error未关闭bug bug-bash
难度 3/5 1-2 天 新手友好度 62/100
Azure/CosmosDBShell#278 ·
维护者通常 1 天内回复
-
bug bug-bash
难度 3/5 1-2 天 新手友好度 75/100
Azure/CosmosDBShell#277 ·
维护者通常 1 天内回复
查看 Azure/CosmosDBShell 的全部 Issue
相似的 Issue
-
bug untriaged
难度 2/5 1-3 小时 新手友好度 67/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 65/100
CarlosAdrianM/Nesto#610 ·
-
area/resource-registry status/triage
难度 1/5 1-3 小时 新手友好度 76/100
Altinn/altinn-auth#4821 ·
维护者通常 1 天内回复
-
a11y community:contribution
难度 2/5 1-3 小时 新手友好度 74/100
microsoft/fluentui-blazor#5590 · 1 条评论 ·
维护者通常 1 天内回复
-
bug mcp small
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复