Skip to content

Conversation

@schlick
Copy link
Member

@schlick schlick commented Nov 4, 2016

When the store yields inside a with_lock call, subsequent requests will block until the lock is available. At that time the object will be reloaded. However, the previous implementation in decision_tree set the ivars before calling start_workflow. This led to the ivars holding values from the original instantiation of the store and incorrectly processing against those. They need to be set after the store object has been reloaded.

Also, I've had to put in early returns to stop decisions and entry points from being run after the workflow has already finished.

…w and do not execute decisions or entry points after workflow has finished
@schlick schlick force-pushed the AV-3601-initialise-after-lock branch from 33e0f4d to 0b0d764 Compare November 4, 2016 03:43
Copy link

@s01ipsist s01ipsist left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@schlick schlick merged commit 98e897c into develop Nov 4, 2016
@schlick schlick deleted the AV-3601-initialise-after-lock branch November 4, 2016 04:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants