Bug triage/2007-07-02

From Second Life Wiki
Jump to navigation Jump to search


Fast Track Import

(Move bugs here that have solid repros, or valid patches that you have reviewed)

  • IMPORTED SVC-371 - Patch for llOwnerSay (color and grammer) - patch by Thraxis Epsilon
    hot by votes (40+ at the moment). I see this one as legit and good. The default color from the previous patch does suck (almost unreadable) and going back to ": " instead of "say " is also helpful, because some objects use this in forms like "User: activates this or that". I think the "say " was a coding error anyway (fell into a default case). Will include it in my viewer. (NB)
  • VWR-1406 - Unchecking "Go Away/AFK when idle" has no effect in 1.17.2.0 - patch by Henri Beauchamp
    10 votes. The patch reverts llagent.cpp back to 1.17.0. Simple 3-liner to make the debug entry prevent the 30-min logout. I support it (it may be something which someone did intentionally, which personally I don't like, because people will find other and more sim hogging ways to stay online).

Hot by Vote

  • IMPORTED VWR-1225 - Embedded notecards not functioning - patch by Gigs Taggart
    Hot by votes (over 100). I'm not sure about the implications of the patch, but since it's from Gigs, I'm sure it's good enough (I'll include it in my viewer) (NB)
    Eh, the patch is safe to use/merge, but it's kinda a workaround and doesn't completely address the issue. Gigs Taggart 17:01, 30 June 2007 (PDT)

Patches

  • VWR-1420 - IM in chat history is rendered nearly unreadbale now in 1.17.2.0 - color not changeable - patch by Thraxis Epsilon
    Have not checked it in depth yet, but will most likely include it in my viewer (more tests tomorrow) (NB)
  • VWR-1465 - Viewer crash after taking several hi-res snapshots - patch by EponymousDylan Ra
    patch looks straightforward to me and looks like it fits the error he describes. Patch itself may need some tweak for indentation (see my comment there) (NB)


Misc Pool

Community members generally collaborate on the agenda for bug triage meetings. Here's how you can quickly fill in an otherwise blank agenda:


Setting up

  • Go to Bug_Triage/YYYY-MM-DD where YYYY is the four digit year code, MM is the two digit month code, and DD is the day code
  • Write and save {{subst:Triage Template}} as the only content of your new page. This will copy the complete markup from Template:Triage Template as a starting point for your agenda.
  • Fill in the relevant time, date, and location info for the upcoming meeting. The easiest way to do this is to copy the entire block of information from an earlier meeting of the same type (RC, regular, etc...) and modify the date and time as needed.

Populating the issue listings section(s)

<perl>

  1. !/usr/bin/env perl

use XML::Simple;

my $bugs = XMLin($ARGV[0]);

foreach my $item (@{$bugs->{channel}->{item}}) {

 $title = $item->{title};
 $title =~ s/^\^\*\] //;
 $key = $item->{key}->{content};
 $votes = $item->{votes};
 $reporter = $item->{reporter}->{username};
 print "* $key - Votes: $votes - $title - $reporter\n";

}


</perl>

  • Pick a reasonable cutoff point, and copy the output into the appropriate section of your newly created page.