Bug triage/2007-12-03

From Second Life Wiki
Jump to navigation Jump to search

Next meeting: 2007-12-3 at 12pm at Hippotropolis. See Bug triage for details.

Fast Track Import

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

  • VWR-3590 - Votes: 2 - Using NVidia drivers 169.09 BETA causes Windlight to render shiny objects as either invisible or transparent - SunShine Kukulcan
Somewhat time sensitive.
    • Imported - Assigned to Windlight
This broke my linked vendorwall, it's a confirmed regression.
    • Imported - Assigned to Triage

Hot by Vote

  • VWR-3171 - Votes: 44 - Local Lighting Exposure in Windlight seems to be greatly lessened. - Aradia Dielli
    • Imported - Assigned to Pastrami Linden
  • SVC-459 - Votes: 13 - De-Link on Border Crossing - Smith Fizz
    • Cross-linked to existing Jira


  • VWR-3093 - Votes: 3 - Allow MU* (MUCK, MUSH, MUX, MUD) like ""poses"" (=IRC emotes) in chat and IMs. - Henri Beauchamp
Triaged last week, but no linden feedback given. Gigs Taggart
  • VWR-3480 - Votes: 1 - Version 1.5 of c-ares has additional parameter on callback - Michelle2 Zenovka
    • Imported - Assigned to Triage
  • VWR-3605 - Votes: 1 - Object group display not properly set for no-group objects - Tateru Nino
    • Same as VWR-2982/DEV-6595. Cross linked
  • SVC-689 - Votes: 1 - LSL: run_jumpif, run_jumpnif do not properly handle lists with only a single entry - Strife Onizuka
    • Imported - Assigned to Soft Linden

Misc Pool

  • MISC-421 - Votes: 5 - High value transactions not being delivered - Inigo Chamerberlin
    • Imported - Assigned to Hamilton Linden
  • MISC-559 - Votes: 1 - When I log into SL, I stay connected for about 15 seconds and then my entire internet crashes. - jewells infinity
    • Closed - Directed to Support
  • MISC-661 - Votes: 5 - Give avatars a REASON why their avatar has been flagged by the Second Life Risk API. - Rosen Janus
    • Imported - Assigned to Aric Linden
  • MISC-664 - Votes: 2 - Massive packet loss in last few days - Hazel Homewood
    • Resolved - Needs More Info. Asked if this is still a problem
  • MISC-672 - Votes: 3 - communication tutorial problem - korin soderstrom
    • Imported - Assigned to Aric Linden
  • MISC-737 - Votes: 1 - SL closes my internet connection - Nikola Monentes
    • Closed - Needs More Info.
  • MISC-744 - Votes: 0 - SL movement restricted to turning around in circles - Casper leinhardt
    • Fixed
  • MISC-746 - Votes: 0 - Second Life crashes around 2 minutes after connection is made - miguel mumfuzz
    • Closed - Needs More Info
  • MISC-748 - Votes: 1 - Group ownership problem regarding objects on group land... - Quik Taurog
    • Closed - Directed to Support. This is not a bug
  • SVC-581 - Votes: 5 - Object Permissions broken and being reset - Montana Corleone
    • Imported - Assigned to Aric Linden
  • SVC-602 - Votes: 5 - llInstantMessage never arrives if the scripted object name is 23 characters and the message is 64 characters - Triple Peccable
    • Imported - Assigned to Aric Linden

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-3548 - Votes: 1 - Cannot Ban a person from land that has profile hidden in search - Teemu Sands
This sounds serious Gigs Taggart
Warkirby says this bug is bogus.


Transcript is/will be at Bug triage/2007-12-03/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.