pprint uses refs internally rather than vars.  I was always a bit
suspicious about that...  Perhaps transaction retries are happening?


On Wed, Mar 13, 2013 at 3:19 PM, larry google groups <
lawrencecloj...@gmail.com> wrote:

> > tl;dr concurrency is hard
>
> Jason, if it was just a concurrency issue, it would happen when I use
> pprint. But the above mess only seems to happen with a very specific
> combination of Timbre and thread measuring functions.
>
>
>
>
>
>
> On Wednesday, March 13, 2013 12:16:46 AM UTC-4, Jason Lewis wrote:
>
>> tl;dr concurrency is hard
>>
>> Jason Lewis
>>
>> Email          jasonl...@gmail.com
>>
>> Twitter        @canweriotnow <http://twitter.com/canweriotnow>
>>
>> Blog           http://decomplecting.org
>>
>> About         http://about.me/jason.lewis
>>
>>
>> On Tue, Mar 12, 2013 at 11:27 PM, Michael Klishin 
>> <michael....@gmail.com>wrote:
>>
>>> 2013/3/13 larry google groups <lawrenc...@gmail.com>
>>>
>>>  At least some of this mangled text is coming from this function, which
>>>> is called at startup and then runs in its own thread
>>>
>>>
>>> If your app itself prints stuff to stdout/stderr, it is likely to be
>>> interleaved with the output from the spying thread.
>>> Thread execution order and time slicing is non-deterministic and nothing
>>> synchronizes writing to stdout/stderr
>>> to enforce ordering.
>>> --
>>> MK
>>>
>>> http://github.com/**michaelklishin <http://github.com/michaelklishin>
>>> http://twitter.com/**michaelklishin <http://twitter.com/michaelklishin>
>>>
>>> --
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Clojure" group.
>>> To post to this group, send email to clo...@googlegroups.com
>>>
>>> Note that posts from new members are moderated - please be patient with
>>> your first post.
>>> To unsubscribe from this group, send email to
>>> clojure+u...@**googlegroups.com
>>>
>>> For more options, visit this group at
>>> http://groups.google.com/**group/clojure?hl=en<http://groups.google.com/group/clojure?hl=en>
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "Clojure" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to clojure+u...@**googlegroups.com.
>>>
>>> For more options, visit 
>>> https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out>
>>> .
>>>
>>>
>>>
>>
>>  --
> --
> You received this message because you are subscribed to the Google
> Groups "Clojure" group.
> To post to this group, send email to clojure@googlegroups.com
> Note that posts from new members are moderated - please be patient with
> your first post.
> To unsubscribe from this group, send email to
> clojure+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/clojure?hl=en
> ---
> You received this message because you are subscribed to the Google Groups
> "Clojure" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to clojure+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

-- 
-- 
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to