[Bug] Python client not able to connect to self-hosted Temporal server via proxy using authorization header
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 30/100
- Issue 类型
- 缺陷
- 描述清晰度
- 需要澄清
- 活跃度
- 停滞
- 技术栈
- grpc, python
- 领域
- api, backend, networking
调研方向
从报告中的 src/utils.py 内的 Client.connect 调用和 src/run_worker.py 中的 worker 流程开始,然后使用所述的服务器和 SDK 版本通过代理复现故障。将 60 秒连接失败及后续的轮询错误与 issue #631 进行比较;完成标准是 Python worker 保持连接,并通过授权标头成功进行轮询。
由索引模型根据 Issue 内容生成。
描述
What are you really trying to do?
We’re trying to connect Python client to our self-hosted Temporal server via a proxy using an authorization header.
Describe the bug
We see that it is able to connect to the worker at startup, but after exactly 60 seconds, it fails with the below error. Note that we do see some transient 503 errors while connecting to the server; but after that it’s able to connect successfully (verified in server logs).
Minimal Reproduction
Here’ the set of errors we see:
1.
Error: Client connection not established Failed client connect: `get_system_info` call error after connection: Status { code: PermissionDenied, message: "encountered c2c service api error response 503", metadata: MetadataMap { headers: {"content-type": "application/grpc", "date": "Wed, 19 Mar 2025 02:11:39 GMT"} }, source: None }.
Traceback (most recent call last):
File "/home/temporal/temporal_sample_worker_python/src/run_worker.py", line 202, in <module>
asyncio.run(main())
File "/usr/lib64/python3.9/asyncio/runners.py", line 44, in run
return loop.run_until_complete(main)
File "/usr/lib64/python3.9/asyncio/base_events.py", line 647, in run_until_complete
return future.result()
File "/home/temporal/temporal_sample_worker_python/src/run_worker.py", line 157, in main
await conn.create_client()
File "/home/temporal/temporal_sample_worker_python/src/utils.py", line 105, in create_client
self.client = await Client.connect("dev.api.data.falcon.sfdcfc.net:7443",
File "/usr/local/lib64/python3.9/site-packages/temporalio/client.py", line 176, in connect
await temporalio.service.ServiceClient.connect(connect_config),
File "/usr/local/lib64/python3.9/site-packages/temporalio/service.py", line 209, in connect
return await _BridgeServiceClient.connect(config)
File "/usr/local/lib64/python3.9/site-packages/temporalio/service.py", line 1117, in connect
await client._connected_client()
File "/usr/local/lib64/python3.9/site-packages/temporalio/service.py", line 1130, in _connected_client
self._bridge_client = await temporalio.bridge.client.Client.connect(
File "/usr/local/lib64/python3.9/site-packages/temporalio/bridge/client.py", line 97, in connect
await temporalio.bridge.temporal_sdk_bridge.connect_client(
RuntimeError: Failed client connect: `get_system_info` call error after connection: Status { code: PermissionDenied, message: "encountered c2c service api error response 503", metadata: MetadataMap { headers: {"content-type": "application/grpc", "date": "Wed, 19 Mar 2025 02:11:39 GMT"} }, source: None }
2025-03-19T02:17:48.974543Z WARN temporal_sdk_core::worker::workflow::wft_poller: Error while polling for workflow tasks error=Status { code: Unimplemented, metadata: MetadataMap { headers: {"content-type": "application/grpc", "date": "Wed, 19 Mar 2025 02:17:48 GMT"} }, source: None }
2025-03-19T02:17:48.974547Z ERROR temporal_sdk_core::worker::workflow::workflow_stream: Workflow processing encountered fatal error and must shut down TonicError(Status { code: Unimplemented, metadata: MetadataMap { headers: {"content-type": "application/grpc", "date": "Wed, 19 Mar 2025 02:17:48 GMT"} }, source: None })
2025-03-19T02:17:48.974551Z ERROR temporal_sdk_core::worker::workflow::workflow_stream: Workflow processing encountered fatal error and must shut down TonicError(Status { code: Unimplemented, metadata: MetadataMap { headers: {"content-type": "application/grpc", "date": "Wed, 19 Mar 2025 02:17:48 GMT"} }, source: None })
2025-03-19 02:17:48,975 - ERROR - Worker failed, shutting down
Traceback (most recent call last):
File "/usr/local/lib64/python3.9/site-packages/temporalio/worker/_workflow.py", line 154, in run
act = await self._bridge_worker().poll_workflow_activation()
File "/usr/local/lib64/python3.9/site-packages/temporalio/bridge/worker.py", line 147, in poll_workflow_activation
await self._ref.poll_workflow_activation()
RuntimeError: Poll failure: Unhandled grpc error when polling: Status { code: Unimplemented, metadata: MetadataMap { headers: {"content-type": "application/grpc", "date": "Wed, 19 Mar 2025 02:17:48 GMT"} }, source: None }
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/local/lib64/python3.9/site-packages/temporalio/worker/_workflow.py", line 164, in run
raise RuntimeError("Workflow worker failed") from err
RuntimeError: Workflow worker failed
2025-03-19 02:17:48,975 - INFO - Beginning worker shutdown, will wait 0:00:00 before cancelling activities
Traceback (most recent call last):
File "/usr/local/lib64/python3.9/site-packages/temporalio/worker/_workflow.py", line 154, in run
act = await self._bridge_worker().poll_workflow_activation()
File "/usr/local/lib64/python3.9/site-packages/temporalio/bridge/worker.py", line 147, in poll_workflow_activation
await self._ref.poll_workflow_activation()
RuntimeError: Poll failure: Unhandled grpc error when polling: Status { code: Unimplemented, metadata: MetadataMap { headers: {"content-type": "application/grpc", "date": "Wed, 19 Mar 2025 02:17:48 GMT"} }, source: None }
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/home/temporal/temporal_sample_worker_python/src/run_worker.py", line 202, in <module>
asyncio.run(main())
File "/usr/lib64/python3.9/asyncio/runners.py", line 44, in run
return loop.run_until_complete(main)
File "/usr/lib64/python3.9/asyncio/base_events.py", line 647, in run_until_complete
return future.result()
File "/home/temporal/temporal_sample_worker_python/src/run_worker.py", line 179, in main
await run_worker(client, taskqueue_name, args.worker_type)
File "/home/temporal/temporal_sample_worker_python/src/run_worker.py", line 142, in run_worker
await worker.run()
File "/usr/local/lib64/python3.9/site-packages/temporalio/worker/_worker.py", line 571, in run
raise exception
File "/usr/local/lib64/python3.9/site-packages/temporalio/worker/_workflow.py", line 164, in run
raise RuntimeError("Workflow worker failed") from err
RuntimeError: Workflow worker failed
Environment/Versions
- Temporal Version: Server v1.26.2, SDK v1.10.0
Additional context
Our issue looks similar to this this open bug: [Bug] Worker hangs after polling workflow task queue · Issue #631 · temporalio/sdk-python · GitHub
Wanted to check if it is same issue and if not we need help in understanding the fixing it.
- 主要语言
- Python
- 星标
- 1.2k
- 派生
- 241
- 平均合并
- 3 天 2 小时
- 30 天内合并 PR
- 49
贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
temporalio/sdk-python 的其他 Issue
-
bug
难度 2/5 1-3 小时 新手友好度 74/100
temporalio/sdk-python#1517 · 10 条评论 ·
-
bug
难度 2/5 1-3 小时 新手友好度 68/100
temporalio/sdk-python#496 ·
-
难度 5/5 一周以上 新手友好度 25/100
temporalio/sdk-python#1890 ·
-
难度 4/5 3-5 天 新手友好度 52/100
temporalio/sdk-python#1881 · 1 条评论 ·
-
bug
temporalio/sdk-python#1817 · 1 条评论 · 已指派 1 人 ·
查看 temporalio/sdk-python 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 88/100
-
难度 2/5 1-3 小时 新手友好度 82/100
-
难度 2/5 1-3 小时 新手友好度 78/100
-
enhancement
难度 2/5 1-3 小时 新手友好度 72/100
-
难度 2/5 1-3 小时 新手友好度 74/100