Custom Query (2551 matches)

• test_sign_bad_perms
• test_unreadable_config
• test_private_config_unreadable
• test_private_config_unreadable_preexisting
• test_write_config_unwritable_file

These all assume that the test process won't be able to read or write a path where the associated filesystem permission bit is not set. This is only true as long as the process isn't a superuser. If it is, it can do what it wants and the tests fail as a result.

It's not a great idea to run Tahoe-LAFS as a superuser but nothing we do actively _prevents_ you from doing so. Also, right now, it would be convenient to run some of the test jobs on CI as root inside a Docker container (otherwise we need to do an unknown amount of Docker image hacking to make running as another user possible).

So, skip these tests if the test process is root.

Server 1 starts with Foolscap. Client hears about from introducer. Server 2 restarts with HTTP. Client now switches to using HTTP.

In storage_client.py there is logic to decide if an announcement is worth paying attention to, by comparing it to the old known announcement. NURLs might end up in a different order, but that is not a semantic difference. So this suggests NURLs should be sent as a set.