Caleb Collins-Parks
Caleb Collins-Parks
Thanks! On Mon, Oct 24, 2022, 7:06 AM Lily Foote ***@***.***> wrote: > Closed #31 as completed. > > — > Reply to this email directly, view it on GitHub...
Ah - maybe kolo ran when I ran our unit/integration tests, some of which set custom times and do API calls? :thinking: :thinking: I'm also seeing a bunch of requests...
> Any change you ran the tests with kolo run or still have some with kolo.enabled() blocks set? I double-checked: no kolo run and I don't have any kolo in...
Talked about this on a call, turns out certain tests are setting DEBUG to true, causing kolo to run. That explains that! It would still be nice if requests were...
I also have a performance issue, even with the slow panels of debug toolbar disabled. We have a large (~5k files) codebase, so it's understandably slow for Kolo to go...
Talked about this in a call, we still see a performance hit even with debug toolbar disabled completely. One option I forgot to mention during the call is that you...
by tracked I mean show up in sidebar, see performance details, variables, etc...
Sweet! I just tried running it. Here are my impressions. 1. :heavy_check_mark: Like you said, just `kolo run ...`. Very easy to do. 2. :heavy_check_mark: Data immediately shows up, which...
> We also now have a @kolo.enable decorator and a with kolo.enabled() context manager to trace smaller, specific blocks of code: https://docs.kolo.app/en/latest/kolo-enabled.html Thanks for this, I was able to use...
I also got this error. Can this issue be reopened please? There is a workaround for it but it's still a bug.