add underlying cause for `TransportError` · googleapis/google-cloud-python

(2 件のコメント) (0 件のリアクション) (0 人の担当者)Python (1,481 件のフォーク)batch import

help wantedpriority: p3type: feature request

Repository metrics

Is it possible to save a reference to the last exception thrown at:

and use it to build a more meaningful error message? at:

that way the underlying reason for the TransportError would be available even if DEBUG logging level is not enabled.

調査方針: The issue suggests modifying the TransportError to include the underlying cause. The relevant code is in google/auth/compute engine/ metadata.py around line 204 and 217-220. A contributor should capture the last exception before raising TransportError and use Python's exception chaining (e.g., `raise ... from exc`) to preserve it. The change is small and localized.
技術スタック: python
領域: backend
Issue 種別: 機能
難度: 2
推定時間: 1時間未満
活動状況: 新着
明確さ: 明確
前提条件: なし
初心者向け度: 80