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

In the example node app when looping through the staged resources, co… #43

Closed
wants to merge 1 commit into from

Conversation

bakaleks
Copy link

@bakaleks bakaleks commented Jan 9, 2019

…nnection_resource iterator gets modified by nmos::modify_resource() while iterating. That results in an unpredictable behaviour when bulk-staging several activations and not all changes get activated. This is only triggered when several receivers(possibly senders too) are registered within the node.

This fix proposes copying iterator elements into a separate vector beforehand.

Reproducable by leaving out iterator-copying and running AMWA's nmos-testing IS05, test_41 (separate pull request in progress there).

…nnection_resource iterator gets modified by nmos::modify_resource() while iterating. That results in an unpredictable behaviour when bulk-staging several activations and not all changes get activated. This is only triggered when several receivers(possibly senders too) are registered within the node.

This fix proposes copying iterator elements into a separate vector beforehand.

Reproducable by leaving out iterator-copying and running AMWA's nmos-testing IS05, test_41 (separate pull request in progress there).
@bakaleks
Copy link
Author

bakaleks commented Jan 9, 2019

Created new test for this AMWA-TV/nmos-testing#73

@garethsb
Copy link
Contributor

Thank you for the report and proposed fix. I think it should be possible to solve this without the need to copy whole resources or even iterators to resources by tweaking the iteration instead. I'm going to investigate this locally; hopefully will push a fix later today.

garethsb added a commit that referenced this pull request Jan 10, 2019
… to @bakaleks, Alexi Bakanov, Bridge Technologies, for the original report in PR #43)

(cherry picked from commit 3fb5925153db37fe44a8079da9aa89c2bb2a1e13)
@garethsb
Copy link
Contributor

Hi @bakaleks

I believe this is resolved by 7f1823c.

Thanks again for the detailed bug report, investigation and test case - I'll add a review of AMWA-TV/nmos-testing#73 soon as well.

See you in Newbury next week!

@bakaleks
Copy link
Author

Thanks Gareth! Great stuff!

@bakaleks bakaleks closed this Jan 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants