Bug triage/2010-03-01

Next meeting: 2010-03-01 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

• SVC-5409 - Votes: 103 - Unix time epoch and llGetUnixTime() is inconsistent between sims. - NeoBokrug Elytis
  • Imported
• SVC-5428 - Votes: 51 - High Packet loss, Rubberbanding, Script runtime stops, various other issues since 1.36.2 emergency release. - Karoline Merlin
  • Resolved - Fixed
• VWR-17467 - Votes: 38 - Content being copy/mod, yet people unable to mod. - Ceri Kesten
  • Resolved - Needs More info

Misc Pool

Misc Pool

• SVC-5445 - Votes: 3 - Mono script in Stopped state loses its Mono compiled result (and mono checkbox) after sim restart ! - maeva anatine

• VWR-17034 - Votes: 0 - HTTP Scripts are not responding - Kero Yifu

• SVC-5440 - Votes: 5 - On logging into Second Life, I recieve an error msg. (Unable to connect to simulator). I am sent to another region due to another msg I recieve (region is not available). This happens whether I am logging back in at last location or at Home Location. - Foxx Pawpad

• VWR-12014 - Votes: 2 - Some Mac keyboard shortcuts are essentially wrong - Nava Muni

• VWR-12870 - Votes: 2 - Logging out of linux Viewer hangs computer - Corin Clary

• SVC-3005 - Votes: 4 - Can not sit on unscripted prims inside the bounding box of a phantom prim. - Les White

• SVC-3935 - Votes: 4 - llKey2Name returns text "(Loading...)" instead of empty string or avatar name - Cenji Neutra

• VWR-12103 - Votes: 4 - "Stop all animations" does not stop animations with joint offsets (aka "deformers") - Adeon Writer

• VWR-1416 - Votes: 4 - Renaming a new inventory item while filtering item names renames parent folder instead. - Poeffie Messmer

• VWR-16338 - Votes: 4 - rendervolumeLODfactor default setting of 1.125 is too low - Siddean Munro

• VWR-3198 - Votes: 4 - Windlight footshadows look strange sometimes - Funk Schnook

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.

Blog/Forum issues - will be triaged by blog team:

• MISC-3954 - Votes: 177 - Teen grid under threat of Copybotted content, economy gets crushed and Report system doesn't work anymore because of great scale. - Ruud Carpool
  • Resolved - Under Advisement
• VWR-17038 - Votes: 28 - Current Outfit Folder Glitch - Serenity Semple
  • Resolved - Dupicate of VWR-17195.
• WEB-1499 - Votes: 7 - SLA/Blogs missing Eyeroll Emote - Void Singer
• WEB-1532 - Votes: 7 - New replies to extremely long discussion forum threads are not appearing - Milla Janick
• WEB-1488 - Votes: 4 - Missing right click behavior for Blog/SLA editor - Void Singer
• WEB-1506 - Votes: 4 - Blog/SLA/Forum: Impossible to turn of email notifications of private messages - Void Singer
• WEB-1489 - Votes: 3 - Blog/SLA Layout - Void Singer
• WEB-1483 - Votes: 2 - Blog/SLA Tags Clouds do not include sub category tag clouds - Void Singer

Transcript

Transcript is/will be at Bug triage/2010-03-01/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)

• Look at the results of one of these queries
  • General triage: "Viewer 2 Bug Triage" (sorted by LL ID, Created, Last Triaged):
    • https://jira.secondlife.com/secure/IssueNavigator.jspa?mode=hide&requestId=12724
  • UI triage:
    • https://jira.secondlife.com/secure/IssueNavigator.jspa?mode=hide&requestId=10470 (The selected filter with id '10470' does not exist.)

  (Note: there's no hard and fast rule that says these are the only valid queries. If you feel there's a better query one particular week, use that.)

• Save a copy of the XML version of the query
• Run this perl script on the xml file

<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.

• if you do not have access to a perl interpreter. There is a ported version of the script on PHP, located here: http://jirafiller.technokittydevelopment.com/ made by roberto salubrius