Bug triage/2007-09-24

Next meeting: 2007-09-24 at 3pm in Hippotropolis. See Bug triage for details.

Fast Track Import

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

Patches

• VWR-2563 - Votes: 0 - Add exists() function to LLFile - Nicholaz Beresford
• SVC-580 - Votes: 1 - ATTACH_LPEC / ATTACH_RPEC reversed - Ziggy Puff
• VWR-1609 - Votes: 3 - disabling "Show Selection Beam" makes beam render incorrectly for others - Lex Neva
• VWR-2524 - Votes: 1 - Possible crash on startup with group messages waiting (llnotify.cpp) - Nicholaz Beresford
• VWR-2551 - Votes: 0 - Error in macview.xcodeproj -- invalid dependencies - bushing Spatula
• VWR-2488 - Votes: 1 - Standalone build is almost, but not quite there. - Seg Baphomet
• VWR-2546 - Votes: 0 - Allow registering multiple message system handlers - Dale Glass
• VWR-860 - Votes: 2 - Support display memory above 512MB - Tillie Ariantho
• VWR-2086 - Votes: 8 - Alt key no longer shows "physical" when pressed. - Cliff Commons
• VWR-2516 - Votes: 1 - Flycam support for Mac OS X - abstra apparatchik
• VWR-2331 - Votes: 7 - Terraform tool variable "strength" - Gigs Taggart
• VWR-2504 - Votes: 0 - Source cleanup: Move chat sending code from LLChatBar to LLAgent - Dale Glass
• VWR-2412 - Votes: 0 - Possible crash drawpoolwater - Nicholaz Beresford
• VWR-2411 - Votes: 0 - Possible crash in pipeline.cpp - Nicholaz Beresford
• VWR-1677 - Votes: 0 - Ctrl+T does not return focus to the chat bar in IM window - Feynt Mistral
• VWR-2256 - Votes: 1 - Mac updater directory permission issues - Grazer Kline
• VWR-2255 - Votes: 1 - Mac updater does not log output. - Grazer Kline
• VWR-2113 - Votes: 0 - Mac Auto Updater "hides", giving appearance of failing - Gibson Willis

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/2007-09-24/Transcript

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