[Bug 11115] New: "Please do not PASTE logs and back traces" message is ignored too often
http://bugs.winehq.org/show_bug.cgi?id=11115
Summary: "Please do not PASTE logs and back traces" message is ignored too often Product: WineHQ Bugzilla Version: unspecified Platform: All OS/Version: All Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: bugzilla-unknown AssignedTo: jnewman@codeweavers.com ReportedBy: jeffzaroyko@gmail.com
It could be that the way the Enter Bug page is designed, this message is not prominent enough for everyone to perceive its importance.
maybe it could be larger to place more emphasis on the message or alternatively feature a stop sign graphic next to it saying something like "STOP, read this."
http://bugs.winehq.org/show_bug.cgi?id=11115
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever Confirmed|0 |1
--- Comment #1 from Austin English austinenglish@gmail.com 2008-01-10 10:15:47 --- Perhaps we could have some way of detecting that a _huge_ amount of info was pasted in there and/or the format of the backtrace?
http://bugs.winehq.org/show_bug.cgi?id=11115
Jeremy Newman jnewman@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|jnewman@codeweavers.com |wine-bugs@winehq.org
http://bugs.winehq.org/show_bug.cgi?id=11115
--- Comment #2 from Nah iamtheoneb4ne1else@hotmail.com 2008-02-02 06:40:52 --- Since Im guilty, a simple regex for /fixme/ would be a good start ;) That should catch 90% of logs
http://bugs.winehq.org/show_bug.cgi?id=11115
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jan.wine@zerebecki.de
http://bugs.winehq.org/show_bug.cgi?id=11115
--- Comment #3 from Kai Blin blin@gmx.net 2008-02-03 00:43:41 --- If you just grep for "fixme", youll have to match a couple of times before you tell the user to attach a log. If there's five lines of log total, I'd rather see that in the bug description than having to open an attachment.
http://bugs.winehq.org/show_bug.cgi?id=11115
--- Comment #4 from Jeff Zaroyko jeffzaroyko@gmail.com 2008-02-03 03:03:14 --- (In reply to comment #3)
If you just grep for "fixme", youll have to match a couple of times before you tell the user to attach a log. If there's five lines of log total, I'd rather see that in the bug description than having to open an attachment.
Yes, I agree with this, I think that the simplest and quickest fix would be to increase the size of the text and either change the colour to red or include an image like this:
http://openclipart.org/Xiph/files/ryanlerch/2972
http://bugs.winehq.org/show_bug.cgi?id=11115
--- Comment #5 from Austin English austinenglish@gmail.com 2008-02-03 16:18:55 --- (In reply to comment #3)
If you just grep for "fixme", youll have to match a couple of times before you tell the user to attach a log. If there's five lines of log total, I'd rather see that in the bug description than having to open an attachment.
Grep for fixme & total lines > 25? Then pop up a warning?
http://bugs.winehq.org/show_bug.cgi?id=11115
Dan Kegel dank@kegel.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |dank@kegel.com
--- Comment #6 from Dan Kegel dank@kegel.com 2008-02-04 06:39:00 --- Back in July, I suggested this to the guy doing the Bugzilla customization. He said the easiest place to do it would be in Javascript on the bug submission form.
For starters, a good regexp to trigger the error might be ((fixme|trace|err):.*){12,}|(Register dump.*(ELF){4,})
http://bugs.winehq.org/show_bug.cgi?id=11115
Jeff Zaroyko jeffzaroyko@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED
--- Comment #7 from Jeff Zaroyko jeffzaroyko@gmail.com 2008-02-20 15:34:28 --- patch applied - let's see how this works out.
http://bugs.winehq.org/show_bug.cgi?id=11115
--- Comment #8 from Dan Kegel dank@kegel.com 2008-02-22 11:30:27 --- What does your patch do - just add the stop sign?
Does it use a regexp to catch bad submissions before they happen?
http://bugs.winehq.org/show_bug.cgi?id=11115
--- Comment #9 from Austin English austinenglish@gmail.com 2008-02-22 13:57:32 --- (In reply to comment #8)
What does your patch do - just add the stop sign?
Does it use a regexp to catch bad submissions before they happen?
Just adds the stop sign. regexp would be a great addition, but a STOP sign is a great step in the right direction... http://source.winehq.org/git/bugzilla.git/?a=commitdiff;h=a064f3ce75b6674a4d...
http://bugs.winehq.org/show_bug.cgi?id=11115
Ken Sharp kennybobs@o2.co.uk changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED |
--- Comment #10 from Ken Sharp kennybobs@o2.co.uk 2009-05-27 19:45:27 --- Reopening...
This still occurs far too often. How about a CAPITAL BOLD STATEMENT IN RED? Or something more drastic...
http://bugs.winehq.org/show_bug.cgi?id=11115
--- Comment #11 from Jeff Zaroyko jeffz@jeffz.name 2009-05-27 19:54:37 --- (In reply to comment #10)
Reopening...
This still occurs far too often. How about a CAPITAL BOLD STATEMENT IN RED? Or something more drastic...
If someone ignores the current message, they're likely to ignore any other message too, thinking it doesn't apply to them. Even if we do a js alert after trying some heuristic on the textfield the user could still blindly discard it.
I think since I added the stop sign, there has been very few people pasting logs.
http://bugs.winehq.org/show_bug.cgi?id=11115
--- Comment #12 from Ken Sharp kennybobs@o2.co.uk 2009-05-27 20:36:34 --- It still happens every day...
http://bugs.winehq.org/show_bug.cgi?id=11115
--- Comment #13 from Jeff Zaroyko jeffz@jeffz.name 2009-05-27 20:49:17 --- (In reply to comment #12)
It still happens every day...
Can you link to some examples that you think are inappropriate? I watch the wine-bugs mailing list and can only remember maybe one in the past few months that was excessive.
http://bugs.winehq.org/show_bug.cgi?id=11115
--- Comment #14 from Austin English austinenglish@gmail.com 2009-05-27 22:36:04 --- (In reply to comment #13)
(In reply to comment #12)
It still happens every day...
Can you link to some examples that you think are inappropriate? I watch the wine-bugs mailing list and can only remember maybe one in the past few months that was excessive.
It's cut down quite a bit since you added the stop sign, yes, but Wine's gotten more popular and more bug reports are coming in.
There is usually a pasted log every day or two.
http://bugs.winehq.org/show_bug.cgi?id=11115
--- Comment #15 from Austin English austinenglish@gmail.com 2009-05-28 10:21:02 --- (In reply to comment #13)
(In reply to comment #12)
It still happens every day...
Can you link to some examples that you think are inappropriate? I watch the wine-bugs mailing list and can only remember maybe one in the past few months that was excessive.
Here was one today: http://bugs.winehq.org/show_bug.cgi?id=18670#c4
http://bugs.winehq.org/show_bug.cgi?id=11115
--- Comment #16 from Dan Kegel dank@kegel.com 2009-05-28 10:28:51 --- That was added as a comment later, and in that interface, there's no stop sign. We could add a stop sign to the warning above the "Additional Comments" field. It'd be kind of ugly, but might work. Maybe a smaller stop sign than the one we use for the new bug form.
http://bugs.winehq.org/show_bug.cgi?id=11115
--- Comment #17 from Austin English austinenglish@gmail.com 2009-05-28 10:39:08 --- (In reply to comment #16)
That was added as a comment later, and in that interface, there's no stop sign. We could add a stop sign to the warning above the "Additional Comments" field. It'd be kind of ugly, but might work. Maybe a smaller stop sign than the one we use for the new bug form.
Ah, you're right. I'll keep my eye out for new bugs with logs.
I'm still a fan of the regexp, personally...
http://bugs.winehq.org/show_bug.cgi?id=11115
--- Comment #18 from Ken Sharp kennybobs@o2.co.uk 2009-05-28 13:30:31 --- I can't remember off-hand any bugs, as I get hundreds of emails every day.
http://bugs.winehq.org/show_bug.cgi?id=18670#c4 has already been mentioned, but ths guy was already told what to do in the comment before it, and he just plain ignored it.
Maybe a character or line limit can be set on the bugs? Of course, this would mean disabling the limit for certain groups of users, who post a lot of *useful* detail in their replies.
http://bugs.winehq.org/show_bug.cgi?id=11115
John Haywards normandy@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |normandy@web.de
--- Comment #19 from John Haywards normandy@web.de 2009-05-28 15:44:57 --- Just a quick idea, don't know how to realize/whether it's possible, but what about some (better) "pastebin" integration?
When I was new to wine, I wanted to post _all info_ I've got, but the attachment-function needed more time than simply pasting it. Maybe a _fast_ integration would help, e.g.: show only the first few lines of a pasted code and a link to sth. like pastebin.winehq.org?
The posting interface would need another quick interface for adding sources/logs without going to another page/subsystem...? BBCode-style/linkage/regexp?
As I said before, 've got no idea how to realize a quicker log-attachment (paste into a input-field in browser vs. paste into editor, save to disk, upload to winehq), but maybe you've got an idea how to speed the process up...
http://bugs.winehq.org/show_bug.cgi?id=11115
--- Comment #20 from Jeff Zaroyko jeffz@jeffz.name 2009-10-15 04:40:35 --- Still happening... Vitaliy did send a patch with a regexp to stop this happening, but iirc it was not applied.
bug 19305 bug 20357
http://bugs.winehq.org/show_bug.cgi?id=11115
zil zilforever@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |zilforever@gmail.com
--- Comment #21 from zil zilforever@gmail.com 2010-05-26 11:54:54 --- Maybe just count number of rows. If more than 20 or 30 display error 'Are trying to paste logs or back traces? If yes put them into attachment'. Such validation is simple, I use it on pages when i dont want people to post long vertical text. It works very well.
Somebody make posts with big number of lines that are not logs or back traces?
The big red sign 'STOP' is not enough.
http://bugs.winehq.org/show_bug.cgi?id=11115
--- Comment #22 from Vitaliy Margolen vitaliy@kievinfo.com 2010-05-26 22:15:56 --- (In reply to comment #21)
Maybe just count number of rows. If more than 20 or 30 display error 'Are trying to paste logs or back traces?
Tried that - AJ rejected the patch.
http://bugs.winehq.org/show_bug.cgi?id=11115
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Platform|All |Other OS/Version|All |other
--- Comment #23 from Austin English austinenglish@gmail.com 2012-02-23 15:19:46 CST --- Removing deprecated 'All' Platform/OS.
http://bugs.winehq.org/show_bug.cgi?id=11115
André H. nerv@dawncrow.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |nerv@dawncrow.de
--- Comment #24 from André H. nerv@dawncrow.de 2012-03-03 06:36:07 CST --- Did the situation changed with the new crash dialog (save backtrace)?
http://bugs.winehq.org/show_bug.cgi?id=11115
Jerome Leclanche adys.wh@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED CC| |adys.wh@gmail.com Resolution| |WONTFIX
--- Comment #25 from Jerome Leclanche adys.wh@gmail.com 2012-03-12 18:31:25 CDT --- According to comment #22 there is pretty much nothing we can do about it.
http://bugs.winehq.org/show_bug.cgi?id=11115
Jerome Leclanche adys.wh@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #26 from Jerome Leclanche adys.wh@gmail.com 2012-03-12 18:31:32 CDT --- Closing
-
wine-bugs＠winehq.org