You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The up/down/sent/received columns of the IPv8 debug info are all empty. The details tab is also empty.
To Reproduce
Steps to reproduce the behavior:
Enable statistics and restart Tribler.
Click on debug.
Click on IPv8 tab.
See lack of info in Overlays and Details tabs.
Expected behavior
Traffic info for all of the IPv8 overlays should be shown.
Screenshots
Desktop (please complete the following information):
OS: Ubuntu 22.04
Tribler's version: 7.13.0-GIT
Additional context
The cause for this behavior is that request_manager.post("ipv8/overlays/statistics", data={"enable": "True", "all": "True"}) is not invoked in debug_window.py (or anywhere else after startup) when Tribler's statistics setting is enabled.
The text was updated successfully, but these errors were encountered:
However, this call enables statistics on all loaded IPv8 overlays.
This was fine, in the past, when the call was made after all IPv8 + Tribler overlays were loaded.
However # 2, after the refactoring of Tribler's component loading, this call was moved to before any IPv8 or Tribler overlays were loaded. So, now, this code is enabling statistics for exactly 0 loaded overlays: it's doing nothing.
Describe the bug
The up/down/sent/received columns of the IPv8 debug info are all empty. The details tab is also empty.
To Reproduce
Steps to reproduce the behavior:
IPv8
tab.Overlays
andDetails
tabs.Expected behavior
Traffic info for all of the IPv8 overlays should be shown.
Screenshots
Desktop (please complete the following information):
Additional context
The cause for this behavior is that
request_manager.post("ipv8/overlays/statistics", data={"enable": "True", "all": "True"})
is not invoked indebug_window.py
(or anywhere else after startup) when Tribler's statistics setting is enabled.The text was updated successfully, but these errors were encountered: