<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.ecmsonormal, li.ecmsonormal, div.ecmsonormal
{mso-style-name:ec_msonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.ecmsohyperlink
{mso-style-name:ec_msohyperlink;}
span.ecmsohyperlinkfollowed
{mso-style-name:ec_msohyperlinkfollowed;}
span.ecemailstyle17
{mso-style-name:ec_emailstyle17;}
p.ecmsonormal1, li.ecmsonormal1, div.ecmsonormal1
{mso-style-name:ec_msonormal1;
mso-margin-top-alt:auto;
margin-right:0cm;
margin-bottom:0cm;
margin-left:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
span.ecmsohyperlink1
{mso-style-name:ec_msohyperlink1;
color:blue;
text-decoration:underline;}
span.ecmsohyperlinkfollowed1
{mso-style-name:ec_msohyperlinkfollowed1;
color:purple;
text-decoration:underline;}
span.ecemailstyle171
{mso-style-name:ec_emailstyle171;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle26
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-AU link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Yes, I think catching duplicates is important – but I’m not 100%
confident the Mantis SOAP adapter is sufficiently advanced that we can search
for that, but I think that might warrant us building a separate webapp for this
actually if we can’t.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>In terms of catching the errors – that part is relatively easy, we’re
a managed application which means we can catch exceptions at the root level.
Getting those is easier – it’s already been suggested we use a secondary
application so we can catch Mono errors too, but I’m not quite sure we really
want to do that – because I believe that falls outside the OpenSim scope. (ie
issues with Mono are a problem for Mono)<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Adam<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div style='border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt'>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'>
<p class=MsoNormal><b><span lang=EN-US style='font-size:10.0pt;font-family:
"Tahoma","sans-serif"'>From:</span></b><span lang=EN-US style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'> opensim-dev-bounces@lists.berlios.de
[mailto:opensim-dev-bounces@lists.berlios.de] <b>On Behalf Of </b>Mircea
Filipescu<br>
<b>Sent:</b> Wednesday, 5 November 2008 4:25 AM<br>
<b>To:</b> opensim-dev@lists.berlios.de<br>
<b>Subject:</b> Re: [Opensim-dev] Automated Bug Reporting<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-size:10.0pt;
font-family:"Verdana","sans-serif"'>Brilliant idea back there! An automated bug
reporting system would certainly be one helpful thing. But indeed it would
raise a lot of complications and could even risk sending false positives at one
point. And indeed the best method for this is a separate project in the Mantis.
opensim-automated_bug_report or something else. Otherwise I don't think it
would be a good idea.. a separate project is the best method in Mantis that
would keep things arranged at their best with this.<br>
<br>
Now a question; How would we prevent this from making a flood of an
unrecognizable pile of issues and crashes? What if the user keeps experiencing
the same crash over and over again? That crash will be spammed 100 times in
that Mantis project which wouldn't be that good. So I'm suggesting a way in
which every single type of crash is auto-reported only once. If the parameters
of a crash being reported are exactly the same as an older crash already there,
skip that second report so the same thing doesn't get posted two times.<br>
<br>
And now another problem; -Who- will report a crash if the only running process
(opensim.exe) is the one who crashes and disappears? We could either make it so
opensim.exe sends the previous crash to Mantis the next time it starts, or some
background process watches opensim.exe and the second it crashes it takes all
the info and throws into the Mantis.<o:p></o:p></span></p>
<div class=MsoNormal align=center style='text-align:center'><span
style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>
<hr size=2 width="100%" align=center id=stopSpelling>
</span></div>
<p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-size:10.0pt;
font-family:"Verdana","sans-serif"'>From: adam@deepthink.com.au<br>
To: opensim-dev@lists.berlios.de<br>
Date: Tue, 4 Nov 2008 21:51:09 -0500<br>
Subject: [Opensim-dev] Automated Bug Reporting<o:p></o:p></span></p>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>The
subject has been raised recently, in anticipation of the 0.6.0 release about
including an automated bug report process in OpenSim, obviously it would be
switched off by default, but the option would exist to have exceptions logged
in OpenSim reported to the Mantis bug tracker automatically.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'> <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>The
big advantage to doing so is it becomes easier to prioritise which bugs need to
be fixed – issues which occur frequently would immediately become visible
(whereas right now they aren’t so much). It would also allow us to get some
debug feedback on features we implement – ie internal exceptions which we
ignore right now could be dumped onto the mantis with appropriate tags.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'> <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>The
solution I am considering for implementing this is the MantisConnect .NET
adapter which basically uses the mantis SOAP interface – right now we’ve got a
section of code in the main OpenSim.exe which handles the ‘last exception’ –
I’d like to put the code initially in there, then open the option up for
developers to report bugs via a ‘Util’ member function at a later point.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'> <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>In
terms of Mantis itself, I’m thinking it might be best to setup a second project
for the automated reports – while we lose the ability to then link issues as
‘related’ with a manual report, it also avoids cluttering up the project with
thousands of automated reports.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'> <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>Thoughts?<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'> <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>Adam<o:p></o:p></span></p>
</div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p> </o:p></span></p>
<div class=MsoNormal align=center style='text-align:center'><span
style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>
<hr size=2 width="100%" align=center>
</span></div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>Get
news, entertainment and everything you care about at Live.com. <a
href="http://www.live.com/getstarted.aspx%20" target="_new">Check it out!</a><o:p></o:p></span></p>
</div>
</div>
</body>
</html>