-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Glances Network Traffic Error #1608
Comments
Thanks for the report, yeah I've noticed that too, there also seem to be two more widgets broken as mentioned here: |
Hi @CrazyWolf13, I believe you can also add gl-network-interfaces to your list. Dashy is unable to recognize that the interface is UP and retrieve the rx/tx data: Data is present at the URL Dashy is sending requests to so I guess there's some issue with processing it?
|
I am also experiencing that issue. |
Environment
Self-Hosted (Bare Metal)
System
Chrome 125
Version
3.1.1
Describe the problem
When using the source code v3.1.1 with Glances v4.0.7 the Network Traffic widget does not display any values (screenshot below) with these two errors in console:
Error: <path> attribute d: Unexpected end of attribute. Expected number, "M".
and
Error: <path> attribute d: Expected number, "Mundefined,NaNLLu…".
both at src/components/Widgets/GlNetworkTraffic.vue:75 and at frappe-charts.min.esm.js:1.
These errors appear regularly with every attempted update of the widget.
The same config worked with v3.0.1 without any issue.
Additional info
Active widget:
Active config:
Error stack:
Full log:
dashy.log
Please tick the boxes
The text was updated successfully, but these errors were encountered: