    ;; it less obviously a win.
    success]
   (let [prelog (utils/pre-log message-loop-name)  ; might be on a different thread
-        fmt (str "Awakening event loop that was sleeping for ~:d ms "
+        fmt (str "Awakening event loop that was sleeping for ~g ms "
                  "after ~:d at ~:d\n"
                  "at ~:d because: ~a")
         now (System/nanoTime)

                                (- end mid)))
          nil)))))

;;; I really want to move schedule-next-timeout! to flow-control.
;;; But it has a circular dependency with trigger-from-timer.
;;; Which...honestly also belongs in there.

                                     (assoc-in state
                                               [::specs/incoming ::specs/parent->buffer]
                                               message))
                      ;; This is a prime example of something that should
                      ;; be queued up to be called for side-effects.
                      ;; TODO: Split those out and make that happen.
                      state' (to-child/forward! io-handle (or pre-processed
                                                            state))]
                  ;; This will update recent.
