Bug triage/2008-01-09

From Second Life Wiki
Jump to navigation Jump to search

Next meeting: 2008-01-09 at 3pm PST at Bridie Linden's house.


(Bugs reported in Release Candidate — consider for import?, sorted by votes)

Hot by Vote

  • SVC-389 - Votes: 13 - Avatar unseated by changes to PRIM_TYPE with llSetPrimitiveParams() - Qie Niangao
    • Imported - Assigned to Dan Linden
  • VWR-1286 - Votes: 19 - alt-zooming on hollow face mishandled - Lex Neva
    • Last Triaged date added
  • VWR-4068 - Votes: 24 - Streaming MP3 file from Comcast does not work anymore and blocks any audio streaming until next Re-log. - Raster Teazle
    • Leaving as-is
  • SVC-905 - Votes: 12 - Crippling Lag since upgrading to Mac OSX 10.5 (Leopard) - Uccello Poultry
    • Imported - Assigned to Aric Linden
  • VWR-2950 - Votes: 12 - Group Notices and Group IMs Constantly Malfunctioning - wayfinder wishbringer
    • Last Triaged date added
  • VWR-3399 - Votes: 11 - Invisiprims Visible (and flickering) in Windlight - Shoshana Epsilon
    • Imported - Assigned to Pastrami Linden
  • SVC-573 - Votes: 26 - Logged out by system during every teleport - Juniskorpi Oldbull
    • Closed - Duplicate of SVC-972
  • SVC-1061 - Votes: 23 - Some link sets spontaneously unlink when taken and rezzed - Lex Neva
    • Last Triaged date added
  • VWR-3871 - Votes: 15 - Prim position appears to be off, but script show it in the right place. When right click and edit, it moves to where it should be kinda - mandyfox falta
    • Imported - Assigned to Aric Linden

High Voted Bugs


  • VWR-3093 - Votes: 13 - Allow MU* (MUCK, MUSH, MUX, MUD) like ""poses"" (=IRC emotes) in chat and IMs. - Henri Beauchamp
    • Imported - Assigned to Aric Linden
  • VWR-3877 - Votes: 3 - A nasty possible memory overwrite and two minor leaks - Nicholaz Beresford
    • Imported - Assigned to triage
  • SVC-1020 - Votes: 9 - New search does not accept Japanese inputs - SakuraNoel Fayray
    • Closed - Duplicate of SVC-4010
  • VWR-4057 - Votes: 1 - Multi-line chat display bug - first character in line missing - Domchi Underwood
    • Imported - Assigned to Triage


Misc Pool

Misc Pool

Pre-meeting activity

Some issues will be resolved in the course of building this agenda. Rather than deleting them from the proposed agenda, move the issue and associated discussion into the appropriate section below.


  • VWR-3948 - Votes: 17 - Cannot take off underwear. (No, seriously!) - Suspected check for teen grid going wrong? - Ron Crimson
  • VWR-4014 - Votes: 0 - navigateToLocalPage() assumes that the html files are in language subfolders - Michelle2 Zenovka
  • VWR-3993 - Votes: 0 - Grid selector of ReleaseNoOpt build doesn't work properly on new login screen - Alissa Sabre
  • VWR-4125 - Votes: 0 - Duplicate names in XUI files make some translated UI texts to show inappropriately - Alissa Sabre



Transcript is/will be at Bug Triage/2008-01-09/Transcript

Creating An Agenda

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)


  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";



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