stdio repl handling of both stderr and stdout for a form can be a problem sometimes

[sogaiu]

If using Janet's stdio repl [1], evaluating the following form leads to on-stray-output being called sometimes:

(do                                                     
  (print "out")
  (error "err"))

IIUC, this occurs because a callback (cb) gets cleared here as a result of on-stdout triggering before on-stderr (and they both call on-message).

By the time on-stderr gets called, cb ends up being bound to on-stray-output because of this.

In my limited testing at the command line (evaluating the same form), stdout output appears to complete after stderr output which is the reverse order of the callbacks being called. I suppose it's possible that that's just the way it could end up being when using event-based things like libuv?

---

[1] Possibly this may be an issue for other languages too as relevant code lives in fnl/conjure/remote/stdio.fnl.

[russtoku]

If you're up to modifying the Janet client code, you could try replacing:

conjure/fnl/conjure/client/janet/stdio.fnl

Line 5 in 4880144

stdio conjure.remote.stdio

with:

conjure/fnl/conjure/client/sql/stdio.fnl

Line 5 in 4880144

stdio conjure.remote.stdio-rt

Please see:

conjure/fnl/conjure/client/sql/stdio.fnl

Line 96 in 4880144

(eval-str (a.assoc opts :code (a.slurp opts.file-path))))

for how things are handled in the SQL client. This might work with a Janet REPL.

This is suggested as a simple work-around for handling other stdio clients. When @Olical completes his modularisation work (#500), hopefully, we can improve how the various REPLs work with Conjure.