Bug triage/2010-08-09

From Second Life Wiki
Jump to navigation Jump to search

Next meeting: 2010-08-09 at 12:00 PM (noon) PDT 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

Misc Pool

Misc Pool

  • VWR-20320 - Votes: 6 - Show in search and set for sale remain enabled after owner changed - Ann Otoole
    • Imported
  • WEB-2494 - Votes: 5 - Verified german paypal account not accepted. - Rene Sciarri
    • Support
  • SVC-5313 - Votes: 4 - Items returned to Lost and Found don't show in inventory until re-log in. - AnnMarie Otoole
    • Imported
  • SVC-6043 - Votes: 2 - Low Sample Rate of Collisions in server 1.40.4 - Les White
    • Resolved - Under Advisement
  • SVC-6058 - Votes: 2 - llGetBoundingBox has gone incorrect since 1.40 released - Aargle Zymurgy
    • Imported
  • VWR-11486 - Votes: 2 - Need to restart SL when connecting and disconnecting headset (USB) - Ethari Hallstrom
    • Imported
  • VWR-11943 - Votes: 2 - Reference Mode Alignment Mis-Match For Path Cut Objects - Cinco Pizzicato
    • Last Triaged date added
  • VWR-13369 - Votes: 2 - Small and zoomed objects (prims) flickering - Kontor Jenkins
    • Last Triaged date added
  • VWR-13591 - Votes: 2 - Sun and moon lighting passes through certain avatar parts, noted on nose and ears. Highlights appear on dark side of face and shadows appear on light side of face. Highlighs also appear inside nose. - Lisa Fossett
    • Resolved - Expected Behavior
  • VWR-14161 - Votes: 2 - Prim hair now appears with halo around semi transparent strands when using 1.23 viewer - Geo Fulton
    • Last Triaged date added
  • VWR-14634 - Votes: 2 - Non-newline whitespace collapsed in local chat - Rex Cronon
    • Resolved - Expected Behavior
  • VWR-15604 - Votes: 2 - Viewer can receive extra root folders as inventory transfer - Adeon Writer
    • Assigned to Soft
  • VWR-15868 - Votes: 2 - Snapshot Freeze-Frame mode not respected by particles, animated textures, and Windlight clouds - Melinda Latynina
    • Last Triaged date added
  • VWR-16195 - Votes: 2 - Non-Trans Texture Eyedropper Duplication - Synaptiq Constantine
    • Assigned to Soft
  • VWR-16326 - Votes: 2 - Random Prims Turning Invisible - Adia Landfall
    • Resolved - Needs more info
  • VWR-16467 - Votes: 2 - Collisions seem unreliable, bullet hitting target using normal SL scripts - Hunter Bronet
    • Moved to SVC,Needs more info
  • VWR-16508 - Votes: 2 - Show Color Under Cursor display shows in snapshots even with Show Interface In Snapshot unchecked - Charlene Trudeau
    • Imported
  • VWR-16559 - Votes: 2 - a big inventory should NOT lag the whole client - TigroSpottystripes Katsu
    • Imported

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/2010-08-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.