RE: [stellation-res] Command line user diagnostics

["Jonathan Gossage" <jgossage@xxxxxxxx>]

> >-----Original Message-----
> >From: stellation-res-admin@xxxxxxxxxxxxxxx
> >[mailto:stellation-res-admin@xxxxxxxxxxxxxxx]On Behalf Of Mark C.
> >Chu-Carroll
> >Sent: October 20, 2002 8:20 PM
> >To: stellation-res@xxxxxxxxxxxxxxx
> >Subject: Re: [stellation-res] Command line user diagnostics
> >
> >
> >On Sun, 2002-10-20 at 20:03, Jonathan Gossage wrote:
> >> I am finding quite a number of places in the command line
> >implementation of
> >> Stellation where errors in user input are resulting in stack
> >trace dumps in
> >> addition to problem text descriptions. I feel that it looks
> >bad and serves
> >> little troubleshooting purpose to include a stack trace for simple user
> >> input errors. I feel that stack traces should be reserved for
> >programming
> >> errors only.
> >>
> >> How to the rest of you feel on this issue>
> >
> >I'm with you on this; in fact, I think I might even take a
> >stronger stance than what you proposed. I don't think that
> >a "production" version of Stellation should *ever* dump a stack trace
> >unless the user specified debug mode.
> >

Perhaps not to the console, but the stack trace should appear in the log
otherwise trouble shooting is crippled.

> >The code for handling errors is something that needs
> >serious work before the release. Until recently, we've
> >been working in debug mode. The error handling needs
> >a thorough scan, the messages need to be improved (it
> >often generates a generic error message and then prints
> >the exception to provide specific information).
> >
> >	-Mark
> >
Sounds like it is time for another code review concentrating on this issue,
but first I would like to get agreement on exactly how errors are to be
handled. If we don't do this we will not ensure consistent handling of
errors and will provide an uneven user experience.

BTW: 1. Have tou had a chance to look at bug 25093.
     2. Could you follow up tomorrow on committer priveleges. I have a bunch
of Windows batch files almost ready for checkin and sending these my Email
is not an option. Any Email with batch files attached gets the files
stripped out very quickly.
     3. I have only two of the script based test cases left to convert so
that piece of the Windows port is almost complete.

Regards

Jonathan

Personal Email
jgossage@xxxxxxxx

Business Email
jonathan@xxxxxxxxxxxxxx