Arq 5.2.3 [En]

Fixed Issues:
- Added a workaround for Amazon Cloud Drive problems which result in random HTTP 400 and 408 errors.
- On backup start, wait up to 30 seconds for an allowed network before failing with an error. This allows for a computer that just woke up to establish network connectivity.
- If Arq is unable to write a README.TXT file in the user's Google Drive account because the quota has been exceeded, ignore the error so that the user can add the Google Drive destination in Arq and then be able to use Arq to delete the "hidden" data (if the user chose to use the hidden "appdata" folder when configuring Arq).
- Fixed an issue where Arq would not show another computer's backup set added later because it used cached data instead of requerying for the current list of backup sets.
- Fixed a database issue which could cause Arq to spend a very long time on a database query for very large (multi-terabyte) backup datasets.
- Fixed an issue which could cause log files to prematurely rotate. Arq, Arq Agent and helper programs will now write 100 MB log files, keeping up to 10 files.
- Removed "wl.basic" from the list of OneDrive permissions requested by Arq, because Arq doesn't need it.

Fixed issues:
- Added logging for error conditions during backup.
- Changed next backup time calculation for daily backups so that it's at the chosen hour even if a backup has already happened today.
- Fixed an issue where daily backup may not begin on computer wake if computer was asleep at the scheduled backup time.
- If user has chosen specific network interfaces and current network interface can't be determined, do not back up.
- When deleting a Dropbox folder, recursively delete the contents first to work around a Dropbox issue.
- If backing up to a local folder, skip checking whether we're on an allowed network.
- When browsing other backup sets, fixed an issue where too much cached information was being cleared, causing browsing to be very slow every time.