Search results disappearing by themselves
Posted: 20 Apr 2014 23:21I'm now encountering a new bug, perhaps introduced in 2.7.4.0.
I had a large batch of search results on a busy push G2 source, which as usual requires periodic manual re-adding of sources to get them to eventually download one by one (or if you're lucky, three at a time), because for some reason when a push source returns a busy signal Shareaza forgets it instead of doing what it does with a non-push source in otherwise identical circumstances, which is to wait two minutes and try again.
I went to add sources back again for the remaining items, and lo and behold they had disappeared from the search tab.
I did not close the search and start a new one. I did not make any changes to the filtering options for that, or any, search tab. I did not type into the quick filter box at the bottom. I did not change any settings. In fact at the time of the event I was using a different application and Shareaza was backgrounded.
Search results should, obviously, not spontaneously disappear without an immediately preceding user interaction that makes them do so.
I can't even find them by turning off *all* filters in that search tab and *all* security rules. Where the hell did they go?
This constitutes a bug causing data loss, as I can't see any quick way to recover the results and continue downloading these files, even though I certainly should be able to do so. I could rerun the search, and take my chances with whether it finds the same files again quickly enough that the source is still online. But why should I have to, and why should I have only a chance at success? I did not choose to delete those search results from the tab. Someone else apparently made such a decision on my behalf. And that was wrong.
I don't want this to happen again. I want to see a version 2.7.5.0 out soon that addresses, at the very least:
1. This issue.
2. The files-overwrite-each-other-in-download-folder bug.
3. The problems with G1 and G2 connection loss and usual need to manually muck around to get G2 working again, and just wait a ridiculously long time to get G1 working again.
4. Those freezes during hashing, which AFAICT serve no useful purpose whatsoever.
5. The incompatibilities with GTK-Gnutella download sources that cause all sorts of headaches.
Particularly, bugs 2, 3, 4, and 5 have been around for years. It's high time someone dealt with them.
I had a large batch of search results on a busy push G2 source, which as usual requires periodic manual re-adding of sources to get them to eventually download one by one (or if you're lucky, three at a time), because for some reason when a push source returns a busy signal Shareaza forgets it instead of doing what it does with a non-push source in otherwise identical circumstances, which is to wait two minutes and try again.
I went to add sources back again for the remaining items, and lo and behold they had disappeared from the search tab.
I did not close the search and start a new one. I did not make any changes to the filtering options for that, or any, search tab. I did not type into the quick filter box at the bottom. I did not change any settings. In fact at the time of the event I was using a different application and Shareaza was backgrounded.
Search results should, obviously, not spontaneously disappear without an immediately preceding user interaction that makes them do so.
I can't even find them by turning off *all* filters in that search tab and *all* security rules. Where the hell did they go?
This constitutes a bug causing data loss, as I can't see any quick way to recover the results and continue downloading these files, even though I certainly should be able to do so. I could rerun the search, and take my chances with whether it finds the same files again quickly enough that the source is still online. But why should I have to, and why should I have only a chance at success? I did not choose to delete those search results from the tab. Someone else apparently made such a decision on my behalf. And that was wrong.
I don't want this to happen again. I want to see a version 2.7.5.0 out soon that addresses, at the very least:
1. This issue.
2. The files-overwrite-each-other-in-download-folder bug.
3. The problems with G1 and G2 connection loss and usual need to manually muck around to get G2 working again, and just wait a ridiculously long time to get G1 working again.
4. Those freezes during hashing, which AFAICT serve no useful purpose whatsoever.
5. The incompatibilities with GTK-Gnutella download sources that cause all sorts of headaches.
Particularly, bugs 2, 3, 4, and 5 have been around for years. It's high time someone dealt with them.
