Metrics tab not working
See original GitHub issue🐛 Bug
Click the Metrics
tab, it shows nothing but a Something went wrong
notification.
To reproduce
Use the pytorch_ignite integration.
Expected behavior
Show metrics pannel.
Environment
- Aim Version 3.7.5
- Python version 3.7.10
- pip version 21.1.3
- Ubuntu 20.04
- I’m using the PyTorch Ignite integration.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:8 (5 by maintainers)
Top Results From Across the Web
Workload metrics tab not displayed · Issue #36587 · rancher ...
This repository uses an automated workflow to automatically label issues which have not had any activity (commit/comment/label) for 60 days.
Read more >Troubleshooting with the All Metrics Tab - VMware Docs
Metric charts are based on the metrics for the active map object that you think can help you identify the cause of a...
Read more >Query metrics tab doesn't work! HELP - Grafana Community
The problem occurs when i try to edit my panel. That's when my query dissapeares and the metrics tab doesn't show any options...
Read more >Code Metrics Results tab not showing the results
When I try to see Code Metrics Result and I select the tab, it doesn't change but shows the previous tab. If I...
Read more >Diagnose the Problem with the Metric Browser Tab - TechDocs
The following tools in the metric browser tab help you find more information about an issue: Historical metrics. Search. Transaction Tracer.
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
Confirming that clearing
127.0.0.1
cache or opening in a private browsing window resolves the issue. (Firefox)Hey @louis-she, the fix for this issue has been shipped with
v3.8.0
To upgrade please runpip install aim --upgrade