🐛 Bug Report: Client.call raises KeyError when error response omits Content-Type

オープン
#174 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
3/5
見積もり時間
1〜2日
初心者へのやさしさ
35/100
issue の種類
バグ
明瞭さ
明確に書かれている
活発さ
活発
技術スタック
python
領域
api, backend

調査の方向性

Start with the synthetic response reproduction in the issue and inspect appwrite/client.py where Client.call handles the HTTP 502 response. Check how the SDK maps failed responses to AppwriteException, then identify the generator or source that owns this read-only SDK before proposing a change. Done means the missing Content-Type no longer causes KeyError and the original status and body surface through AppwriteException.

索引モデルが issue の本文から書いたものです。

説明

👟 Reproduction steps

With SDK 27.0.0, use a synthetic requests.Response and patch requests.request so no network request is made:

from unittest.mock import patch
from requests import Response
from appwrite.client import Client

response = Response()
response.status_code = 502
response.url = "https://cloud.appwrite.io/v1/synthetic"
response._content = b"upstream unavailable"
response.headers = {}  # valid response without a Content-Type header

with patch("appwrite.client.requests.request", return_value=response):
    Client().call("get", "/synthetic")
👍 Expected behavior

The failed HTTP response should surface as AppwriteException (including its status/body where available), consistent with the SDK's documented error behavior.

👎 Actual Behavior

The call raises KeyError: 'Content-Type' from appwrite/client.py while handling the HTTP 502, hiding the original HTTP failure and bypassing AppwriteException.

🎲 Appwrite version

Different version (specify in environment): SDK package 27.0.0; no live Appwrite server was used.

💻 Operating system

Windows

🧱 Your Environment

CPython 3.13, requests 2.34.2. The reproduction patches the request function and uses only a synthetic response; it sends no network request and uses no credentials.

👀 Have you spent some time to check if this issue has been raised before?
  • I checked and didn't find a similar issue. I reviewed the related client-error report #108 and searched existing issues for Content-Type and KeyError AppwriteException; neither reports this missing-header failure.
🏢 Have you read the Code of Conduct?
  • I have read the Code of Conduct

The SDK README describes this repository as auto-generated, and the repository's bot told PR #162 that direct pull requests are not accepted. I'm reporting the reproducible behavior here rather than editing generated code; please route the fix through the appropriate generator/source if applicable.

主要言語
Python
スター
265
フォーク
68
平均マージ
5時間 2分
マージ済み PR(30日)
8

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

appwrite/sdk-for-python のほかの issue

appwrite/sdk-for-python の issue をすべて見る

似ている issue

Python の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。