Static Performance Report: Allow stacklevel optional argument for gathering source code
See original GitHub issueAllow the user to specific which level of the call stack is used for capturing source code in the static report generated by dask.distributed.performance_report
. In some cases, the method might be wrapped by another function so allowing users to ability to select which level to include in the report might be helpful to them.
with dask.distributed.performance_report(filename=filename, stacklevel=2):
...
I am happy to pick this up as I’m working on related functionality.
Issue Analytics
- State:
- Created 2 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Source code for distributed.client - Dask documentation
TimeoutError`` **kwargs : dict Optional keyword arguments for the function Returns ... client.gather(c) # doctest: +SKIP 33 You can also call Client with...
Read more >Python Logging Guide - Best Practices and Hands-on Examples
LogRecord objects capture the msg and args arguments of logging methods and the exception and call stack information along with source code ......
Read more >"Optional" should not be used for parameters
Java static code analysis. Unique rules to find Bugs, Vulnerabilities, Security Hotspots, and Code Smells in your JAVA code. All rules 649 ·...
Read more >Profiler Code Overview — Firefox Source Docs documentation
Optional profiler pause, which stops most recording, usually near the end of a session so that no data gets recorded past this point....
Read more >coiled.core — Coiled documentation - Coiled Docs
Source code for coiled.core ... be looked up or created. default_cluster_timeout Default timeout in seconds to ... For a list of hosted performance...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Conflicted meaning that both James and I work for Coiled, and this is necessary for internal Coiled work. This seems pretty innocuous, but we’d feel more comfortable giving the green light if some non-Coiled person signed off on it. I think that @jakirkham 's comment does that. Thanks!
Woo! @ndanielsen a PR adding
stacklevel=
would be very welcome