Now for the issue at hand: I think there are other legitimate reports of qBittorrent failing to save/truncating configuration files/fastresumes under some circumstances that have so far not been addressed. There's also a small portion of issues that are known but for which we must wait on something else in order to fix them (e.g. Perhaps we should change this going forward I've been entertaining the idea of moving all feature requests to the "Ideas" section under "Discussions" the "Feature request" label would be reserved for issues opened about planning/discussion of implementation details of a feature request that someone wants to implement from the "Ideas".Īdditionally, many of the opened reports right now that are not feature requests also suck and are on the chopping block next. Then, it can either be rejected or accepted, and only at that point will the feature request issue be closed. Non-reproducible crash reports, or crash reports with no debug symbols of ancient versions are also not useful.Īlso, a significant portion of the open issues are actually feature requests (almost 1k now: ).įeature requests tend not be closed at all, as per the team's policy to increase the chances that someone will take it upon themselves to start a legitimate discussion and effort about implementing it. The issue tracker management has improved significantly since about 2 years ago or so - the singal-to-noise ratio is much higher, the vast majority of reports are assigned a label and receive a response from a project member or contributor within a short time of being posted, and the team members and contributors are able to more readily focus on the most pressing problems.įurthermore, contributors have been steadily fixing bugs and improving the project, even collaborating with upstreams such as libtorrent.Ī lot of issues are closed because they suck (not enough information, can't be reproduced, the OP just dumped a non-reproducible report and bailed, users don't understand how BitTorrent works, etc.).Ī lot of the time people either don't read the contributing guidelines or wiki and don't provide the information requested in the issue template, or don't have enough expertise to meaningfully contribute the required information to track down a legitimate problem, or their systems are utterly broken messes of anti-virus and bloatware that interferes with the normal operation of qBittorrent and other programs, or all of these or some combination of these at once. This is an unfair insinuation that either the issue tracker is mismanaged, or that the bugs are not getting fixed, or both. There's a reason there are 2.3k open issues (as of now), and most of them "closed due to inactivity". Guess being condescending and giving people less reasons to use the software comes before helping fix simple QoL problems for users. I was under the impression that open source can be improved by open discussion and that it could grow. This is the appropriate issue and it's open right now, others in this very thread already confirmed it happens, it would be a simple fix and it's kind of astonishing it hasn't been touched yet in 3 years. I've edited my previous comment to be more clear, but the previous version was plain on this: I didn't read anywhere, just experienced it twice in less than a month apparently you either couldn't grasp that or chose to ignore it.Ĭongrats for your anecdotal evidence, not what I'm looking for. I presume you have wrong idea of the term "open source." Tixati to an open source client, &c., &c. Have been using it over a year, have changed the platform in meanwhile, have never had corruption of config even once.
If you have crashes, open an appropriate issue.Īfter using QB for less than a month it's already happened twice I wonder where did you read that qBittorrent does. Other clients either have this by default or never crashed or corrupted config files with me.Īhaha. I was happy to finally make the switch from Tixati to an open source client, but now I'm considering going back and this one simple, major thing hasn't been fixed ever since 2017.
After using QB for less than a month it's already happened twice. Other clients either have this by default or never crashed or corrupted config files with me. I want a simple and effective solution since the files are so prone to corruption it's a major PITA to fiddle with the settings and manually add and recheck torrents, specially on hard drive storage. That's the point having to do this sucks. Linux users have been using similar techniques to sync their shell, media player, software config for a long time.
I suggest collect $PROFILE nf nf nf bashrc vimrc zshrc mpv.conf. Then, you can save all those actual files inside a folder and use git to sync them with other devices and GitHub, etc. You can always replace the config path that qB will use by a symlink pointing to another file which will save the actual content.
0 kommentar(er)
