debug info & actual output emitted on stdout #456

Open
opened 2022-02-02 12:10:09 +00:00 by noerw · 0 comments
Member

describe your environment

describe the issue (observed vs expected behaviour)

The output NOTE: no gitea login detected, falling back to login 'foo' (and other debug info) disturbs other command output, thus should be emitted on stderr.

This specific note shows up in most commands and seems a bit too verbose to show up by default, we should remove or hide it by default.

related: #207

### describe your environment - tea version used (`tea -v`): 0.8.0 - [x] I also reproduced the issue [with the latest master build](https://dl.gitea.io/tea/master) - operating system: gnu/linux ### describe the issue (observed vs expected behaviour) The output `NOTE: no gitea login detected, falling back to login 'foo'` (and other debug info) disturbs other command output, thus should be emitted on stderr. This specific note shows up in most commands and seems a bit too verbose to show up by default, we should remove or hide it by default. related: #207
noerw added the
kind
enhancement
label 2022-02-02 12:10:09 +00:00
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: gitea/tea#456
No description provided.