Synchronously create Document patch message to avoid race conditions #6028
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.
In order to support immediate dispatch of events when a Document lock is not required we have a special handler that sends messages on the websocket when Bokeh would ordinarily wait to acquire a lock explicitly. When a document lock is required, however, this custom handling can result in race conditions because the event isn't dispatched until long after the model has been added as a reference to the Document, meaning that when the message is created and dispatched it assumes the model has already been fully serialized. In order to work around this we immediately serialize events into messages ensuring that they correctly reflect the state of the document at the time the event is generated.
Fixes #6019