Erik Moeller

Thanks - I was mostly trying to understand the risk of production-level data integrity issues or user-facing impact. > In theory, however, I don't see how it's meaningfully more rare...

I think the preferred behavior would be for the API to also filter with `.last_updated.isnot(None)`. These are not valid sources and should never be returned. The interface in the screenshot...

Per testing at least with the dev env this appears to be limited to downloading collections (even if said collection only contains one file), not individual files from the source...

Still pending reproduction. At minimum during this sprint we may see another RC (and then the final at the end of the sprint period) and can do some additional testing...

The changes to the connection wizard have been deferred to Tails 4.20, due on 2021-07-13. Re-milestoning this issue to the next release.

The Tor Connection Assistant is part of Tails 4.20 (I've re-titled the issue accordingly). I've not been able to reproduce the original issue, but given how timing-dependent it is, it's...

Here's what I've learned after another 90 minutes or so of investigation: - I've still not been able to reproduce the original issue, but I am consistently able to reproduce...

I'm still seeing the flash error on Tails 4.21, but only on initial connect, not on reconnect. I'm also sometimes seeing a more serious error which is likely related: the...

> Run the Tor config script at startup As far as I can tell, this would require running a script as root on startup, for which Tails does not appear...

I've tested the behavior in Tails 4.22 and still observe the following issues: - intermittent errors when Tails checks for updates, due to the enforced Tor restart interfering with said...