Fixed issue setting (Multi)Select value when options changed #291
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This fixes callbacks set on a MultiSelect widget which change the values. Due to the ordering of the watchers it can happen that the options change before the value change event has been propagated to the underlying bokeh model. Ideally we would have a way to elevate the precedence of watch calls which would allow us to order the watchers appropriately.
This PR simply addresses the symptom by skipping values that aren't found.