openerp-india team mailing list archive
-
openerp-india team
-
Mailing list archive
-
Message #26993
[Bug 1264950] [NEW] 7.0: stock_picking.action_cancel can cause RuntimeError: maximum recursion depth exceeded
Public bug reported:
During the testing of an addon for a customer, in which I call
cancel_assign on stock pickings I came across the exception for which a
stack trace is attached to this bug report.
It looks like writing to the state attribute of the picking generates
call to trg_write, even if the value written is the same as the existing
value. So a possible fix would be to check for the state of the picking
and only issue a call to write if the value is to be modified.
** Affects: openobject-addons
Importance: Undecided
Status: New
** Attachment added: "stack trace"
https://bugs.launchpad.net/bugs/1264950/+attachment/3937654/+files/recursion_depth_exceeded.txt
--
You received this bug notification because you are a member of OpenERP
Indian Team, which is subscribed to OpenERP Addons.
https://bugs.launchpad.net/bugs/1264950
Title:
7.0: stock_picking.action_cancel can cause RuntimeError: maximum
recursion depth exceeded
Status in OpenERP Addons (modules):
New
Bug description:
During the testing of an addon for a customer, in which I call
cancel_assign on stock pickings I came across the exception for which
a stack trace is attached to this bug report.
It looks like writing to the state attribute of the picking generates
call to trg_write, even if the value written is the same as the
existing value. So a possible fix would be to check for the state of
the picking and only issue a call to write if the value is to be
modified.
To manage notifications about this bug go to:
https://bugs.launchpad.net/openobject-addons/+bug/1264950/+subscriptions
Follow ups
References