Re: [Gnumed-bugs] <bug>: ? on front desk

[Karsten Hilbert]

Hi Marc,

thanks for your report.

> user comment  : ? on front desk
> 
> client version: 1.6.14

The problem you are seeing:

> 2017-11-07 10:44:27  ERROR     gm.person 
> (/usr/share/gnumed/Gnumed/business/gmPerson.py::get_emr() #1966): still 
> failed to acquire EMR access lock, aborting (thread [140383943759616])
> 2017-11-07 10:44:27  ERROR     gm.gui 
> (/usr/share/gnumed/Gnumed/wxpython/gmExceptionHandlingWidgets.py::handle_uncaught_exception_wx()
>  #215): enabling debug mode
> 2017-11-07 10:44:27  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/lib/python2.7/dist-packages/wx-3.0-gtk2/wx/_core.py", line 
> 16765, in <lambda>
>     lambda event: event.callable(*event.args, **event.kw) )
>   File "/usr/share/gnumed/Gnumed/wxpython/gmEncounterWidgets.py", line 634, 
> in __refresh
>     enc = gmPerson.gmCurrentPatient().get_emr(allow_user_interaction = 
> False).active_encounter
>   File "/usr/share/gnumed/Gnumed/business/gmPerson.py", line 1967, in get_emr
>     raise AttributeError('cannot lock access to EMR for identity [%s]' % 
> self._payload[self._idx['pk_identity']])
> AttributeError: cannot lock access to EMR for identity [7022]

is the our old problem of sometimes having race conditions
between threads, especially when GNUmed asks the user whether
to continue a recent encounter (which can be worked around by
setting the interval between always-new-encounter and
always-old-encounter to zero or very small, say 1 second).

In version 1.7 I have reworked that to use a completely
different approach so we should not see that problem anymore
(and I haven't during development).

Sorry for the nuisance,
Karsten
-- 
GPG key ID E4071346 @ eu.pool.sks-keyservers.net
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346