[drbits]

Jiaz said to work hard testing this version.

I do not expect all of these to be fixed in the next Stable release. Some should wait. I will continue adding to the end of this message until the next version appears. I do not know which are important enough to report in BugTracker (several are already in BugTracker). If a decision is made to not implement or to delay or a BugTracker ticket is created, please add that to this thread. I will strike-out the item here.

1) When a file is deleted, different hosts display different messages. The messages should be consistent.
Recommended message: Deleted or Deleted: substatus.
If a file is found, the status of "Found" is recommended.
If the status is really unknown, then it should be displayed as "Unknown" or "Unknown: substatus". Any details from the host should be shown in the properties, not the grid.
Rapidshare, Hotfile: [Not Available] (what are the brackets for?)
Depositfiles: Not found
This does not require changing the plugins. There is a discussion thread that settled on these as the recommended replacements for "Online", "Offline", and the other inconsistent or confusing status names.
This is to assist the LinkGrabber part of status consolidation and to help prepare for the Event Manager.

2) Rapidshare sometimes shows "Unknown file size" for files that are "[Not Available]", and sometimes shows a length. If a file is not available or not found, the length should be either the file's actual length or 0. It should be consistent across all hosts. The database still contained the length when the status was changed to "[Not available]" This does not require changing the plugins.

3) In a package with 3 mirrors for each of 8 parts, when all parts are deleted, right clicking on the package shows "Resume (8)" instead of "Resume (24)" Apparently "[Not Available]" locks the link (and displays the do not enter red icon), but is not an error. It looks like "Not found" is what is being counted. All of the other counts are 24.

URLs in this package (1), (2), (3), (5):
**External links are only visible to Support Staff****External links are only visible to Support Staff**
**External links are only visible to Support Staff****External links are only visible to Support Staff**
**External links are only visible to Support Staff****External links are only visible to Support Staff**
**External links are only visible to Support Staff****External links are only visible to Support Staff**
**External links are only visible to Support Staff****External links are only visible to Support Staff**
**External links are only visible to Support Staff****External links are only visible to Support Staff**
**External links are only visible to Support Staff****External links are only visible to Support Staff**
**External links are only visible to Support Staff****External links are only visible to Support Staff**
**External links are only visible to Support Staff****External links are only visible to Support Staff**
**External links are only visible to Support Staff****External links are only visible to Support Staff**
**External links are only visible to Support Staff****External links are only visible to Support Staff**
**External links are only visible to Support Staff****External links are only visible to Support Staff**
**External links are only visible to Support Staff****External links are only visible to Support Staff**
**External links are only visible to Support Staff****External links are only visible to Support Staff**
**External links are only visible to Support Staff****External links are only visible to Support Staff**
**External links are only visible to Support Staff****External links are only visible to Support Staff**
**External links are only visible to Support Staff****External links are only visible to Support Staff**
**External links are only visible to Support Staff****External links are only visible to Support Staff**
**External links are only visible to Support Staff****External links are only visible to Support Staff**
**External links are only visible to Support Staff****External links are only visible to Support Staff**
**External links are only visible to Support Staff****External links are only visible to Support Staff**
**External links are only visible to Support Staff****External links are only visible to Support Staff**
**External links are only visible to Support Staff****External links are only visible to Support Staff**
**External links are only visible to Support Staff****External links are only visible to Support Staff**

4) [Not available] does not mark the package with the orange error dot.
Sample URL:
**External links are only visible to Support Staff****External links are only visible to Support Staff**

5) Reset or Resume on Deleted links does not always change the display of the link until the mouse is moved over the line containing the link.

6) The first link shown above, when "Reset" and "Force Download", displays a status of "TOS violation. File removed by rapidshare" and the No Entry red icon. It also causes the orange dot on the package, while it did not when the file was [Not Available].
The status should be "Deleted" with a substatus of "censored" (Displayed as Deleted: censored) and the explanation (as currently displayed) should be in the properties.

