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

COT shouldn't clone existing items to lower InstanceID #70

Closed
glennmatthews opened this issue Nov 29, 2017 · 0 comments
Closed

COT shouldn't clone existing items to lower InstanceID #70

glennmatthews opened this issue Nov 29, 2017 · 0 comments
Assignees
Labels

Comments

@glennmatthews
Copy link
Owner

Because COT always picks the lowest unused InstanceID when creating an Item, when given an OVF with non-consecutive InstanceIDs (e.g., 1, 2, 3, 4, 10, 11, 12, 2001, 2002) then cloning existing Items will result in them being out-of-order (e.g., cloning Item 2002 will result in a new Item with InstanceID 5), which can subsequently cause problems because COT iterates over items in InstanceID order (so the newly cloned Item comes before the item it was cloned from, rather than after as COT expects).

Probably COT should always clone to an InstanceID higher than the item being cloned.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant