eliot
eliot copied to clipboard
Eliot: the logging system that tells you *why* it happened
I'm seeing this traceback in an `@eliot.twisted.inline_callbacks`-decorated method .. I'm not sure exactly what is happening yet and some initial attempts to re-create the error with a smaller test-case hasn't...
it would be nice to have a pytest integration that handles traces at test setp/call/teardown level as well as including eliot trees/traces onto a test report
Hi @itamarst - I extended the jsonencoder to handle pandas in my own code and it worked well. Wondering if you're interested in developing something like this as part of...
`contextvars` support in newer Twisted might be a less verbose alternative to current approach, it might Just Work.
This adjust `eliot_friendly_generator_function` to handle the use case of #472 but doesn't do the work of exposing it to users.
Fixes #449. I'm not sure if this a great solution, but it appears to fix the issue by letting Failure's stack walking find the right context. When an inlineCallback completes...
Consider: ``` from eliot.twisted import inline_callbacks from twisted.internet.defer import fail @inline_callbacks def foo(): yield yield bar() @inline_callbacks def bar(): yield raise Exception("Some problem") foo() ``` This results in the following...
There is the private `eliot_friendly_generator_function`, which is almost what I need, but it initializes the context on the first call of `next`/`send`, rather than on creation. My use cases is...
It appears that it will serialize all messages, until the first one that does not validate, or none, if there are unflushed tracebacks.
It would be really great, if you could use eliot without modifying the source code. I would like to provide a list of methods which should create events: ['mymodule.foo.bar', '....]...