Thanks for the offer to help.
I was hoping someone would see an apparent bug in the outline, so i wouldn't
have to build a a SSCCE
unfortunately, that wasn't going to fly, so I built out a self-contained
version of the issue
Before sharing it, I added in some docs references to the example...
On Jan 19, 2014, at 1:27 PM, Jonathan Vanasco wrote:
> Before sharing it, I added in some docs references to the example...
>
> and then I noticed something peculiar, and seemed to have solved the problem
> !
and that right there is a major reason we ask people for SSCCEs when
they
The log is very valuable to me for debugging, but I'd love to know how to
improve the precision of the time stamp. My log shows stuff like this:
2014-01-19 12:44:37-0500 [-] 'SCPProtocol.ackNotReceived:
aa23827e20547c6aca71ecfcdeb486a99fe6cf314e1b84e687296821a8ca423a'
2014-01-19 12:44:37-0
>From what I can tell in a few old bugs and the API docs, the key is to
monkey-patch log.FileLogObserver.timeFormat.
Dustin
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
On 19 Jan, 09:27 pm, twisted-pyt...@2xlp.com wrote:
Thanks for the offer to help.
i'm not sure of the specifics on how / why this manifests, but if I
just use runInteraction and bypass using `deferToThread`, everything
works out perfect.
To intentionally slightly misinterpret you, the speci
On 19 Jan, 11:47 pm, dus...@v.igoro.us wrote:
From what I can tell in a few old bugs and the API docs, the key is to
monkey-patch log.FileLogObserver.timeFormat.
Or just politely set it on the instance of FileLogObserver your
application creates so as to avoid global side-effects. :)
Jean-P
On Sun, Jan 19, 2014 at 8:55 PM, wrote:
> On 19 Jan, 11:47 pm, dus...@v.igoro.us wrote:
>>>
>>> From what I can tell in a few old bugs and the API docs, the key is to
>>
>> monkey-patch log.FileLogObserver.timeFormat.
>
>
> Or just politely set it on the instance of FileLogObserver your applicati
