Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    andy-landy
    @andy-landy
    This room is intended as a lighter alternative to Github Issues page. Please feel free to ask any questions, clarifications and leave feedback.
    Kryštof Řeháček
    @Krystofee
    Hello there :) I’m a bit worried about the security in production environment. What if I use the traceback with variabled and some other service such as rollbar or sentry? Is there some simple way to prevent including api tokens and other private info within the traceback?
    5 replies
    Kryštof Řeháček
    @Krystofee
    image.png
    kmonson
    @kmonson
    Hi @andy-landy. Are there any plans to support output asyncio.Task.get_stack()?
    1 reply
    I don't know if this is by design or an oversight, but when calling Task.result() any raised exception does not set traceback to that of the task but instead to the traceback of the caller.
    kmonson
    @kmonson
    To get the call stack of the task at the time the exception was raised you need to call Task. get_stack() which returns a list of frame objects. https://docs.python.org/3/library/asyncio-task.html#asyncio.Task.get_stack
    kmonson
    @kmonson
    Bleh, never mind. It appears that you can't currently get the frame info for a task outside of the task.
    Unless I'm missing something.
    kmonson
    @kmonson
    I was missing something. We are using multiprocessing and it handles formatting of the remote exception itself. Still asyncio.Task.get_stack() support would be nice.
    kmonson
    @kmonson
    Hi again @andy-landy. How would you feel about adding support for outputting the stack trace as HTML? Our use case produces a very large output in many cases. We would like to capture the trace and put it in a file to be opened later. Being able to make that an HTML file where the stack frames contents could be collapsed and expanded would be very useful.
    4 replies