bug: repo migration IPFS fallback handling

[SgtPooki]

debugging whether fallback to IPFS works with kubo, to confirm users blocked by ipfs.io are able to download repo migrations from IPFS network.

documented quick check at https://github.com/ipfs/fs-repo-migrations/issues/184, but I wonder why user in https://github.com/ipfs/ipfs-desktop/issues/2572 was not able to successfully download from IPFS? Logs get cut off so i'm not sure if that succeeded or not.

open questions

• Did user in https://github.com/ipfs/ipfs-desktop/issues/2572 download migration successfully via IPFS, but we didn't see it because github issue didn't include full output?
• did ipfs-desktop see the error for the failure to download from IPFS and exit early?

[SgtPooki]

I just downloaded an old version of IPFS-desktop https://github.com/ipfs/ipfs-desktop/releases/tag/v0.26.1, blocked access to ipfs.io, ran ipfs-desktop v0.26.1, and then selected "check for updates" and it did not update successfully

[SgtPooki]

seems like this is not a bug, but a UX problem.

• ipfs-desktop does show the migration output when attempting to run a migration, and i can see HTTP fail, but IPFS backup does succeed.
• ipfs config had Migration.DownloadSources set to [], but I updated it to ["HTTP", "IPFS"]. This being empty could be why some users aren't getting the fallback to IPFS?

[SgtPooki]

seems like this works properly even when Migration.DownloadSources is set to []. closing