Error during a Nefarian parse

[GoogleCodeExporter]

I have no idea what's going on here, but I thought I'd share it with you guys 
and maybe one of you can figure it out!  This first try on Nefarian threw up 
all kinds of weird errors, but all the subsequent ones went through fine.  
Errors copied here, log attached for your reference.

./stasis: WARNING: -template is an experimental option, please report any 
strange behavior
./stasis: Encounter start: maloriak at 2/13 16:48:29.073 .. writing Maloriak 
(sws-maloriak-20110213-164829-1-) .. done.
./stasis: Encounter start: chimaeron at 2/13 16:58:42.927 .. writing Chimaeron 
(sws-chimaeron-20110213-165842-1-) .. done.
./stasis: Encounter start: atramedes at 2/13 17:13:59.766 .. writing Atramedes 
(sws-atramedes-20110213-171359-1-) .. done.
./stasis: Encounter start: nefarian at 2/13 17:51:08.788 .. writing Nefarian 
try 1 (sws-nefarian-20110213-175108-0-) .. Use of uninitialized value $_[1] in 
localtime at lib/Stasis/Page.pm line 241, <INPUT> line 109473.
Use of uninitialized value $mintime in subtraction (-) at 
lib/Stasis/Page/Chart.pm line 634, <INPUT> line 109473.
Use of uninitialized value $maxtime in subtraction (-) at 
lib/Stasis/Page/Chart.pm line 634, <INPUT> line 109473.
Use of uninitialized value $maxtime in numeric le (<=) at 
lib/Stasis/Page/Chart.pm line 638, <INPUT> line 109473.
Use of uninitialized value $i in numeric le (<=) at lib/Stasis/Page/Chart.pm 
line 638, <INPUT> line 109473.
Use of uninitialized value $i in exists at lib/Stasis/Page/Chart.pm line 639, 
<INPUT> line 109473.
Use of uninitialized value $mintime in subtraction (-) at 
lib/Stasis/Page/Chart.pm line 639, <INPUT> line 109473.
Use of uninitialized value $i in subtraction (-) at lib/Stasis/Page/Chart.pm 
line 639, <INPUT> line 109473.
Use of uninitialized value $i in exists at lib/Stasis/Page/Chart.pm line 640, 
<INPUT> line 109473.
Use of uninitialized value $mintime in subtraction (-) at 
lib/Stasis/Page/Chart.pm line 640, <INPUT> line 109473.
Use of uninitialized value $i in subtraction (-) at lib/Stasis/Page/Chart.pm 
line 640, <INPUT> line 109473.
Use of uninitialized value $i in exists at lib/Stasis/Page/Chart.pm line 641, 
<INPUT> line 109473.
Use of uninitialized value $mintime in subtraction (-) at 
lib/Stasis/Page/Chart.pm line 641, <INPUT> line 109473.
Use of uninitialized value $i in subtraction (-) at lib/Stasis/Page/Chart.pm 
line 641, <INPUT> line 109473.
Use of uninitialized value $i in addition (+) at lib/Stasis/Page/Chart.pm line 
642, <INPUT> line 109473.
Use of uninitialized value $mintime in subtraction (-) at 
lib/Stasis/Page/Chart.pm line 642, <INPUT> line 109473.
Use of uninitialized value $i in subtraction (-) at lib/Stasis/Page/Chart.pm 
line 642, <INPUT> line 109473.
Use of uninitialized value $maxtime in numeric le (<=) at 
lib/Stasis/Page/Chart.pm line 638, <INPUT> line 109473.
done.
./stasis: Encounter start: nefarian at 2/13 17:53:41.321 .. writing Nefarian 
try 2 (sws-nefarian-20110213-175341-0-) .. done.

Original issue reported on code.google.com by twini...@gmail.com on 14 Feb 2011 at 6:11

Attachments:

• 20110213.rar

[GoogleCodeExporter]

And, actually, while I'm here, thank you all for continuing to update this for 
Cata!  Our raid still much prefers the output of stasis to anything else, fast, 
easy to read, and reliably self hosted.

Original comment by twini...@gmail.com on 14 Feb 2011 at 6:17

[GoogleCodeExporter]

I think this is caused by one of your raid 'starting' a combat by using Mind 
Vision on Nefarian. It basically makes it think there's a zero-damage 
encounter. I'll see if I can patch something in to ignore Mind Vision events or 
think up a better solution. Your log also shows that Onyxia isn't correctly set 
as part of the encounter - the early bit of combat isn't being included in 
parses I think.

I'll fix both as soon as I can - probably the Onyxia bug first as that'll be 
easy :)

Original comment by eddedmondson on 14 Feb 2011 at 11:29

• Changed state: Started

[GoogleCodeExporter]

OK both fixed in r101. It now ignores Mind Vision when splitting logs. Other 
similar non-aggressive spells may cause this bug but haven't been coded for - 
it's a fairly unusual and harmless bug at least!

Original comment by eddedmondson on 14 Feb 2011 at 12:34

• Changed state: Fixed