Bug triage/2009-07-06

From Second Life Wiki
Jump to navigation Jump to search

Next meeting: 2009-07-06 at 12:00 NOON SLT at Hippotropolis Meeting area.. See Bug triage for details.

Fast Track Import

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

Hot by Vote

High Voted Bugs

No issues over 10 votes!

Misc Pool

Misc Pool

  • WEB-1091 - Votes: 5 - OpenID Login Process for XStreetSL.com fails with Opera browser (and sometimes others) - Zuza Ritt
    • Imported
  • SVC-2273 - Votes: 4 - Scripts randomly shutting themselves off - eren padar
    • More Information Needed
  • VWR-5832 - Votes: 4 - Gradual Crash - Network Data fall to Zero - Crash Logger does not detect crash - Aphrodite Tagore
    • Resolved - Needs More Information
  • WEB-397 - Votes: 4 - Login screen web page is erroneously cached - ZigZag Freenote
    • Resolved - Needs More Information
  • MISC-154 - Votes: 3 - "Multiplicity of actions and orders on the avatar, as well as words in chat and IMs" - Sunayu Dagostino
    • Resolved - Contact Support
  • SVC-1574 - Votes: 3 - physical objects embed themselves in other objects and get 'stuck' - Darek Deluca
    • Resolved - Needs More Information
  • SVC-1966 - Votes: 3 - Perms spontaneously change on object once it's rezzed by new owner. - Esch Snoats
    • Rresolved - Needs More Information
  • SVC-2337 - Votes: 3 - "Spambots destroying quality of life, limit free account IMs per day." - IntLibber Brautigan
    • Resolved - Under Advisement
  • SVC-890 - Votes: 3 - llAttachToAvatar() can cause a stack/heap collision in certain circumstances - Lex Neva
    • Imported
  • VWR-14176 - Votes: 3 - Uneven Textures version 1.23 Appears to effect Alpha textures with texture changing script. - Nisa Maverick
    • Imported
  • VWR-14301 - Votes: 2 - Viewer crashes immediately on changing screen mode (Linux) - Morgaine Dinova
    • Imported
  • WEB-1110 - Votes: 2 - xstreetsl.com allows accounts presumably banned from the Second Life service to log in - Ann Otoole
    • Imported
  • MISC-1931 - Votes: 1 - Mono Sim crashes with SLaccountant of libsl or other botprograms - Navar Harbinger
    • Imported
  • SVC-1801 - Votes: 1 - llSetLocalRot() not always working on Havok4 sims - Jupiter Ducatillon
    • resolved - Needs More Information
  • SVC-2661 - Votes: 1 - totally unseeable prims - Saiki Spirt
    • Imported
  • SVC-3078 - Votes: 1 - Temp Objects are being removed too early. Somtimes instantly. - darling brody
    • Resolved - Expected Behavior
  • SVC-3412 - Votes: 1 - "Inventory Loss -- When will SL understand what the word ""Transaction"" means ?" - Carl Wilder
    • Resolved - Duplicate of SVC-114

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.




Transcript is/will be at Bug triage/2009-07-06/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.