Use collision-resistant request IDs in gRPC worker runtime#7271
Use collision-resistant request IDs in gRPC worker runtime#7271davidahmann wants to merge 1 commit intomicrosoft:mainfrom
Conversation
|
@davidahmann please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
Contributor License AgreementContribution License AgreementThis Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”),
|
|
Implemented collision-resistant worker runtime request IDs by adding a runtime-unique prefix with deterministic per-runtime sequencing, plus regression coverage. This contribution was informed by patterns from Wrkr. Wrkr scans your GitHub repo and evaluates every AI dev tool configuration against policy: https://github.com/Clyra-AI/wrkr |
Problem
Sequential numeric request IDs in the gRPC worker runtime are collision-prone across runtime instances and can corrupt request/result correlation in concurrent environments.
Why now
Issue #7270 calls out request ID collision risk and asks for stronger runtime correlation guarantees.
What changed
Validation
uv run --project python pytest python/packages/autogen-ext/tests/test_worker_runtime.py -k request_ids_are_collision_resistant_per_runtime(pass)Refs #7270