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

Force recheck and ".!qB" #3890

Closed
yar3333 opened this issue Oct 3, 2015 · 7 comments
Closed

Force recheck and ".!qB" #3890

yar3333 opened this issue Oct 3, 2015 · 7 comments

Comments

@yar3333
Copy link

yar3333 commented Oct 3, 2015

Will be good, if qBT check not only "file.ext.!qB", but "file.ext" too.
v3.3.0beta

@chrishirst
Copy link
Contributor

It does.

Failing that, you need to provide a much better explanation of what you consider the problem to be.

@yar3333
Copy link
Author

yar3333 commented Oct 4, 2015

I add new torrent and see what already have some files (option "Use .!qB" is checked). I move files into torrent folder and click "Recheck" - after rechecking: nothing found. I rename files into *.!qB and click "Recheck" again - files found.

@ngosang
Copy link
Member

ngosang commented Nov 6, 2015

@sledgehammer999 should be tested before v3.3.0 release. Some tag?

@sledgehammer999
Copy link
Member

I think this bug wasn't introduced in v3.3.x but exists already, mostly due to limitations on our implementation(or libtorrent's). Basically libtorrent expects files with .!qB. To properly fix this we need to check for the existence of the regular files and if they exist rename them in libtorrent. But if the .!qB files exist by renaming them libtorrent will probably overwrite the "regular ones". In any case, I don't think this is simple enough to fix in time.
And maybe @glassez can throw ideas on how to do this.

@glassez
Copy link
Member

glassez commented Nov 10, 2015

I don't think this is simple enough to fix in time.
And maybe @glassez can throw ideas on how to do this.

We need to think carefully on this. Should not rush with this...

@slrslr
Copy link
Contributor

slrslr commented Jul 4, 2018

Here i described same or very similar issue and how to reproduce it. This issue is v.3.3 and my issue is v. 4.1

@sledgehammer999
Copy link
Member

This issue has been closed and locked for being too old, and thus either most likely resolved in recent versions or no longer applicable.
If you experience the reported problem or similar in the latest version, please open a new issue report with the requested information in the issue template.

A new issue report with relevant updated data gathered from the latest version is preferable to necroing an old report with a comment like "still happens in version x.y.z", even if you think the bug is the same, or suspect of a regression.
Due to the changes made to the qBittorrent code and its dependencies over time, the exact cause of your problem could be totally different than the original one, despite the visible symptoms of the bug being similar.
Thus, providing relevant updated information is crucial to find and fix the root cause of a recurrent problem or regression.

Thank you for your contributions.

@qbittorrent qbittorrent locked and limited conversation to collaborators Oct 29, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

6 participants