                                                       min-resend-time))
                                             (min next-based-on-eof rtt-resend-time)
                                             next-based-on-eof)
-        _ (log/debug (cl-format nil
-                                  "~a: Adjusted for RTT: ~:d"
-                                  message-loop-name
-                                  next-based-on-earliest-block-time))
+        _ (log/debug prelog
+                     (cl-format nil
+                                "Adjusted for RTT: ~:d"
+                                next-based-on-earliest-block-time))
         ;; There's one last caveat, from 298-300:
         ;; It all swirls around watchtochild, which gets set up
         ;; between lines 276-279.

                                                      actual-next
                                                      (System/nanoTime)
                                                      success))
                                (case (first success)
                                  ::drained (do (log/warn pre-log
                                                          ;; Actually, this seems like a strong argument for
                                                          ;; having a pair of streams. Child could still have
                                                          ;; bytes to send to the parent after the latter's

                                                    (map (fn [^bytes buf]
                                                           (count buf))
                                                         ->child-buffer))]
          (log/debug prelog
                     "Have"
                     previously-buffered-message-bytes
                     "bytes in"
