Not sure how to deal with it going forward, since the commits are in a different repo.
But there was no additional fixes to ngclient for this round.
We are working on it. I have added your findings as issues.
I see there is a bug that prevents you from seeing the filename. The feature is a new cleanup that identifies leftover index files and removes them. According to the database they contain no needed information so they can be safely deleted.
I will fix the issue preventing the name from being displayed, so we can see what file it is.
It does not have any negative impact, but it does give a warning on each run.
I see that part needs to be fixed. The ITimeoutExemptBackend was used for the timeout system prior to this release but should not be used anymore.
The read-write-timeout is not an upload timeout, it is an inactivity timeout. Every time some data is processed, the timer is reset. So a default of 30 seconds means that not even a single byte was processed for 30 seconds, which would indicate a stalled connection IMO.
This looks like it timed out after 45 seconds. Any clue as to why it would time out? Network issues?
We can increase the timeout to 60s by default, but it should not be required.
Fixed one parsing error, but apparently created a new one.
I have registered an issue.
No, that is a good point. They should be deleted, so perhaps I should just update the code to delete them anyway. They serve no purpose anymore.