Ability to view performance reports without internet access
See original GitHub issueI’m working in an airgapped environment. The general dask dashboard running on the scheduler works really well.
But when I attempt to view performance reports, I get a blank page and it seems that Bokeh is attempting & failing to connect to an external resource. The http server that I started to view it reports the request and replies with a 304:
$ python -m http.server
Serving on ...
{IP} {date} "GET /dask-report.tml HTTP/1.1" 304
The page is blank an the the developer console shows:
Has anyone else had this and has a workaround?
Issue Analytics
- State:
- Created 2 years ago
- Comments:9 (9 by maintainers)
Top Results From Across the Web
11 Best Internet Monitoring Software - Comparitech
We review the best internet connection monitoring software for 2022. ... Performance Monitor enable network managers to plan capacity for ...
Read more >Network Performance Reporting Tool | SolarWinds
Easily manage fault and availability using network monitoring reports with SolarWinds Network Performance Monitor. Download a free 30-day trial!
Read more >What is Network Performance Monitoring? - TechTarget
Network performance monitoring is a process of measuring and monitoring the quality of service of a network to understand if it is properly...
Read more >Network Performance Monitor solution in Azure - Microsoft Learn
Network Performance Monitor in Azure helps you monitor the performance of your networks, in near real time, to detect and locate network ......
Read more >Network Performance Monitoring Reviews 2022 - Gartner
Read Network Performance Monitoring Tools reviews verified by Gartner. Compare and find the best Network Performance Monitoring Tools for your organization.
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
This explains so much. Thanks for figuring that out @jakirkham!
@jrbourbeau, I got a response from GitHub. The gist is we have to check the checkbox for the PR to close the issue. If it is not checked, the issue will not be closed