Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cascade delete of VariableSets does not increment concurrency version #5025

Closed
NickJosevski opened this issue Oct 24, 2018 · 2 comments

Comments

@NickJosevski
Copy link

commented Oct 24, 2018

A a dirty write may occur on a VariableSet if it happens during a cascade delete because the cascade operation does not increment the concurrency version property on VariableSet.

Impacts all prior versions of Octopus

Work around

Do not save variables while deleting entities in Octopus that may update variables

@NickJosevski

This comment has been minimized.

Copy link
Author

commented Oct 29, 2018

Release Notes: Improvements to concurrency protection on variable sets

@lock

This comment has been minimized.

Copy link

commented Jan 27, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. If you think you've found a related issue, please contact our support team so we can triage your issue, and make sure it's handled appropriately.

@lock lock bot locked as resolved and limited conversation to collaborators Jan 27, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
1 participant
You can’t perform that action at this time.