Use on_flush (not on_flushed) when calling restored callbacks

Author: schloerke

shiny/bookmark/_bookmark.py

@@ -332,7 +332,10 @@ async def invoke_on_restore_callbacks():
 
             # Run the on_restored function after the flush cycle completes and
             # information is sent to the client.
-            @session.on_flushed
+            # Update: Using `on_flush` to have the callbacks populate the output message
+            # queue going to the browser. If `on_flushed` is used, the messages stall
+            # until the next `on_flushed` invocation.
+            @session.on_flush
             async def invoke_on_restored_callbacks():
                 print("Trying on restored")
                 if self._on_restored_callbacks.count() == 0:

shiny/session/_session.py

@@ -665,9 +665,6 @@ def verify_state(expected_state: ConnectionState) -> None:
                             with session_context(self):
                                 self.app.server(self.input, self.output, self)
 
-                            if self.bookmark.store != "disable":
-                                await reactive_flush()  # TODO: Barret; Why isn't the reactive flush triggering itself?
-
                         elif message_obj["method"] == "update":
                             verify_state(ConnectionState.Running)