7) Filefactory and Mediafire sometimes download and sometimes display "Plugin error (Out of date)".
7a) This status message is overused. It is often incorrect. The correct status would be "User needed: unexpected response"
7b) The Mediafire was an attempt to start 4 links at the same time (an entire new package). Three of the 4 started, one gave the spurious message.

8) Links are being marked with a relatively new status: "File loaded from other source". It is not clear where this is coming from or when it is generated. If it is generated when the file actually exists, the "File exists" status (a permanent error) should be displayed. If it is generated when it is discovered that a mirror is downloading the file, this is a bug.
8a) In any case, disabling the link is a bug. This should be reserved for users disabling links.
8b) If links are going to be automatically disabled, the text should be clear, only the background grayed.

Sample links for (7) and (8)
**External links are only visible to Support Staff****External links are only visible to Support Staff**
**External links are only visible to Support Staff****External links are only visible to Support Staff**
**External links are only visible to Support Staff****External links are only visible to Support Staff**
**External links are only visible to Support Staff****External links are only visible to Support Staff**
**External links are only visible to Support Staff****External links are only visible to Support Staff**
**External links are only visible to Support Staff****External links are only visible to Support Staff**
**External links are only visible to Support Staff****External links are only visible to Support Staff**
**External links are only visible to Support Staff****External links are only visible to Support Staff**
**External links are only visible to Support Staff****External links are only visible to Support Staff**
**External links are only visible to Support Staff****External links are only visible to Support Staff**
**External links are only visible to Support Staff****External links are only visible to Support Staff**
**External links are only visible to Support Staff****External links are only visible to Support Staff**
**External links are only visible to Support Staff****External links are only visible to Support Staff**
**External links are only visible to Support Staff****External links are only visible to Support Staff**

9) The properties pane still covers the info pane on both Download and Linkgrabber.
9a) The Linkgrabber setting "Show info panel" does not seem to do anything.
9b) The Download info pane is still missing the number of active downloads. This should be the number that have begun downloading file data, not including the number that are trying to connect.

10) Is the KB Loaded and the speedometer based on the TCP packet payload transferred or the data processed? It still looks rough when the system has other programs running (even if they are not using the network). This should be explained.

11) The most important status text is still not kept between sessions. It apparently can also be lost when packages are merged. Keeping status is especially important when the link has been automatically disabled.
11a) Some messages are kept between sessions that should not be (temporary messages like connecting).
11b) For the future, I suggest three status fields per link (status, substatus, and host message). If necessary, temporary messages should be kept in the DB, but separate from the Status fields (it can be the "DL_current_display" field, and identified as temporary in the DB).

12) Passwords are still not always kept when packages are merged. I don't know if the "Move the password to the link" solution is broken or we need to move to a "always add the manual password to the auto-password list" approach.

13) Not a bug, just so we have it on record. JD slows down noticeably at around 19 000 links. Packages with over a few hundred links are hard to work with, but packages do not slow down with size, at least up to 7000 links.

14) We still have to click on a package for Find, Move to top, and Move to bottom.

15) When turning off automatic reconnection, a disturbing warning is displayed (too strong). It is missing the "Do not show this again" check box.

16) The confirmation for Reset should show the number of files (as I am told that it did in early versions). It is missing the "Do not show this again" check box.

17) A lot of the on-line documentation is from before the adoption of tabs.

18) Sometimes the Captcha pop-up captures the keyboard input while it is not the selected window. This just happened with uploadbox, but I think it is a general problem. If I am typing a word when it pops up, it captures part of the word. If the keyboard is quiet at the time, it seems to wait.

19) TCP stability appears to be improved. I seem to be able to run 18 downloading links concurrently on a 160 KB/s connection (a total of 34 connections, because the 4 mediafire downloads are using 5 chunks each). I am running while using FF and doing file copies and unrars I have restricted JD to -Xmx384m (about 440MB private bytes).
19a) I can confirm that Max. Con., Max. Dls., and Maximum simultaneous downloads per host are all working correctly.

