This repository has been archived by the owner on Apr 11, 2022. It is now read-only.
forked from huntc/js-engine
-
Notifications
You must be signed in to change notification settings - Fork 20
Stream Stdout/Stderr instead of buffering #26
Comments
The fix for this is essentially on declaring a new type of message extending this: Taking Trireme as an example, where the message is handled: ...an addition handler is required for the new message, passing in the So that you know: the source and sink abstractions will be replaced in a few months with their equivalents from akka-streams. :-) However they will be semantically similar. HTH. |
On a related note, I've observed the following when using sbt-mocha:
This means that there's some overflow going on... |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Currently all logging is buffered inside a
ByteString
builder,which let's long running tasks appear unresponsive (e.g. rjs
optimize).
I tried to get my head around the
Engine
class and implementing a simplelogging trait where other logging implementations, such as sbt.streams,
can easily be wrapped.
However I failed handling the
ByteString
s and thecontext.become
calls.My
Logger
trait looks essentially like thisThe text was updated successfully, but these errors were encountered: