E&S CVS Commit: Trellis - Fixes for various complex scenarios,
such as:
pje at eby-sarna.com
pje at eby-sarna.com
Mon Nov 3 18:22:45 EST 2008
Author: pje
Date: Mon Nov 3 18:22:37 2008
New Revision: 2595
URL: http://svn.eby-sarna.com?rev=2595&view=rev
Log:
Fixes for various complex scenarios, such as:
* False-positive detection of circularity in some cases where
retried rules are related, but not actually circular.
* Lazily-created components in uninitialized rules called from
@compute or @perform rules could trigger read-only violation
errors.
* If a "future" value was accessed from both rule and non-rule
code in the same transaction, it could trigger a silent,
partial rollback of the non-rule code, leading to inexplicable
result.
Also, as a side effect of these changes, CircularityError
instances now includes a path indicating at least one possible
cycle in the given routes, and "futures" must now be copyable
objects.
Many thanks go to Sergey Schetinin, who not only reported these
issues, but also diagnosed them and provided both test cases and
suggestions for fixes. Thank you, Sergey!
Modified:
Trellis/README.txt
Trellis/peak/events/stm.py
Trellis/peak/events/trellis.py
Trellis/test_trellis.py
More information about the source-changes
mailing list