Update of bug #54828 (project wget): Status: None => Invalid Open/Closed: Open => Closed
_______________________________________________________ Follow-up Comment #1: This is actually two different issues. Anyways, firstly, the speed being stuck is a technical limitation of Wget being a single threaded application. Wget uses only blocking network sockets and while it is blocked on a read() call, there is nothing it can do to update the UI. Similarly, mentioning that it is stalled is also not possible without adding threading support. Something that we do not intend to do. These issues don't exist in Wget2 which has been designed with multi-threading from the very beginning. Regarding the "(Success)" string, that is not controlled by Wget at all. It is in fact the string reported by the kernel for the last error. In your case, it seems to be that the last socket operation was a success, but the connection was still terminated. _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?54828> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/