gnumed-bugs
[Top][All Lists]
Advanced

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

Re: [Gnumed-bugs] <bug>: <user did not comment on bug report>


From: Karsten Hilbert
Subject: Re: [Gnumed-bugs] <bug>: <user did not comment on bug report>
Date: Thu, 27 Dec 2018 16:47:12 +0100
User-agent: Mutt/1.10.1 (2018-07-13)

Dear parallels,

thanks for taking the time to report this problem.

> user comment  : <user did not comment on bug report>
> 
> client version: 1.6.11

You may want to try the newest stable version which is 1.7.3
(1.7.4 released but not packaged by distributions yet).

The first two login attempts failed because you did not have
a local GNUmed server running, which is needed for logging
into it:

> 2018-12-26 14:39:06  ERROR     gm.ui 
> (/usr/share/gnumed/Gnumed/wxpython/gmAuthWidgets.py::connect_to_database() 
> #198): login attempt failed: could not connect to server: Connection refused
>       Is the server running on host "127.0.0.1" and accepting
>       TCP/IP connections on port 5432?
...
> 2018-12-26 14:41:35  ERROR     gm.ui 
> (/usr/share/gnumed/Gnumed/wxpython/gmAuthWidgets.py::connect_to_database() 
> #198): login attempt failed: could not connect to server: No such file or 
> directory
>       Is the server running locally and accepting
>       connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"?

You then tried to log into the public database which needs a
password supplied:

> 2018-12-26 14:39:26  ERROR     gm.ui 
> (/usr/share/gnumed/Gnumed/wxpython/gmAuthWidgets.py::connect_to_database() 
> #152): login attempt failed: PostgreSQL: fe_sendauth: no password supplied
> DSN: dbname=gnumed_v21 host=publicdb.gnumed.de port=5432 user=any-doc 
> sslmode=prefer
> 2018-12-26 14:39:26  WARNING   gm.db 
> (/usr/share/gnumed/Gnumed/pycommon/gmPG2.py::__str__() #2303): 
> cAuthenticationError.__str__() called
> 2018-12-26 14:39:26  ERROR     gm.db 
> (/usr/share/gnumed/Gnumed/pycommon/gmPG2.py::__str__() #2305): PostgreSQL: 
> fe_sendauth: no password supplied
> DSN: dbname=gnumed_v21 host=publicdb.gnumed.de port=5432 user=any-doc 
> sslmode=prefer

which you did, eventually, and logged in successfully.

You then hit upon this:

> 2018-12-26 14:48:48  DEBUG     gm.gui 
> (/usr/share/gnumed/Gnumed/wxpython/gmExceptionHandlingWidgets.py::handle_uncaught_exception_wx()
>  #219): unhandled exception caught:
> Traceback (most recent call last):
>   File "/usr/share/gnumed/Gnumed/wxpython/gmHorstSpace.py", line 228, in 
> _on_notebook_page_changed
>     new_page.receive_focus()
>   File "/usr/share/gnumed/Gnumed/wxpython/gmPlugin.py", line 189, in 
> receive_focus
>     self._widget.repopulate_ui()
>   File "/usr/share/gnumed/Gnumed/wxpython/gmEMRBrowser.py", line 1410, in 
> repopulate_ui
>     self._pnl_emr_tree._emr_tree.patient = pat
>   File "/usr/share/gnumed/Gnumed/wxpython/gmEMRBrowser.py", line 1302, in 
> _set_patient
>     return self.__populate_tree()
>   File "/usr/share/gnumed/Gnumed/wxpython/gmEMRBrowser.py", line 255, in 
> __populate_tree
>     self.__update_text_for_selected_node()                                    
> # this is fairly slow, too
>   File "/usr/share/gnumed/Gnumed/wxpython/gmEMRBrowser.py", line 465, in 
> __update_text_for_selected_node
>     txt = emr.format_summary()
>   File "/usr/share/gnumed/Gnumed/business/gmClinicalRecord.py", line 1292, in 
> format_summary
>     end = vacc['date_given']
>   File "/usr/share/gnumed/Gnumed/pycommon/gmDateTime.py", line 674, in 
> calculate_apparent_age
>     raise ValueError('calculate_apparent_age(): <end> (%s) before <start> 
> (%s)' % (end, start))
> ValueError: calculate_apparent_age(): <end> (2000-09-17 01:00:00+03:00) 
> before <start> (2000-12-21 17:00:00+02:00)

GNUmed tries to calculate the "age" of a vaccination for
display. However, someone had previously modified that
patient's date of birth such that it came to fall *after* an
already documented vaccination. GNUmed did not deal very
gracefully with that fact (but, at least, did not display
invalid data).

Improvement is work-in-progress: GNUmed will attempt to check
existing clinical dates when the user attempts to modify the
DOB of an existing patient. Also, "negative" ages will be
displayed in a way that makes it painfully obvious that
something is amiss.

The easy fix is to reset the DOB of such patients to the
proper date (which I did for the public database) or to
remove/correct the offending clinical data item.

Best,
Karsten
-- 
GPG  40BE 5B0E C98E 1713 AFA6  5BC0 3BEA AC80 7D4F C89B



reply via email to

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