April 2022 Archives by subject

• Messages sorted by: [ thread ] [ author ] [ date ]
• More info on this list...

Starting: Sat Apr 2 13:52:35 UTC 2022
Ending: Fri Apr 29 15:08:08 UTC 2022
Messages: 27

• [tahoe-lafs-trac-stream] [Tahoe-LAFS] #3526: Stop using the mock library for testing: src/allmydata/test/cli/test_invite.py   Tahoe-LAFS
• [tahoe-lafs-trac-stream] [Tahoe-LAFS] #3526: Stop using the mock library for testing: src/allmydata/test/cli/test_invite.py   Tahoe-LAFS
• [tahoe-lafs-trac-stream] [Tahoe-LAFS] #3802: Schema enforcement for HTTP protocol contents   Tahoe-LAFS
• [tahoe-lafs-trac-stream] [Tahoe-LAFS] #3872: Limit memory and CPU usage of writes/reads via HTTP storage server   Tahoe-LAFS
• [tahoe-lafs-trac-stream] [Tahoe-LAFS] #3875: Server/client code for HTTP storage protocol fURLs   Tahoe-LAFS
• [tahoe-lafs-trac-stream] [Tahoe-LAFS] #3884: HTTPS storage client logic when server's private key doesn't match public key, and when cert is signed by well-known CA (was: Test what happens in HTTPS storage client logic when server's private key doesn't match public key)   Tahoe-LAFS
• [tahoe-lafs-trac-stream] [Tahoe-LAFS] #3884: Improved testing for HTTPS storage client logic: when server's private key doesn't match public key, and when cert is signed by well-known CA (was: HTTPS storage client logic when server's private key doesn't match public key, and when cert is signed by well-known CA)   Tahoe-LAFS
• [tahoe-lafs-trac-stream] [Tahoe-LAFS] #3886: It is inconvenient to test code using `async def` using Tahoe's unittest-based testing tools   Tahoe-LAFS
• [tahoe-lafs-trac-stream] [Tahoe-LAFS] #3886: It is inconvenient to test code using `async def` using Tahoe's unittest-based testing tools   Tahoe-LAFS
• [tahoe-lafs-trac-stream] [Tahoe-LAFS] #3887: HTTPConnectionPool briefly leaks reactor state in a way that makes resource cleanup more complicated   Tahoe-LAFS
• [tahoe-lafs-trac-stream] [Tahoe-LAFS] #3888: Handling Tor and i2p in NURLs   Tahoe-LAFS
• [tahoe-lafs-trac-stream] [Tahoe-LAFS] #3888: Handling Tor and i2p in NURLs   Tahoe-LAFS
• [tahoe-lafs-trac-stream] [Tahoe-LAFS] #3888: Handling Tor and i2p in NURLs   Tahoe-LAFS
• [tahoe-lafs-trac-stream] [Tahoe-LAFS] #3888: Handling Tor and i2p in NURLs   Tahoe-LAFS
• [tahoe-lafs-trac-stream] [Tahoe-LAFS] #3888: Handling Tor and i2p in NURLs   Tahoe-LAFS
• [tahoe-lafs-trac-stream] [Tahoe-LAFS] #3888: Handling Tor and i2p in NURLs   Tahoe-LAFS
• [tahoe-lafs-trac-stream] [Tahoe-LAFS] #3888: Handling Tor and i2p in NURLs   Tahoe-LAFS
• [tahoe-lafs-trac-stream] [Tahoe-LAFS] #3888: Handling Tor and i2p in NURLs   Tahoe-LAFS
• [tahoe-lafs-trac-stream] [Tahoe-LAFS] #3889: update nix packaging to latest nixos 21.11 / pypi db   Tahoe-LAFS
• [tahoe-lafs-trac-stream] [Tahoe-LAFS] #3889: update nix packaging to latest nixos 21.11 / pypi db   Tahoe-LAFS
• [tahoe-lafs-trac-stream] [Tahoe-LAFS] #3889: update nix packaging to latest nixos 21.11 / pypi db   Tahoe-LAFS
• [tahoe-lafs-trac-stream] [Tahoe-LAFS] #3889: update nix packaging to latest nixos 21.11 / pypi db   Tahoe-LAFS
• [tahoe-lafs-trac-stream] [Tahoe-LAFS] #3890: Implement just enough read+write mutable APIs for HTTP storage client   Tahoe-LAFS
• [tahoe-lafs-trac-stream] [Tahoe-LAFS] #3890: Implement just enough read+write mutable APIs for HTTP storage client (was: Implement mutable APIs for HTTP storage client)   Tahoe-LAFS
• [tahoe-lafs-trac-stream] [Tahoe-LAFS] #3890: Implement mutable APIs for HTTP storage client   Tahoe-LAFS
• [tahoe-lafs-trac-stream] [Tahoe-LAFS] #3890: Implement mutable APIs for HTTP storage client   Tahoe-LAFS
• [tahoe-lafs-trac-stream] [Tahoe-LAFS] #3891: Mutable HTTP protocol, part 2   Tahoe-LAFS

Last message date: Fri Apr 29 15:08:08 UTC 2022
Archived on: Fri Aug 29 08:06:55 UTC 2025

• Messages sorted by: [ thread ] [ author ] [ date ]
• More info on this list...