From 5f0a21b5cae780fa33b2a92cb6743a2f9d0949d8 Mon Sep 17 00:00:00 2001 From: Jason Grout Date: Fri, 26 Jul 2019 06:32:20 -0700 Subject: [PATCH] Revert status message updates to revert back to exactly three status message states. We still remove the part about spoofed status messages since it really is not part of the kernel message spec. --- docs/messaging.rst | 7 ++----- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/docs/messaging.rst b/docs/messaging.rst index 77ab743ac..7eb6435a6 100644 --- a/docs/messaging.rst +++ b/docs/messaging.rst @@ -1228,7 +1228,8 @@ Message type: ``status``:: content = { # When the kernel starts to handle a message, it will enter the 'busy' # state and when it finishes, it will enter the 'idle' state. - execution_state : ('busy', 'idle', other optional states) + # The kernel will publish state 'starting' exactly once at process startup. + execution_state : ('busy', 'idle', 'starting') } When a kernel receives a request and begins processing it, @@ -1239,10 +1240,6 @@ it shall publish a status message with ``execution_state: 'idle'``. Thus, the outputs associated with a given execution shall generally arrive between the busy and idle status messages associated with a given request. -A kernel may send optional status messages with execution states other than -`busy` or `idle`. For example, a kernel may send a status message with a -`starting` execution state exactly once at process startup. - .. note:: **A caveat for asynchronous output**