V2.1.0.3_beta Issue: b2_list_file_versions spike. Downgrade to v2.1.0.2_beta?

That seems to support the original idea that something changed in 2.1.0.3.
Given all the download trouble, I wonder how well compact or restore run?

EDIT 2:

GitHub issue linked from original post here found this, matching tests here:

UPDATE: confirmed that the error does not happen in v2.1.0.2_beta.

I have to say I had trouble figuring out where to find 2.1.0.3 GitHub source.
Generally I go for the tag, but should I be looking at a branch for releases?

Fixed not creating releases on master when building from a branch #5936
was me wondering why the source release didn’t seem to match the binary.

EDIT 3:

This is new in 2.1.0.3. I wonder if 30 seconds needs more for big backups?

C:\Duplicati\duplicati-2.1.0.3_beta_2025-01-22-win-x64-gui>Duplicati.CommandLine help read-write-timeout
  --read-write-timeout (Timespan): Set the read/write timeout for the connection
    The read/write timeout is the maximum amount of time to wait for any activity during a transfer. If no activity is detected for this period, the connection is considered broken and the transfer is
    aborted. Set to 0s to disabled
    * default value: 30s

The GitHub issue also said that the problem was associated with big backup.

Just backup a large dataset to Backblaze B2