-
Notifications
You must be signed in to change notification settings - Fork 415
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
Incorrect Traffic Period Sorting #2818
Comments
Does this bug date back to version 4? Or does it only happen on version 5? |
not sure I don't have time to test rn, but remind me in ~1 week (if I forgot to do it before then) and I'll test it |
There are some irregularities in the diagnostics you provided, but can you clarify exactly what you don't like. It looks to me to be mostly functioning as intended. January will always be the first bar on the left and December will always be the last bar on the right. The orientation of the months will never shift. Notice that the individual bars are two different shades of green, one brighter and one darker (the same is true for download which is blue, but downloaded amount is not significant in relation to uploaded amount in your case and so does not appear prominently in your image). Data for the current year is the brighter green, whereas data from the prior year will be the darker green. The only time all the bars will be bright green, will be during the month of December when all currently displayed data is from the current year. Now for the irregularities in your image, I think they can mostly be explained by missing or corrupt data in the stored traffic information. I am assuming that there is no data for 03.2023 or 03.2024 which is why that bar is completely missing including its label. There is no data for 04.2024, which is why the data from 04.2023 is being displayed which would not be the case if there was 04.2024 data in the database. As for why 08.2023 data is being displayed in the 9th position (or at least that's what the label says), is the only thing that I have no explanation for and would consider not working as intended. It would be a reasonable assumption that, if there IS corruption in some of the stored traffic data, that that could have somehow confused the graph renderer and led it to display some of the information in the wrong place. Here is another screenshot of traffic for additional reference. Unfortunately since we are in the month of December, none of the data in this graph is from the prior year and therefore, none of the bars are the darker green color. Also, I cant help with this, but for anyone to determine whether your issue is a bug in ruTorrent, or just your installation working with incomplete/corrupt data, they would need a copy of all your stored traffic data. Additionally, please read https://github.com/Novik/ruTorrent/wiki/PluginTrafic which has some documentation on how the plugin works. Pay specific attention to this point:
Finally, to emphasize the above if it isn't apparent, until you load the ruTorrent webpage in your browser and login, after bringing up rtorrent, the Traffic plugin is not recording data (unless you have added the correct command to your |
what irregularities in the diagnostics?
I'll provide a tarball of all of my traffic data later.
hmm, this is good to know. I was not aware of this. |
Please complete the following tasks.
Tell us about your environment
Web Browser: Firefox 134.0b2
ruTorrent: v5.1.1
PHP: 8.3.14
OS: Arch Linux 6.11.9-arch1-1 x86_64
Tell us how you installed ruTorrent
via the
rutorrent
AUR package (the package is currently out of date, so I changed the version from5.0.0
to5.1.1
manually then set the sha256 for it to'SKIP'
)Describe the bug
The sorting of dates is incorrect.
The dates (in the provided screenshot) are sorted in the following order:
How it manages to sort like this is entirely beyond me, unless it's some type of race condition
Steps to reproduce
trafic
[sic] pluginExpected behavior
Does not do this.
Additional context
No response
The text was updated successfully, but these errors were encountered: