Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Bokeh Task Stream doesn't get cleared after a client.restart()
See original GitHub issueAs it says in the title. Ideally for me a client.restart() would clear the previous tasks.
If the current behaviour is as intended I’m fine with that, I’m just opening this issue in case the current behaviour isn’t intended.
Issue Analytics
- State:
- Created 5 years ago
- Comments:8 (8 by maintainers)
Top Results From Across the Web
API — Dask.distributed 2022.12.1 documentation
The client connects to and submits computation to a Dask cluster (such as a ... Get task stream data from scheduler ... Restart...
Read more >python - dask.config.get cannot get anything?
I came here because I get the same problem, and your solution doesn't work for me. I still get a KeyError using dask.config.get('distributed....
Read more >Futures — Dask 2.23.0 documentation
Start Dask Client¶. You must start a Client to use the futures interface. This tracks state among the various worker processes or threads:....
Read more >Working notes by Matthew Rocklin - SciPy
We connect a client to our Dask cluster, composed of one centralized dask-scheduler process and ... Pandas users should find the code above...
Read more >Dask.distributed Documentation
Getting Started 1 ... client = Client() # set up local cluster on your laptop. > ... Note: At least one dask-worker must...
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 Free
Top 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
Just that it can clutter the task view with history I don’t care about - e.g.
I want to see what happened in my most recent run but because the old run is kept around each task in the task stream appears infinitesimally small making it hard to extract any useful information visually.
Since it seem this is intended I’ll close this.