20) Dragging packages leaves the wrong package highlighted. It should be the package that was dragged, not the package before or after. I believe this is a problem with Links as well.

21) Right clicking should not change the highlighted link or package, unless there is none highlighted. When a package is open, right clicking on the package header changes the highlight to that line. This makes working with a subset of links more difficult. Eventually, it might be best to have a selection of links, independent of the packages (e.g., select links in multiple packages, right click, move to new package).

22) Files are supposed to be checked to make sure JD does not download extra HTTP, HTML, or XML at the beginning of the file. Due to a bug in 9.579, I have 4 links to HTML files instead of the RAR files they claim to be. Since the extension does not match the file signature, this should have been reported by JD as a bad link. Instead, it was reported by unrar as "Extract failed: ASpb.rar is not RAR archive" (sic.).
22a) Part of the problem is the HTML kludge. JD sometimes removes the .HTML or .HTM without checking that there is no HTML file there. This could also be related to the recent fix to avoid messing with the extension of XML variants (such as .docx, .stl). I know that sometimes we have to remove the .HTML to avoid a loop or a 40x, but those can be dealt with better.
22b) We have a list of file header signatures and the proper MIME-type (content-type) and extension for that signature. If JD finds a mismatch, it should act then. Initially, it would be enough to check for about 20 binary types (zip, rar, 7z, tar, gz, bz2, common Linus installers, riff (AVI), mp3, mkv, mp4, gif, jpeg, png, and so on), HTML, XHTML, and XML signatures (<H, <!, or <?). If it receives a page that does not match the content-type, then it is an "Unexpected data error" (which we now report as plugin out of date, but should be retryable). This may have to wait until the host plugins are restructured into subclasses or callbacks of JDhost_plugins (or whatever the class name will be).

23) Not being able to sort on status makes large packages much harder to deal with.
23a) For example (probably not in this release):
finished (downloaded and extracted or hash checked): 100, (Green Check mark icon)
downloaded: 90, (Blue check mark)
downloading: 80, (Green down arrow)
negotiating download: 75, (displayed as downloading)
HTTP connecting: 70, (displayed as downloading)
waiting in the queue: 60, (nothing to display)
Unknown: not checked (and similar benign status, such as duplicate link): 50 (blue link)
in a wait that affects all links for a host: 45 (blue clock icon?)
retryable (if it has not retried yet): 40 (blue link), retries exhausted (example of resumable)
waiting for user (resumable): 30 (blue clock?)
user disabled link: 25 (shown by blue lock icon?)
Host busy (including no slots): 20 (orange clock icon)
Unexpected data: 15 (orange link?)
downloaded, but post-processing error: 10 (orange down arrow)
"bad link", Deleted (and other permanent errors): 5 (broken orange link)

Unexpected data is an extended form of what currently generates Plugin error (out of date). It includes
* data that should be on the page, but cannot be found,
* content-type (MIME type) does not match data,
* extra html page that JD does not know how to handle, usw.
Eventually, extra html pages should be handled with the same regex as other pages. Buttons marked Skip or Proceed should just be followed. Defaults should be used for missing data. When things are moved around on the page or moved from page to page, JD should be flexible enough to handle it.

Background color of filename field and status field should vary with status. The specific colors should be defined in the style or a style_name.inc or rc file. (default could be red=255-2.5*value, green = 2.5*value, blue=192 this is magenta through cyan).

24) Sometimes, a link will stop downloading, but the green light with a check mark will not appear, because the file hasn't finished downloading. There is no status message or symbol to explain the situation. The Progress column shows the same two numbers (as do Loaded and FileSize, but the numbers are not the correct file size). The Part file is there instead of the regular file name. It appears to happen most when there is no Hash and the file is a media file. I seem to remember that the downloaded column tooltip for a link used to be the number of bytes downloaded. The tooltip for the filesize column should also be in bytes. In this case, the file was in x7.to, and so I will have to reset and redownload it.
Today's Sample Link: **External links are only visible to Support Staff** Original Link from KatzForums: **External links are only visible to Support Staff**



Log attached