bug: createsiteusers/deletesiteusers line counts and output format incorrect
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Aptitud para principiantes
- 68/100
Línea de trabajo
Start with the summary block in tabcmd/commands/user/create_site_users.py and the output handling in tabcmd/commands/user/delete_site_users_command.py. Compare both commands with the expected tabcmd 1 output described here, including processed and skipped counts, error counts, duplicate lines, and error details. Done means both commands produce consistent summaries with accurate counts and formatted errors.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Summary
createsiteusers and deletesiteusers show incorrect line counts and inconsistent output format, discovered during live server output comparison testing (2026-07).
createsiteusers — "Lines skipped" shows error count, not skipped count; output inconsistent with tabcmd 1
Current output (error case):
Lines processed: 1
Lines skipped: 1
Number of users added: 0
Error details:
['ServerResponseError']
Expected (tabcmd 1):
===== Lines processed: 1
Lines skipped: 0
Number of users added: 1
Number of errors: 0
Lines skipped is being populated with number_of_errors instead of a genuine skip count. There is no separate "Number of errors" line. The error_list is logged as a raw Python list rather than formatted per-line.
Location: tabcmd/commands/user/create_site_users.py — summary block at the end of run_command.
deletesiteusers — "Lines processed" shows 0 even when a user was attempted
Current output:
Lines processed: 0
404: Item not found
Item not found: [Users] [email protected]
Lines processed: 0
Number of errors: 1
Error details:
Issues:
Lines processed: 0even though 1 user was attempted- "Lines processed" appears twice
- Empty "Error details:" section despite an error being shown above it
- Blank lines and indented error text mixed into the summary block
Location: tabcmd/commands/user/delete_site_users_command.py
Relationship to #429
Issue #429 item 4 fixes the createsiteusers error message format (str(e) instead of e.__class__.__name__). The counting and structural output issues are tracked here separately.
- Lenguaje dominante
- Python
- Estrellas
- 52
- Forks
- 17
- Merge medio
- 5 d 20 h
- PR fusionados (30 d)
- 2
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Sin 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 tableau/tabcmd
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
-
feat: publish missing --description flag from tabcmd ClassicPosiblemente ocupada Un pull request vinculado a esta issue está abierto o ya se fusionó. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
-
feat: creategroup missing --role flag from tabcmd ClassicPosiblemente ocupada Un pull request vinculado a esta issue está abierto o ya se fusionó. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
Todos los issues de tableau/tabcmd
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 62/100
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 70/100
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
topoteretes/cognee#5773 ·
Los mantenedores suelen responder en 1 día
-
MiKTeX: a failed build reports no errors because texify --quiet switches the log to file:line: styleAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
SublimeText/LaTeXTools#1718 ·