Skip to content

Flush after output has been recalculated #1361

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

Closed
wants to merge 5 commits into from

Conversation

cpsievert
Copy link
Collaborator

Closes #1360

@cpsievert cpsievert force-pushed the flush-after-calculate branch from 1387307 to c9ba49c Compare May 7, 2024 20:08
Comment on lines +1450 to +1454
# Needed so that Shiny knows to flush the outputs. Even if no
# outputs/errors are queued, it's necessary to flush so that the
# client knows that progress is over.
if isinstance(session, AppSession):
await session._flush()
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

NOTE: this is a bit different from how we handle this in R (via requestFlush()), but we currently don't have a request_flush() in Python

@cpsievert cpsievert requested a review from wch May 7, 2024 20:40
@cpsievert
Copy link
Collaborator Author

See #1360 (comment) (we'll handle the issue in shiny.js, not here)

@cpsievert cpsievert closed this May 7, 2024
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.

1 participant