Bug triage/2007-10-24/Transcript

The following transcript is slightly reordered and typo-corrected for easy reading. Several off-topic talks, including "hi" and "hello", are removed.
== VWR-2843: Issue with horizontal and vertical texture repeats per face in Release Candidate Viewer 1.18.4 ==
Daedalus Young: I already saw is a dupe of 
Daedalus Young: as noted in the wiki 
Alissa Sabre: seems ok. 
Alissa Sabre: do we need to discuss on the severity levels? 
Aric Linden: We can discuss it briefly if you'd like 
Alissa Sabre: no? that's fine. 
Alissa Sabre: ah, np. 
== VWR-2834: Standalone builds fail on 1.18.4.0 with no mozlib ==
Aric Linden: I think we're on 
Daedalus Young: sounds good 
Aric Linden: I'll import this one 
== VWR-2830: Search->Places : results show "[AREA] sq. m." in parcel details ==
Aric Linden: 
Daedalus Young: reproes for me 
Daedalus Young: Search->Places : results show "[AREA] sq. m." in parcel details 
Alissa Sabre: I didn't understand what is this issue... 
McPhenius Swain: definitely not a showstopper 
Dirk Talamasca: Hmmm Me either 
Dirk Talamasca: Need more Info 
Aric Linden: I dont' either 
Daedalus Young: repro: 
Daedalus Young: Go to Search 
Daedalus Young: Places 
Daedalus Young: enter anything you might search for 
Aric Linden: I get the repro, what's the bug? 
McPhenius Swain: I get it too, but is it a bug? 
Daedalus Young: notice to the bottm right, for example: Traffic: 14117.Area: [AREA] sq. m. 
McPhenius Swain: right 
Daedalus Young: rather than Area: 16 sqm 
Alissa Sabre: ah, Ok. 
McPhenius Swain: just typo 
Dirk Talamasca: ahhhh 
Dirk Talamasca: okay gotcha 
Alissa Sabre: the substring "[AREA]" should have been replaced by a name of the parcel 
Daedalus Young: by the correct number 
Alissa Sabre: not the name of the parcel, but the number? 
Daedalus Young: how large is the parcel? [AREA] sqm it is 
Alissa Sabre: well, I have never tried to buy lands, so I'm not familiar with this panel... 
Daedalus Young: the amount of land it should be 
Alissa Sabre: ok. 
Aric Linden: I'm not seeing the issue, but I'm not running on the RC version 
Alissa Sabre: so, the problem is that the amount of land is not shown and it says "[AREA]" there. 
Daedalus Young: exactly 
Aric Linden: OK. 
Aric Linden: i'll import it 
Alissa Sabre: It sounds like a bug, then. 
== VWR-2827: right click of existing folder --> new folder while in inventory places you in 'rename' position of existing folder instead of creating a new sub-folder ==
Aric Linden: 
Daedalus Young: right click of existing folder --> new folder while in inventory places you in 'rename' position of existing folder instead of creating a new sub-folder. 
McPhenius Swain: I see it works fine on your Max Dae.. it's works on my XP too 
Daedalus Young: did not repro for me on my Mac 
McPhenius Swain: Just tried it 
Daedalus Young: ok 
Opensource Obscure: i can't repro on Linux, here. 
Alissa Sabre: I'm too lazy and have not tried this one. 
Daedalus Young: looks like reporter is confused with new behavior 
Alissa Sabre: but the feeling here is "can't reproduce." 
Aric Linden: I agree with you Alissa 
Aric Linden: I'll update accordingly 
Seg Baphomet: Can't seem to repro here either. Nicholaz viewer. 
Harleen Gretzky: Supposedly it is a RC bug 
Alissa Sabre: many people said the bug doesn't reproduce 
Alissa Sabre: anyone tried the bug 2827 on 1.18.4RC? 
Alissa Sabre: or you just said "it doesn't appear on 1.18.3 viewers" 
Daedalus Young: the New Folder one? yes 
Alissa Sabre: Yes, new folder thing 
Daedalus Young: no, I tried the New Folder bug in the latest RC, 1.18.4 
Daedalus Young: and there it did not repro 
Harleen Gretzky: But you are on MAC, Charlene is on Windows 
Seg Baphomet: Ah, I'm not up to 1.18.4 yet. 
Opensource Obscure: [i should have said i'm on 1.18.4(0)] 
Daedalus Young: I'm on the RC too, so I can see if a bug reproes :) 
== VWR-2826: Several problems on handling Japanese input (and possiblly Chinese/Korean also) ==
Aric Linden: 
Daedalus Young: Several problems on handling Japanese input (and possiblly Chinese/Korean also) 
Alissa Sabre: ah, that's mine. lol 
Aric Linden: Ahh. I've already imported this one 
Aric Linden: 
Aric Linden: so we can move on 
PulseBurst Flow: what do you mean by imported. 
Aric Linden: Moved it from the external bug tracking system to the internal one 
Alissa Sabre: Hmm. 
Aric Linden: 2826 has already been imported Alissa 
Seg Baphomet: That's a springy couch. :) 
Alissa Sabre: can we discuss what should be done on 2826? 
Aric Linden: Alissa, do you want to discuss 2826? 
Alissa Sabre: ah, yes, but I think we can do it later 
Alissa Sabre: please go on to the next issue 
== VWR-2824: Incorrect information in View Groups ==
Aric Linden: 
Daedalus Young: Incorrect information in View Groups 
Daedalus Young: really odd one, I have it too 
Daedalus Young: seemingly random, my entire Group list says it's empty, then on relog sometimes it is back full again 
Daedalus Young: I initially used another Issue to report this bug, but it's as described here 
Aric Linden: I think these *are* dupes 
PulseBurst Flow: I cant reproduce 2824 with RC and OSX 
Daedalus Young: Pulse, it appears to be random on relog 
McPhenius Swain: I haven't ever noticed this one 
Daedalus Young: I don't have it now, but I had it yesterday 
McPhenius Swain: Dae is it on log in or randomly while in world? 
Daedalus Young: on login 
McPhenius Swain: maybe lag? 
Daedalus Young: so maybe it fails to load and never updates 
PulseBurst Flow: Well, I had something I get might be related, but havent Jira it.. 
Aric Linden: it may be the asset server being behind in delivering bits and then timing out 
Daedalus Young: I tried relogging in empty regions too 
PulseBurst Flow: will wait. 
Daedalus Young: although it first did appear after there were also payment and attachment problems 
Aric Linden: I personally haven't seen this issue 
Daedalus Young: that was not the case later when I relogged in an empty region 
Aric Linden: my suggestion is that we close one as a dupe and import the other 
Daedalus Young: sounds cool 
== VWR-2823: Show in Search option is retained when tranfering or selling the object ==
Aric Linden: 
Daedalus Young: Show in Search option is retained when tranfering or selling the object 
Alissa Sabre: I have a feeling that this is not a simple bug, but related to a fundamental design issue on the new search feature 
Dirk Talamasca: I think Jeska has addressed this in the blog. 
Aric Linden: I think we'll import it and make sure. 
Aric Linden: sound ok? 
McPhenius Swain: yep 
== VWR-2821: Can't change Search option in No Mod objects ==
Daedalus Young: at least 2821 is addressed in the blog 
Dirk Talamasca: Before the blog comments closed, several Residents asked about the inability to change the 'show in search' checkbox on non-modifyable objects which were left set 'for sale' by their creator. We've made a change, which will push in the next release candidate, to allow owners of objects to modify the 'show in search' checkbox even if they do not have the ability to modify the object in other ways. 
Daedalus Young: concerning no-mod objects 
Daedalus Young: yes, that's about 2821 imo 
Alissa Sabre: do we have a resolution such as "see blog"? lol 
Dirk Talamasca: LOLOl 
Daedalus Young: Fixed Internally, I'd say 
Alissa Sabre: sounds good 
Aric Linden: yep. I'll resolve it as such. 
== VWR-2817: Edit Window Displays Copy Tools Differently ==
Aric Linden: 
Daedalus Young: Edit Window Displays Copy Tools Differently 
Alissa Sabre: this is yours, Dirk 
Alissa Sabre: what is the problem? 
Aric Linden: I'm happy to import this and pass it to the RX group for their judgement. 
Daedalus Young: those two checkboxes used to be on the right? 
Aric Linden: I dn't know why this changed. 
Dirk Talamasca: Yes thety normally appear to the right of the shapes 
Alissa Sabre: so, the change of the UI panel layout *is* the problem. am I right? 
Dirk Talamasca: Correct 
Harleen Gretzky: the 3 Copy Selection and it's 2 subboxes 
PulseBurst Flow: be nice to see side-by-side in the jira to see difference. 
Aric Linden: /nods at PulseBurst 
Dirk Talamasca: It is minor but still.. when you build you kind of just know where these things are after awhile 
Harleen Gretzky: Copy Seelction is next to the Grass Icon normally 
Aric Linden: we can compare versions internally 
Daedalus Young: and seeing there appears to be no reason for the change 
Aric Linden: I'll import 
Daedalus Young: oter than to annoy people :P 
Alissa Sabre: One of the thing is 
Alissa Sabre: 1.18.4 RC release note has no words on this change 
Daedalus Young: maybe it is for future expansion adding a sculpty button 
Alissa Sabre: so, we external developers chan't decide whether this is a bug or intended change 
Aric Linden: I don't think it was expected. I think it's simply a bug 
Alissa Sabre: Ok. fine. 
Daedalus Young: there would've been something about it in the notes, surely 
== VWR-2803: Lag Meter network ping metric doesn't account for residents outside the USA ==
Aric Linden: 
Daedalus Young: Lag Meter network ping metric doesn't account for residents outside the USA 
Aric Linden: I'll import this. I think the arguments are well made 
Alissa Sabre: well, 
Alissa Sabre: I support the idea this is a problem 
Daedalus Young: I'm often around 250 msec, which is the threshold for yellow 
Alissa Sabre: but I don't support the proposed solution here. 
Alissa Sabre: SL users are now in world wide, and there are various network environment 
Alissa Sabre: we need to set some threshold 
Aric Linden: what would you suggest Alissa 
Alissa Sabre: I just want to change the wording 
Alissa Sabre: something like "the network may not suitable to use SL" may be ok 
Alissa Sabre: however, saying "problem or file shareing brah brah" seems inappropriate 
Aric Linden: ok. please add your comments. or perhaps you'd prefer to do a patch? 
Alissa Sabre: I already commented 
Aric Linden: :-) 
Alissa Sabre: I'm afraid my comment is not too clear... 
Daedalus Young: file sharing apps do bring the ping down 
Daedalus Young: I've had it at 3000 msec once 
Aric Linden: yes. since you appear to feel that the solution will be accepted as is. I'm not convinced of that. 
Daedalus Young: so that -can- be correct 
Alissa Sabre: If we just raise the threshold to 300ms 
Alissa Sabre: someone in other location would say "hey, 300ms is my normal latency." 
Aric Linden: I'll go ahead and import it. 
Daedalus Young: you would have to let the system learn what is the average then and let it decide on that 
Alissa Sabre: I'm just afraid what the normal, no-techy end user think he/she is told "network problem" 
Daedalus Young: it's different for every user 
Aric Linden nods 
Alissa Sabre: so, my point is 
Alissa Sabre: putting some fixed threshold seems ok as a short term solution 
PulseBurst Flow: where do yo see msec value? 
Alissa Sabre: but we need to be careful how to express it to end users 
Daedalus Young: ctrl-shift-1 
Daedalus Young: Ping Sim 
Daedalus Young: 230 for me atm 
Daedalus Young: 172 now :P 
McPhenius Swain: 84 
Daedalus Young: 234 now :P 
PulseBurst Flow: Oh, I must be in some remote desert then.. ;-D 
== VWR-2795: New Land Description Multiline box does not allow Line Return formatting - converts to ? ==
Aric Linden: is next 
Daedalus Young: New Land Description Multiline box does not allow Line Return formatting - converts to ? 
Aric Linden: this is a bug, straightup 
Alissa Sabre: I'm not familiar with land-owner's tools 
Daedalus Young: yep, haven't seen it, but I'm sure it's right 
PulseBurst Flow: me either. 
PulseBurst Flow: haven't used it. 
Aric Linden: linefeed/cr storage conversion is suspect 
Alissa Sabre: yes. 
Aric Linden: going from windows to linux 
Daedalus Young: having programmed php before, I know that can be a pain 
Alissa Sabre: so, in a previous version, land owners could use returns in description? 
Daedalus Young: no, that's new 
Aric Linden shrugs 
Daedalus Young: you only had one line 
Alissa Sabre: what I'm asking is the expected behaviour in previous versions 
Aric Linden: I honestly don't know 
Alissa Sabre: ok. 
Alissa Sabre: so, in 1.18.3, it was one line. 
Aric Linden: I suspect that a change was made to the dialog to support the new search stuff 
Daedalus Young: just like with webforms, you can have an input for one line and an input (textarea) for multiple lines 
Alissa Sabre: in 1.18.4, it becomes multi-line 
Daedalus Young: one line does not accept returns, the textarea does 
Alissa Sabre: but it doesn't allow newlines there 
Aric Linden: so that descriptions can be made larger, but I don't know that for sure 
Daedalus Young: I think for more usability in the new search 
Alissa Sabre: agreed. 
== VWR-2847: Wrong hover text in Japanese UI ==
Aric Linden: 
Aric Linden: is next 
Daedalus Young: Wrong hover text in Japanese UI 
Daedalus Young: Alissa's again 
Alissa Sabre: that's mine. 
Alissa Sabre: I believe it is just a mistake in XUI resource file for Japanese 
Aric Linden: ok 
Aric Linden: do you want to fix it? 
Aric Linden: or should I just import it? 
Alissa Sabre: ah, if you want, I can send a patch 
Aric Linden: Alissa, that'd be great if you'd be willing to patch it 
Alissa Sabre: should I send a patch against 1.18.4 or 1.18.3? 
Aric Linden: 1.18.4 
Aric Linden: since that will be release soon 
Alissa Sabre: ok. I'm doing it. 
Aric Linden: thanks 
Alissa Sabre: you can assign this issue to me. 
Aric Linden: done 
== VWR-2829: Texture Picker Jumps Between Multiple Highlighted Textures ==
Aric Linden: 
Daedalus Young: Texture Picker Jumps Between Multiple Highlighted Textures 
Daedalus Young: I haven't seen this myself 
Daedalus Young: but judging from the video, looks like the picker is trying to catch up with loading the texture 
McPhenius Swain: If I am right, I think I have had this... but it might be that Dae 
McPhenius Swain: I have closed, then re=open and was fine 
Daedalus Young: and jumps back up when a particular texture is loaded 
Aric Linden: I think i'll import this for internal repro 
McPhenius Swain: I haven't had this issue for quite sometime, but I alsso upgraded my video card a month ago 
Aric Linden: that's interesting McPhenius 
Aric Linden: Worth seeing if we can repro it inhouse 
McPhenius Swain: I completely forgot about that.. until I watched the video, it's been awhile 
PulseBurst Flow: can't view the .avi 
McPhenius Swain: I was using a ATI Radeon 700 Pro 256mb previously 
McPhenius Swain: now using Nvidia 7600 GS 
Daedalus Young: ah, the issue lists ati radeon too 
McPhenius Swain: rigth 
Daedalus Young: then I have to recheck it, I have that too in my machine 
Daedalus Young: on a mac though 
== SVC-846: Not all my groups are visible and the group dialog, (Edit -> Groups...) i'm missing some groups ==
Aric Linden: 
Aric Linden: is next 
Aric Linden: is this still an issue? 
Alissa Sabre: I just want to know the reason 
Daedalus Young: Can't start 1.18.3(5) RC viewer after 1.18.4(0) RC appeared 
Alissa Sabre: was it a right thing? 
Daedalus Young: I see what you mean 
Harleen Gretzky: Because that RC went standard 
Alissa Sabre: 1.18.3.5 RELEASE viewer is compatible to the current grid, so is 1.18.3.5 RC 
PulseBurst Flow: I am not going to try to reproduce this. 
Alissa Sabre: why LL excluded use of 1.18.3.5 RC 
Harleen Gretzky: But there is no reason to use that RC, it is the same as teh standard viewer 
Daedalus Young: those two are the same 
Aric Linden: yes. it's the new upgrade model 
Daedalus Young: so you would have the official one -and- an RC, which are exactly the same 
Aric Linden: I'd like to simply close this if that's ok? 
Alissa Sabre: so, Aric, you said it is intended 
Aric Linden: yes 
Alissa Sabre: well, for this particular case, it's ok. 
Alissa Sabre: because 1.18.3.5 RC and release are identical 
Alissa Sabre: however, we sometimes need to run _old_ viewers to see the old behaviour 
Alissa Sabre: during trouble shooting 
Aric Linden: as daedalus said, we're trying to keep the release candidate channel for release candidates and production channel for production versions 
Daedalus Young: if 1.18.4.1 comes out, it will prob be optional then 
PulseBurst Flow: well, if they meant 1.18.3.5 RC, and that's the same as release..then it is a problem 
Alissa Sabre: so, makeing as much viewer versions runnable seems good 
PulseBurst Flow: if someone wants to try lastest RC, but go back to normally using current released. 
Aric Linden: they can do that with the new model, PulseBurst 
Alissa Sabre: the 1.18.3.5 RC binary is identical to 1.18.3.5 RELEASE 
Alissa Sabre: but there are some difference in resource 
Aric Linden: yes. that's correct Alissa 
Aric Linden: name resource and date are the difference 
PulseBurst Flow: right..so they can try RC, and go back to last release.. 
Aric Linden: that's completely do-able 
Aric Linden: are we good? 
Alissa Sabre: ok 
Daedalus Young: rather than rolling out all the RCs as new official viewers, we special dedicated bold Resi's are chosen to try them out before the masses start crying about broken things :) 
Aric Linden: I'm afraid we're out of time 
Daedalus Young: and out of issues 
== VWR-2826, again ==
Alissa Sabre: ok, the last word on my japanese input method thing 
Aric Linden: yes. Alissa, was there something specific you wanted to cover 
Alissa Sabre: I just wanted to say that this issue need not to be fixed. 
Aric Linden: ok 
Alissa Sabre: instead, I just want to revert the changes from 1.18.3.5 
Aric Linden: ok. 
Alissa Sabre: the currrent 1.18.4 RC viewer is unusable if you use Japanese 
Aric Linden: I'll reassign it to you and you can patch it or whatever 
Alissa Sabre: but fixing these new feature is useless, because better improvement on input method handling is coming 
Alissa Sabre: no, that's not the point 
Aric Linden: yes. it's true 
Aric Linden: we're working it 
Alissa Sabre: just remove all related changes introduced in 1.18.4 
Aric Linden: Ok. I'll close it 
Alissa Sabre: that's what I propose here 
Aric Linden: thanks