Ken Restivo writes:
> Only when conch is called, is this error generated. Not shelling out
> makes the problem go away. So it's an interaction between pr-str,
> conch and/or clojure.java.shell, and Timbre-- all three of which are
> manipulating *out* which I'm guessing is not thread-safe.
You ca
I've dug into this more, and it seems there's a third factor at work: conch.
In one of the functions called before this data is written, conch is shelling
out to a command. Obviously it's also mucking around with stdin/stdout/stderr.
Only when conch is called, is this error generated. Not shelli
So you actually want to print your data. I don't think it can be helped
then, two threads writing to the same buffer. I would have one of them use
a different buffer, write the logs to a file and tail it for instance.
On Wed, Oct 7, 2015 at 11:36 AM, Ken Restivo wrote:
> Yep. It doesn't help.
>
Yep. It doesn't help.
I also tried (.flush *out*) before... no dice.
-ken
--
-
On Wed, Oct 07, 2015 at 11:31:12AM +0300, Atamert Ölçgen wrote:
> Hi Ken,
>
> Have you tried with-out-str?
>
> On Wed, Oct 7, 2015 at 11:18 AM, Ken Restivo wrote:
>
> > I was trying to save a data structure us
Hi Ken,
Have you tried with-out-str?
On Wed, Oct 7, 2015 at 11:18 AM, Ken Restivo wrote:
> I was trying to save a data structure using prn-str.
>
> However, I'm also using Timbre for logging.
>
> My nice data structure is getting corrupted by INFO and DEBUG and other
> log messages from Timbre.
