Hello Olivier,
It has been fixed in lp:~openerp-dev/openobject-client/trunk-dev-client with
revision-info as
1381 [email protected] and will be merged soon
to the trunk client.
Thanks,
** Changed in: openobject-client
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of OpenERP
sa GTK client R&D, which is a bug assignee.
https://bugs.launchpad.net/bugs/682801
Title:
Loop looking for maintenance contract when server is broken
Status in OpenObject GTK Client:
Fix Released
Bug description:
Steps to reproduce:
0. Put server or client in debug_rpc mode for easier diagnostics
1. Login onto a working OpenERP Server with GTK client, until you see the menu
2. Stop the server, then start it again with an invalid database username or
password (e.g. -r foobar)
3. In GTK, try to refresh the menu that is still open (CTRL-R)
4. See that the GTK client loops endlessly, trying to call
maintenance.contract.status(), until you stop the server
-> Errors should be caught when calling maintenance.contract.status() with a
fallback that shows the error even if the maintenance status could not be
determined.
See also: bin/common/common.py:397 (from revision 1703)
Thanks!
_______________________________________________
Mailing list: https://launchpad.net/~openerp-dev-gtk
Post to : [email protected]
Unsubscribe : https://launchpad.net/~openerp-dev-gtk
More help : https://help.launchpad.net/ListHelp
