docs: explain how shared signal writes are confirmed in tests - #5999
Open
mcollovati wants to merge 1 commit into
Open
docs: explain how shared signal writes are confirmed in tests#5999mcollovati wants to merge 1 commit into
mcollovati wants to merge 1 commit into
Conversation
A write to a shared signal is applied optimistically and is visible through peek() right away, but the SignalOperation it returns completes only after the queued confirmation task has been run by runPendingSignalsTasks(). Document that, including why blocking on operation.result().get(...) before draining the queue always times out. Refs vaadin/browserless-test#202
mcollovati
added
flow
target/v25.2
Preview DeploymentThis PR has been deployed for preview. URL: https://docs-preview-pr-5999.fly.dev Changed pagesAdded content is highlighted in green; removed content is marked in red on each page.
Built from 6c32725 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
A write to a shared signal is applied optimistically and is visible through peek() right away, but the SignalOperation it returns completes only after the queued confirmation task has been run by runPendingSignalsTasks(). Document that, including why blocking on operation.result().get(...) before draining the queue always times out.
Refs vaadin/browserless-test#202