<bug>: immediate 2nd exception after last bug repo

[Saša Janiška]

user comment : immediate 2nd exception after last bug report (maybe after I clicked "View log" after previous bug report without initial obvious result) ... I therefore clicked "Close gnumed" and after I closed it, this unhandled exception came up.

system account: jb
staff member : Dr.Leonard Horatio McCoy (LMcC = any-doc)
sender email : <email address hidden>

 affects gnumed

[shilbert (sebastian-hilbert)]

On Mittwoch 24 September 2008, Gour wrote:
> ** Attachment added: "log file"
> http://launchpadlibrarian.net/17920865/log.tar.gz
>
> ** Changed in: gnumed
> Importance: Undecided => Medium
>
> ** Tags added: automatic-report

Please close as it is no bug but user clicked on continue instead of close in
the bug reporter.

--
Sebastian Hilbert
Leipzig / Germany
[www.gnumed.de] -> PGP welcome, HTML ->/dev/null

[shilbert (sebastian-hilbert)]

On Mittwoch 24 September 2008, Gour wrote:
> Public bug reported:
>
> user comment : immediate 2nd exception after last bug report (maybe
> after I clicked "View log" after previous bug report without initial
> obvious result) ... I therefore clicked "Close gnumed" and after I
> closed it, this unhandled exception came up.
>
> system account: jb
> staff member : Dr.Leonard Horatio McCoy (LMcC = any-doc)
> sender email : <email address hidden>
>
> affects gnumed
>
> ** Affects: gnumed
> Importance: Medium
> Status: New
>
>
> ** Tags: automatic-report

Ahh, good that one can stay then.

--
Sebastian Hilbert
Leipzig / Germany
[www.gnumed.de] -> PGP welcome, HTML ->/dev/null

[shilbert (sebastian-hilbert)]

well it is not really a bug. User clicked continue after a bug ocured. This leaves GNUmed in a buggy state and triggers further exceptions. Solution is to quit after an exception occurs.

[ncq (karsten-hilbert)]

> well it is not really a bug. User clicked continue after a bug ocured.
> This leaves GNUmed in a buggy state and triggers further exceptions.

"Undetermined" rather than "buggy" and "*can* trigger further exceptions".

The exception handler message very much informs the user of said
state of affairs.

Karsten

--
Sensationsangebot verlängert: GMX FreeDSL - Telefonanschluss + DSL
für nur 16,37 Euro/mtl.!* http://dsl.gmx.de/?ac=OM.AD.PD003K1308T4569a

[ncq (karsten-hilbert)]

So this is rather a quite expected situation and not a bug at all.

It should be recast as "Wont fix" or something.

Karsten

-------- Original-Nachricht --------
> Datum: Mon, 19 Jan 2009 16:35:33 -0000
> Von: shilbert <email address hidden>
> An: <email address hidden>
> Betreff: [Bug 273970] Re: <bug>: immediate 2nd exception after last bug repo

> well it is not really a bug. User clicked continue after a bug ocured.
> This leaves GNUmed in a buggy state and triggers further exceptions.
> Solution is to quit after an exception occurs.
>
> ** Changed in: gnumed
> Status: New => Confirmed
>
> --
> <bug>: immediate 2nd exception after last bug repo
> https://bugs.launchpad.net/bugs/273970
> You received this bug notification because you are a member of GNUmed
> development, which is subscribed to GNUmed.
>
> Status in GNUmed - electronic medical record: Confirmed
>
> Bug description:
> user comment : immediate 2nd exception after last bug report (maybe after
> I clicked "View log" after previous bug report without initial obvious
> result) ... I therefore clicked "Close gnumed" and after I closed it, this
> unhandled exception came up.
>
> system account: jb
> staff member : Dr.Leonard Horatio McCoy (LMcC = any-doc)
> sender email : <email address hidden>
>
> affects gnumed

--
Sensationsangebot verlängert: GMX FreeDSL - Telefonanschluss + DSL
für nur 16,37 Euro/mtl.!* http://dsl.gmx.de/?ac=OM.AD.PD003K1308T4569a