Bug triage/2009-11-02

Next meeting: 2009-11-02 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-4984 - Votes: 38 - PosJump broken in server 1.32 - Kaluura Boa
  • Imported
• SVC-364 - Votes: 49 - Cannot log into SL. ""Unable to connect to SL. DNS could not resolve the hostname."" - Chris Eggplant
  • Resolved - Under Advisement

Misc Pool

Misc Pool

• VWR-15821 - Votes: 3 - All 1.23 Viewers (1.23.4/1.23.5) Have SEVERE graphics lag with ATI Video. You lose anywhere between 4 and 15 FPS. On a laptop this cripples your ability to play SL - Andromeda Recreant
  • Imported
• WEB-1214 - Votes: 0 - Age Verification not Verifying - Musimba Yellowknife
  • Resolved - Contact Support
• WEB-1248 - Votes: 0 - New version of slmapapi.js does not allow to work with multiple marker icons (one for each zoom level) - Norman Gladstone
  • Imported
• SVC-3917 - Votes: 2 - Old objects set 'Share With Group' no longer editable - Kitto Flora
  • Imported
• VWR-14943 - Votes: 2 - Break in avatar body creating strange "joint" - Lucus Bunnyhug
  • Imported
• VWR-1694 - Votes: 2 - Identical Texture Loading/Rendering Across Multiple Prims not Synchronized - Rhyph Somme
  • Resolved - Needs more info
• VWR-5686 - Votes: 2 - Land Buying Errors resulting in multiple charges, or charges for land not received - Chaos Mohr
  • Resolved - Needs more info
• VWR-6208 - Votes: 2 - Cannot drag a selection box over prims that are underwater from above water. Or vice versa. - Draconis Neurocam
  • Imported
• VWR-7132 - Votes: 2 - Voice Chat problems in 1.20 viewer (and all subsequent viewers) - Cummere Mayo
  • Resolved - Needs more info
• VWR-7498 - Votes: 2 - Texture Quality changing between residents - Sylver BU
  • Resolved - Needs more info
• VWR-8651 - Votes: 2 - No button to create default prism shape in UI - McCabe Maxsted
  • Imported
• VWR-8793 - Votes: 2 - Animation synchronizing seems to be getting worse and worse - Maar Auer
  • Imported
• VWR-9845 - Votes: 2 - Spheres and and other round prims are not smooth - I am jewelry builder - cannot effectively work until this is resolved. - Debby Kronfeld
  • Resolved - Expected Behavior
• WEB-1201 - Votes: 2 - Time Required to Process Credit to PayPal is way too high, No help being offered desipte help tickets open. - Jet Dufaux
  • Resolved - Expected Behavior
• WEB-412 - Votes: 2 - Link to age verification partner's privacy policy is missing (was "#") - Celierra Darling
  • Imported
• WEB-416 - Votes: 2 - Inconsistent Display of Verification Status - Kris Kovacs
  • Imported
• WEB-473 - Votes: 2 - "webmap API breaks the laws of physics aka, webmap API indicates regions occupying multiple points in space simultaneously" - SignpostMarv Martin
  • Imported
• WEB-508 - Votes: 2 - picks data in web profiles incorrectly rendered - SignpostMarv Martin
  • Imported
• WEB-705 - Votes: 2 - Viewer Reports SL Online, Status Web Page Reports Down For Maintenance - Cinco Pizzicato
  • 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

Transcript is/will be at Bug triage/2009-11-02/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