Component

cli

Describe the bug

• login as woodpecker admin user (via gitea) ✔️
• see and use API Access Token via swagger ✔️
• connection of cli to server using the woodpecker user token works ✔️
• getting list of users shows one single empty line ❌
  • used command docker compose run cli user ls
• adding new user using cli successful ✔️
  • used command docker compose run cli user add joe
    • output Successfully added user joe
  • creation of user verfied in swagger
  • user is able successfully loign into woodpecker (via gitea)
• getting list of users shows two empty lines now ❌
  • used command docker compose run cli user ls
• deleting new user using cli successful ✔️
  • used command docker compose run cli user rm joe
    • output Successfully removed user joe
• getting list of users shows one empty line again ❌
  • used command docker compose run cli user ls

My assumption is that communication with the API works fine, and the issue is only in the rendering output part.
I have tired to pass --pretty and --log-level trace arguments but without any effect.

System Info

services:
  svc:
    image: woodpeckerci/woodpecker-server:v2.0.0
    environment:
    - WOODPECKER_ROOT_PATH=/woodpecker
    - WOODPECKER_ADMIN=woodpecker
    ...not relevant...
    networks:
      lan:

  cli:
    image: woodpeckerci/woodpecker-cli:v2.0.0
    env_file:
    - $DATA/cli.secrets
    environment:
    - WOODPECKER_SERVER=http://svc:8000/woodpecker/
    networks:
      lan:

Additional context

No response

Validations

• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Checked that the bug isn't fixed in the next version already [https://woodpecker-ci.org/faq#which-version-of-woodpecker-should-i-use]
• Check that this is a concrete bug. For Q&A join our Discord Chat Server or the Matrix room.