Skip to content
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

The last activity shows irregular values after the update #18637

Closed
stalkerok opened this issue Mar 1, 2023 · 8 comments
Closed

The last activity shows irregular values after the update #18637

stalkerok opened this issue Mar 1, 2023 · 8 comments

Comments

@stalkerok
Copy link
Contributor

qBittorrent & operating system versions

2023-03-01_141916

What is the problem?

When updating from 4.5.1 to 4.5.2, all torrents in transfer list that did not have information about the last activity (infinity symbol ∞) began to show some huge values ​​(53 years ago).
2023-03-01_141228
This only affects building with lt2.0, probably because of these changes arvidn/libtorrent#7328. I would also like to note that the last activity is now saved after a system reboot, which fixes this problem #13150

Steps to reproduce

Update client

Additional context

No response

Log(s) & preferences file(s)

No response

@impdust
Copy link

impdust commented Aug 30, 2023

qBittorrent: v4.5.5
Operating System: Windows 64bit
Qt: 5.15.10
Libtorrent: 1.2.19.0

Issue still exists in v4.5.5. When upgrading from v4.5.4 to v4.5.5. My infinite ones stayed infinite, but all the ones that have activity now show Last Activity as 53 years ago and X days. Seems like it's related to the classic 1970s problem where a zero date is 1 January 1970. The invalid Last Activity date still shows after a system reboot.
LastActivty

@stalkerok
Copy link
Contributor Author

I made a backport of the fix to RC_1_2
The good news is that the last activity is now working, and when installing a clean client, it will display correctly.
The bad news: when updating, it will show 53 years ago.
I will close this as it is more of a side effect than a bug.

@klepp0906
Copy link

klepp0906 commented Sep 19, 2023

I made a backport of the fix to RC_1_2 The good news is that the last activity is now working, and when installing a clean client, it will display correctly. The bad news: when updating, it will show 53 years ago. I will close this as it is more of a side effect than a bug.

does this mean that for those of us with several thousand seeding torrents we're basically stuck with the borked last activity time? seems i have 4603 affected >.<

would switching to SQL perhaps fix it? or is it a db thing? manually editing db and changing it back to infinity or something possible to at least get them all functioning again?

@stalkerok
Copy link
Contributor Author

stalkerok commented Sep 21, 2023

does this mean that for those of us with several thousand seeding torrents we're basically stuck with the borked last activity time?

Just wait for activity to appear on the torrents and don't take the meaning of "53 years ago" seriously.

would switching to SQL perhaps fix it? or is it a db thing? manually editing db and changing it back to infinity or something possible to at least get them all functioning again?

If you want to reset the values, you need to manually edit the files .fastresume or SQL db, if you use it.

@klepp0906
Copy link

klepp0906 commented Sep 21, 2023

does this mean that for those of us with several thousand seeding torrents we're basically stuck with the borked last activity time?

Just wait for activity to appear on the torrents and don't take the meaning of "53 years ago" seriously.

would switching to SQL perhaps fix it? or is it a db thing? manually editing db and changing it back to infinity or something possible to at least get them all functioning again?

If you want to reset the values, you need to manually edit the files .fastresume or SQL db, if you use it.

Oh sweet. so those torrents will "right" themselves when they get activity? I feel like having 4000+ of my 15000 torrents (a reasonable chunk) still displaying 53+ years is evidence to the contrary. but maybe THAT many torrents hasnt seen activity since the fix i guess is possible.

when you said "a clean install" i took it as it would take newly added torrents to begin working again. If the fix is retroactive then this is way less an issue for me.

thank you for the information (and the fix for that matter!)

EDIT: unless i misunderstood you and by "dont take the meaning of....." you mean simply ignore the value going forward, permanently. if that is the case, i'll need to find a way to ferret out those 4000+ torrents from the rest, then find a way to bulk/mass edit them to whatever value indicates infinity (which i assume is equivalent to resetting them to working order). 1 by 1 is tantamount to a loss as theres no way. it's important I have the metric to track when doing pruning etc.. but not so important im going to edit 4000 files 1 by 1.

@stalkerok
Copy link
Contributor Author

I also have a lot of torrents, there are quite rare ones and I expect that they will not be updated soon. The client on the home server works non-stop after the update and a huge part of them has already been updated, so I'm just waiting.

@stalkerok
Copy link
Contributor Author

stalkerok commented Sep 21, 2023

I advise you to just wait, it will be the best solution. When activity appears on the torrents, they will come to order themselves, but it may take some time if these are rare torrents from some private tracker.
By a clean install, I meant that the user who has just installed the client will not notice these "53 years ago" at all.

@klepp0906
Copy link

I advise you to just wait, it will be the best solution. When activity appears on the torrents, they will come to order themselves, but it may take some time if these are rare torrents from some private tracker. By a clean install, I meant that the user who has just installed the client will not notice these "53 years ago" at all.

perfect! now i understand. thank you once again for your time!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants