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

Aberta
#174 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
3/5
Tempo estimado
1-2 dias
Facilidade para iniciantes
35/100
Tipo de issue
Bug
Clareza
Claramente especificada
Status de atividade
Ativa
Stack de tecnologia
python
Domínio
api, backend

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

👟 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.

Linguagem predominante
Python
Estrelas
265
Forks
68
Merge médio
5h 2min
PRs com merge (30d)
8

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de appwrite/sdk-for-python

Todas as issues de appwrite/sdk-for-python

Issues semelhantes

Mais issues de Python

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.