Bug Report: UnicodeDecodeError when limit_bytes truncates UTF-8 mid-character
Los mantenedores suelen responder en 1 día
Evaluación
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Aptitud para principiantes
- 68/100
Línea de trabajo
Start with kubernetes/client/rest.py at the UTF-8 decode in request, then inspect the response handling and tests for preloaded content. Reproduce with a response ending in an incomplete UTF-8 sequence and confirm ordinary invalid UTF-8 still behaves as intended. Done means a byte-limited pod log no longer raises UnicodeDecodeError when truncation splits a character.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Summary
When using read_namespaced_pod_log() with _preload_content=True and limit_bytes parameter, the client raises UnicodeDecodeError if the byte limit cuts a multi-byte UTF-8 character in the middle.
Environment
- kubernetes-client version: 36.0.3 (also occurs in versions < 36.0.0)
- Python version: 3.12
- Operating System: Linux
Problem Description
The limit_bytes parameter works at the byte level and can cut a multi-byte UTF-8 character mid-sequence. When _preload_content=True (the default), the client attempts to decode the truncated byte stream as UTF-8 in rest.py:232, which raises UnicodeDecodeError.
Root Cause
In kubernetes/client/rest.py, line 232:
r.data = r.data.decode('utf8')
This assumes:
- The response is valid UTF-8
- The byte stream is complete
However, the Kubernetes API /api/v1/namespaces/{namespace}/pods/{name}/log endpoint:
- Returns logs as a byte stream with no encoding specified (content-type: text/plain)
- The
limitBytesparameter cuts at byte boundaries, not character boundaries - Can therefore return incomplete UTF-8 sequences when the limit is reached
Evidence
Stack Trace
File "/opt/app-root/lib/python3.12/site-packages/kubernetes/client/rest.py", line 232, in request
r.data = r.data.decode('utf8')
^^^^^^^^^^^^^^^^^^^^^
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xc2 in position 10485759: unexpected end of data
Analysis
- Position 10485759: This is exactly 10MB - 1 byte (10485760 = 10 * 1024 * 1024)
- Byte 0xc2: Start of a 2-byte UTF-8 sequence (continuation byte missing)
- The error occurs precisely at the
limit_bytesboundary
Full Call Stack
File "/opt/app-root/lib/python3.12/site-packages/kubernetes/client/api/core_v1_api.py", line 24264, in read_namespaced_pod_log
return self.read_namespaced_pod_log_with_http_info(name, namespace, **kwargs)
File "/opt/app-root/lib/python3.12/site-packages/kubernetes/client/api/core_v1_api.py", line 24387, in read_namespaced_pod_log_with_http_info
return self.api_client.call_api(...)
File "/opt/app-root/lib/python3.12/site-packages/kubernetes/client/api_client.py", line 348, in call_api
return self.__call_api(resource_path, method, ...)
File "/opt/app-root/lib/python3.12/site-packages/kubernetes/client/api_client.py", line 180, in __call_api
response_data = self.request(...)
File "/opt/app-root/lib/python3.12/site-packages/kubernetes/client/api_client.py", line 373, in request
return self.rest_client.GET(url, ...)
File "/opt/app-root/lib/python3.12/site-packages/kubernetes/client/rest.py", line 244, in GET
return self.request("GET", url, ...)
File "/opt/app-root/lib/python3.12/site-packages/kubernetes/client/rest.py", line 232, in request
r.data = r.data.decode('utf8')
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xc2 in position 10485759: unexpected end of data
Reproduction
from kubernetes import client, config
config.load_kube_config()
v1 = client.CoreV1Api()
# This will fail if limit_bytes cuts a UTF-8 character mid-sequence
try:
log = v1.read_namespaced_pod_log(
name="pod-with-large-logs",
namespace="default",
limit_bytes=10 * 1024 * 1024, # 10 MB
_preload_content=True, # Default
)
except UnicodeDecodeError as e:
print(f"Error at position {e.start}: {e.reason}")
# Output: Error at position 10485759: 'utf-8' codec can't decode byte 0xc2
Proposed Solutions
Option 1: Handle Incomplete UTF-8 (Recommended)
Modify rest.py:232 to handle incomplete UTF-8 sequences:
# Current code:
r.data = r.data.decode('utf8')
# Proposed fix:
r.data = r.data.decode('utf8', errors='ignore') # Or 'replace'
Or better, strip incomplete sequences at the end:
def safe_decode_utf8(data):
"""Decode UTF-8, handling incomplete sequences at the end."""
try:
return data.decode('utf8')
except UnicodeDecodeError as e:
# If error is at the end, try truncating incomplete sequence
if e.start >= len(data) - 4: # UTF-8 max 4 bytes
return data[:e.start].decode('utf8', errors='strict')
raise
Impact
This affects any application using:
read_namespaced_pod_log()withlimit_bytes- Default
_preload_content=True - Pod logs containing non-ASCII characters (common in error messages, stack traces)
References
- Related issue: #2596 (different manifestation of string handling in v36.x)
- Discussion: https://gitlab.cee.redhat.com/ccx/ccx-ocp-core/-/merge_requests/1146
Expected Behavior
The client should handle incomplete UTF-8 sequences gracefully, OR
Actual Behavior
The client raises an unhandled UnicodeDecodeError that propagates to the application.
- Lenguaje dominante
- Python
- Estrellas
- 7.7k
- Forks
- 3.5k
- Merge medio
- 1 d 9 h
- PR fusionados (30 d)
- 25
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de kubernetes-client/python
-
getheaders is deprecated in urllib3 >= 2.0.0Quizá libre de nuevo Un pull request para esta issue se cerró sin fusionarse. Abiertokind/bug
Dificultad 1/5 Menos de una hora Aptitud para principiantes 68/100
kubernetes-client/python#2280 · 18 comentarios · 9 reacciones ·
Los mantenedores suelen responder en 1 día
-
kind/feature
Dificultad 4/5 3-5 días Aptitud para principiantes 48/100
kubernetes-client/python#2764 ·
Los mantenedores suelen responder en 1 día
-
Resolve inconsistent typing in 37.0.0 delete operationsPosiblemente ocupada @tamird la tomó hoy. Abiertokind/feature
Dificultad 4/5 3-5 días Aptitud para principiantes 55/100
kubernetes-client/python#2752 · 8 comentarios ·
Los mantenedores suelen responder en 1 día
-
Make async an extraPosiblemente ocupada @jdork0 la tomó hace 6 días. Abiertokind/feature
Dificultad 2/5 1-3 horas Aptitud para principiantes 55/100
kubernetes-client/python#2739 · 3 comentarios · 1 asignado ·
Los mantenedores suelen responder en 1 día
-
Growing library sizePosiblemente ocupada Un pull request vinculado a esta issue está abierto o ya se fusionó. Abiertohelp wanted
Dificultad 5/5 Más de una semana Aptitud para principiantes 35/100
kubernetes-client/python#2677 · 16 comentarios · 1 reacción ·
Los mantenedores suelen responder en 1 día
Todos los issues de kubernetes-client/python
Issues similares
-
area/profiles comp/cli P3 type/feature
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
NousResearch/hermes-agent#146372 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
Los mantenedores suelen responder en 1 día
-
[oblt-aw][autodoc] Document obs-aw-automerge contract and fix automerge doc inconsistenciesPosiblemente ocupada @github-actions la tomó hoy. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
Los mantenedores suelen responder en 1 día
-
GeoSeries scale and skew tests fail with pytest 9.2.0Posiblemente ocupada @jiayuasu la tomó hoy. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
Los mantenedores suelen responder en 1 día
-
admission-deferred priority: medium status: ready work-class: scoped
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
melodic-software/claude-code-plugins#10887 · 4 comentarios ·
Los mantenedores suelen responder en 1 día