[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-panel-devel
Subject:    Re: DrKonqi and BKO
From:       Martin Klapetek <martin.klapetek () gmail ! com>
Date:       2016-11-01 17:42:53
Message-ID: CAPLgePrMAQ0tWCbKPB0_fsg4W+g9B6kTzmw0zpPpMW-kUHTsUQ () mail ! gmail ! com
[Download RAW message or body]

On Tue, Nov 1, 2016 at 6:24 AM, David Edmundson <david@davidedmundson.co.uk>
wrote:

> On Tue, Nov 1, 2016 at 9:28 AM, René J.V. Bertin <rjvbertin@gmail.com>
> wrote:
>
>> Hi,
>>
>> Sorry if this has already been answered somewhere where I've missed it:
>>
>> DrKonqi has lost much of its interest (in v5.8.2) due to recent changes
>> in BKO. Most of the crashes I've been trying to report via the tool have
>> led to rejection because of an overzealous spam filter, and now because
>> there's a (new? lowered?) max. limit of 64k characters per comment.
>> Evidently an inline backtrace can be much longer than that.
>>
>> I do agree that it'd be better for readability to put backtraces in an
>> attachment;
>>
>
> As attachments is awful. You cannot search if it's in an attachment.
> Searching is ridiculously important.
>

For improving readability, there is bugzilla-traceparser plugin, that can
dynamically
hide looooooooong backtraces with a bit of JS magic to expand them and much
more
like finding duplicates and also auto-dupe. I still think this would help
tremendously to
all our bugzilla users.

See https://bugs.kde.org/show_bug.cgi?id=354217

Cheers
-- 
Martin Klapetek

[Attachment #3 (text/html)]

<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Tue, Nov 1, 2016 \
at 6:24 AM, David Edmundson <span dir="ltr">&lt;<a \
href="mailto:david@davidedmundson.co.uk" \
target="_blank">david@davidedmundson.co.uk</a>&gt;</span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div \
class="gmail_quote"><span class="gmail-">On Tue, Nov 1, 2016 at 9:28 AM, René J.V. \
Bertin <span dir="ltr">&lt;<a href="mailto:rjvbertin@gmail.com" \
target="_blank">rjvbertin@gmail.com</a>&gt;</span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex">Hi,<br> <br>
Sorry if this has already been answered somewhere where I&#39;ve missed it:<br>
<br>
DrKonqi has lost much of its interest (in v5.8.2) due to recent changes in BKO. Most \
of the crashes I&#39;ve been trying to report via the tool have led to rejection \
because of an overzealous spam filter, and now because there&#39;s a (new? lowered?) \
max. limit of 64k characters per comment.<br> Evidently an inline backtrace can be \
much longer than that.<br> <br>
I do agree that it&#39;d be better for readability to put backtraces in an \
attachment; <br></blockquote><div><br></div></span><div>As attachments is awful. You \
cannot search if it&#39;s in an attachment. </div></div>Searching is ridiculously \
important.<br></div></div></blockquote><div><br></div><div>For improving readability, \
there is bugzilla-traceparser plugin, that can dynamically</div><div>hide \
looooooooong backtraces with a bit of JS magic to expand them and much \
more</div><div>like finding duplicates and also auto-dupe. I still think this would \
help tremendously to</div><div>all our bugzilla users.</div><div><br></div><div>See  \
<a href="https://bugs.kde.org/show_bug.cgi?id=354217">https://bugs.kde.org/show_bug.cgi?id=354217</a></div><div><br></div><div>Cheers</div></div>-- \
<br><div class="gmail_signature"><div dir="ltr"><div><div><span \
style="color:rgb(102,102,102)">Martin Klapetek</span></div></div></div></div> \
</div></div>



[prev in list] [next in list] [prev in thread] [next in thread]