I didn't see any provisions in the code to change this behavior, and I could easily reproduce the issue by interrupting downloads half-way. And it truly sucks.
It looks like a possible regression while fixing a related issue, but I only had a very cursory look. Not passing blame, yet. :)
No issue or PR exists concerning this problem, yet. If you cannot be bothered to create one, I might do so myself this weekend.