gnumed-bugs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnumed-bugs] <bug>: This exception seems to happen when trying


From: Rogerio Luz Coelho
Subject: Re: [Gnumed-bugs] <bug>: This exception seems to happen when trying
Date: Tue, 5 Jul 2011 22:17:28 -0300



2011/7/5 Karsten Hilbert <address@hidden>
Hello Rogerio,

> user comment  : This exception seems to happen when trying to save a episode under a Problem that still has a open episode ... but this is an exception ?

That's right.

> client version: 0.9.6

I cannot, for the life of it, reproduce or find this problem:

> 2011-07-02 11:43:01  DEBUG     gm.gui (/usr/share/gnumed/Gnumed/wxpython/gmExceptionHandlingWidgets.py::handle_uncaught_exception_wx() #152): unhandled exception caught:
> Traceback (most recent call last):
>   File "/usr/share/gnumed/Gnumed/wxpython/gmEditArea.py", line 287, in _on_save_button_pressed
>     if self._PNL_ea.save():
>   File "/usr/share/gnumed/Gnumed/wxpython/gmEditArea.py", line 173, in save
>     return self._save_as_update()
>   File "/usr/share/gnumed/Gnumed/wxpython/gmEMRStructWidgets.py", line 1498, in _save_as_update
>     if not move_episode_to_issue(episode = self.data, target_issue = issue, save_to_backend = False):
>   File "/usr/share/gnumed/Gnumed/wxpython/gmEMRStructWidgets.py", line 1197, in move_episode_to_issue
>     'old_epi_end': exist_range[1].strftime('%m/%y')
> KeyError: u'issue name'

I have searched the entire source code: there simply is no
"issue name" string (note: not "issue_name" with underscore)
anywhere in the code let alone being used to access a
dictionary or some such.

This leaves only two possibilities:

1) The code on your machine is different from the code on my machine.

       This does not seem to be the case because you sent me your
       /usr/share/gnumed/Gnumed/wxpython/gmEMRStructWidgets.py and
       it did not contain "issue name" either.

2) The key being applied is not hard-coded but rather comes
  from your database.

So, my questions:

a) Can you reproduce this with any patient or any combination
  of health issue with open episode plus another open episode
  being moved into it ?

Yes it is still happening all the time.

Do you want to have a look on my DB backup? (can send you privately or give you a download link) 


 
b) Do you happen to have a health issue in your database that
  is *named* "issue name" ?

c) Did you happen to enter "issue name" into the target issue
  phrasewheel ?


Not that I have inputed, all text is in Portuguese.

Rogerio 

reply via email to

[Prev in Thread] Current Thread [Next in Thread]