Bug triage/2009-02-23

From Second Life Wiki
Jump to: navigation, search



Next meeting: 2009-02-16 at 12:00 PM SLT at Hippotropolis Meeting areaD. 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

Patches

Patches

Misc Pool

Misc Pool

  • SVC-758 - Votes: 2 - Assigning key as list element at declare time in the global scope converts it to a string. - Siann Beck
    • Old issue, no recent updates. GW (T|C) -- 06:50, 15 February 2009 (UTC)
    • Issue reopened and updated after this resolution --Harleen Gretzky 18:35, 15 February 2009 (UTC)
  • VWR-2987 - Votes: 0 - Inventory > Library > Textures > Sculpt Textures > Surface Textures > orange 1 should be stem 2 - Daedalus Young
    • Old issue, no recent updates. GW (T|C) -- 06:50, 15 February 2009 (UTC)
    • Checked, issue still exists in RC 1.22.9 --Harleen Gretzky 18:58, 15 February 2009 (UTC)
  • VWR-4315 - Votes: 2 - When I try to click on one of my HUD objects, meant to respond, it doesn't, and if I give a command to a tool/gadget, meant to recognize it, it dosn't - Steven Wilberg
    • See also VWR-8215 - Votes: 7 - After login, sometimes Mouse steering on avatar and HUDs don't work (discussed during Bug Triage 2009/02/12) - Opensource Obscure
  • SVC-3813 - Votes: 1 - Selecting "Share with group" fails if "Transfer" is not enabled. - Aargle Zymurgy
  • VWR-9204 - Votes: 1 - Clicking the mute button from a dialog when receiving a landmark or a notecard (spam) will crash the viewer if there are pending notifications behind the dialog - Tasty Tiramisu
  • VWR-11887 - Votes: 0 - Radeon HD 4670 graphics card does not work with the SL client (the graphics card will not even be used (0% activity reported by it while Second Life is open)). - Pawz Tomcat
  • WEB-814 - Votes: 11 - cannot post event where land's landing point's Z is > 768

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.

Imported

Resolved

  • VWR-2578 - Votes: 3 - Blocky Default Particle Sprites - Harke Hartnell
    • Old issue, no recent updates. GW (T|C) -- 06:24, 15 February 2009 (UTC)
  • VWR-12019 - Votes: 2 - Voice Chat - Device Settings Wizard Fails - Dirk Talamasca
    • Fixed, resolved as such. GW (T|C) -- 06:50, 15 February 2009 (UTC)
  • WEB-948 - Votes: 1 - economy_stats.php unchanged since January 16, 2009 - Adz Childs
    • Dupe of WEB-295 which has itself been resolved. GW (T|C) -- 06:50, 15 February 2009 (UTC)
  • VWR-6193 - Votes: 1 - Beacon turns 'invisible' at larger distances - {{User|Daedalus Young}
    • Old issue, no recent updates. GW (T|C) -- 06:50, 15 February 2009 (UTC)
  • WEB-300 - Votes: 1 - Passwords with special characters fail to login - Steve Patel
    • Old issue, no recent updates. GW (T|C) -- 06:50, 15 February 2009 (UTC)
  • VWR-4277 - Votes: 1 - different simulator version message has unclickable links - Dedric Mauriac
    • Old issue, no recent updates. GW (T|C) -- 06:50, 15 February 2009 (UTC)
  • SVC-3182 - Votes: 0 - Payment received by one vendor ended up in another avatar's transaction history - Timeless Prototype
    • ISSUE HAS BEEN DISAPPEARED BY THE LINDENS. Since most of us can't see the issue to help debug it because we are not worthy this issue can't be properly triaged. GW (T|C) -- 06:50, 15 February 2009 (UTC)
  • VWR-8374 - Votes: 0 - bandwidth indicator does not fit - wulfric chevalier
    • Currently resolved as NMI. GW (T|C) -- 06:50, 15 February 2009 (UTC)
  • VWR-7035 - Votes: 0 - Closing dialogue causes uploading message to disappear - Haravikk Mistral
    • Old issue, no recent updates. GW (T|C) -- 06:50, 15 February 2009 (UTC)
  • VWR-8214 - Votes: 0 - Removing last friend does not clear friends list until relog - sydney pinion
    • Old issue, no recent updates. GW (T|C) -- 06:50, 15 February 2009 (UTC)
  • SVC-2069 - Votes: 0 - Bumpy Flight - WarKirby Magojiro
    • NMI. GW (T|C) -- 06:50, 15 February 2009 (UTC)
  • VWR-3063 - Votes: 0 - Crash during tp - Luxarnia Dagger
    • Issue was resolved as NMI, no changes since. GW (T|C) -- 06:50, 15 February 2009 (UTC)
  • VWR-3034 - Votes: 0 - Scrolling in text boxes in the client is broken - Domchi Underwood
    • Needs more info. GW (T|C) -- 06:50, 15 February 2009 (UTC)
  • VWR-3032 - Votes: 0 - Linked parts, when copied will unlink the original copied from - Marc Montague
    • Already resolved as NMI, no updates since. GW (T|C) -- 06:50, 15 February 2009 (UTC)
  • SVC-2375 - Votes: 0 - llSetClickAction in a linked set only affects click status of root prim - Francisco Koolhoven
    • Old issue, no recent updates. GW (T|C) -- 06:50, 15 February 2009 (UTC)
    • Resolved as Expected Behavior --Harleen Gretzky 18:50, 15 February 2009 (UTC)

Transcript

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

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