540164 - Improve console outputs

Status: ASSIGNED

(Developer Services :: Mercurial: qimportbz, defect)

Comment 1

[Serge Gautherie (:sgautherie)]

Attachment: (Av1) Just do it

*s/print "Warning: /bug.settings.ui.warn/ to sync with the rest of the code.
*Bug fetching: remind bug number, be more readable in case of errors.

Comment 2

[Rob Arnold [:robarnold]]

Comment on attachment 422001 [details] [diff] [review]
(Av1) Just do it

I like the print change and displaying the bug number when fetching.

I don't like the new style of splitting the "Doing x" "done" messages onto separate lines. It makes it unnecessarily more verbose. You could just eliminate the "done" messages if that's more appealing but do we really need to change it?

Comment 3

[Serge Gautherie (:sgautherie)]

(In reply to comment #2)

Do we actually care for 1-2 more lines?
Getting the errors on the "Parsing..." line is more a concern, I think.
If you do want 1 line only, I could only do the opposite: remove the "..." line and merge it with the "Done" line :-|

Example of the issue from bug 533890:
"Parsing...** unknown exception encountered, details follow"

Comment 4

[Rob Arnold [:robarnold]]

(In reply to comment #3)
> (In reply to comment #2)
> 
> Do we actually care for 1-2 more lines?
I think it looks much nicer.

> Getting the errors on the "Parsing..." line is more a concern, I think.
> If you do want 1 line only, I could only do the opposite: remove the "..." line
> and merge it with the "Done" line :-|
> 
> Example of the issue from bug 533890:
> "Parsing...** unknown exception encountered, details follow"

I do like this. A nicer looking message would be something like "Parsing...failed. Details follow:". I think the asterisks are rather unsightly.

Comment 5

[Sylvestre Ledru [:Sylvestre]]

Greg, is qimportbz still a thing? :)
Thanks!

Comment 6

[Gregory Szorc [:gps]]

qimportbz is still a thing. The code has been on life support for years. I'm surprised it has continued to apparently work with so little testing and supervision.