Endpoint._make_request namespace detection guard misses text/xml responses
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Aptitud para principiantes
- 50/100
Línea de trabajo
Start in tableauserverclient/server/endpoint/endpoint.py at Endpoint._make_request and compare its Content-Type guard with TSC’s XML_CONTENT_TYPE constant. Review #1046 and PR #1863 to determine whether namespace detection remains needed; done means the chosen path is covered for the relevant XML response type or the obsolete subsystem is removed consistently.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Endpoint._make_request (in tableauserverclient/server/endpoint/endpoint.py) parses the response Content-Type and calls the namespace-detection helper only when it matches:
if content_type == "application/xml":
self.parent_srv._namespace.detect(server_response.content)
Tableau Server emits text/xml (which is what TSC's own XML_CONTENT_TYPE constant is set to), so _namespace.detect() never fires from this path. The pre-existing sign-in path called _namespace.detect() explicitly, so the pre-8.3 namespace fallback still worked there; PR #1848 routes signin through _make_request, which now exposes the bug for signin traffic too.
Two things worth thinking about together:
- The immediate fix: widen the guard to accept both
application/xmlandtext/xml, or (cheaper) just check"xml" in content_typesince detection is idempotent and cheap. - Is the code even reachable? The namespace fallback exists to accept pre-Tableau-8.3 servers that used
http://tableausoftware.com/apiinstead ofhttp://tableau.com/api. TSC'sminimum_supported_server_versionis 2.3, which corresponds to Tableau Server 10.0 (2016). Any server old enough to emit the pre-8.3 namespace is far below the minimum. See #1046 and PR #1863 for a proposed removal of the whole detection subsystem.
If PR #1863 lands, this issue is moot (the whole _namespace.detect call and the Namespace class go away). If it doesn't, we need to fix the guard.
Filed after a fresh-eyes review flagged the guard on PR #1848.
- Lenguaje dominante
- Python
- Estrellas
- 716
- Forks
- 446
- Merge medio
- 8 d 8 h
- PR fusionados (30 d)
- 2
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 tableau/server-client-python
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
tableau/server-client-python#1865 ·
-
in-progress
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
tableau/server-client-python#1829 · 1 comentario ·
-
enhancement gap needs investigation
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
tableau/server-client-python#1322 · 1 comentario ·
-
[Type2] Allow Incremental Refresh type schedules to be added via `server.schedules.add_to_schedule` Abiertohelp wanted Server-Side Enhancement ui-exists
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
tableau/server-client-python#1101 · 3 comentarios ·
-
enhancement good first issue
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
tableau/server-client-python#783 · 5 comentarios ·
Todos los issues de tableau/server-client-python
Issues similares
-
bug confirmed issue
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
open-webui/open-webui#30750 · 1 comentario ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
-
enhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
OpenwaterHealth/openmotion-bloodflow-app#604 · 1 comentario ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
-
good first issue
Dificultad 1/5 Menos de una hora Aptitud para principiantes 90/100