https://git.schokokeks.org/derivepassphrase.git/tree/b76c2afc68fd4e0a5164fa9ff258470be947d5e2 Recent commits feed provided by GitList. Use a common parameter set and a common monkeypatching setup. At the moment, this is done by copy-pasting the parametrization and setup code, but this could feasibly be abstracted into a common testing function and common parameter set within the `tests.data` and `tests.data.callables` modules. https://git.schokokeks.org/derivepassphrase.git/commit/b76c2afc68fd4e0a5164fa9ff258470be947d5e2 software@the13thletter.info (Marco Ricci) Sat, 20 Jun 2026 13:58:03 +0200 b76c2afc68fd4e0a5164fa9ff258470be947d5e2 https://git.schokokeks.org/derivepassphrase.git/commit/bad75d455d6e170c20b0405ead16fa732de727e3 software@the13thletter.info (Marco Ricci) Sat, 20 Jun 2026 11:36:36 +0200 bad75d455d6e170c20b0405ead16fa732de727e3 For compatibility with `contextlib.contextmanager`, and because it is the more specific type, we annotate generators as `Generator[T, None, None]`, not as `Iterator[T]`. In January 2026, typeshed started shipping type annotations for the Python standard library that deprecate the use of `contextlib.contextmanager` with general functions returning `Iterator[T]`. `contextlib.contextmanager` actually requires a `Generator[T, None, None]` to work, but the `contextlib` and the `typing` documentation has been erroneously suggesting the `Iterator[T]` type as a "shorthand" notation for years. For `contextlib.contextmanager`, the difference matters. So, re-annotate everything explicitly with generators (when producing) or iterables (when consuming), whichever is appropriate. https://git.schokokeks.org/derivepassphrase.git/commit/f797d5074181fc4d5a35f04367784543249315e4 software@the13thletter.info (Marco Ricci) Fri, 19 Jun 2026 22:40:11 +0200 f797d5074181fc4d5a35f04367784543249315e4 Use pytest parametrization and hypothesis randomization systematically: tests that have exhaustive configurations or error conditions use pytest parametrization, tests with whole classes of configurations or error conditions use hypothesis randomization. Consolidate tests that test the same thing, but under different circumstances, into pytest parametrized tests. Also, use class inheritance to share helper functions for setting up the stub agent environment across all relevant test groups. Consolidating tests usually involves variants of a test for different variants of the stubbed agent. Converting pytest parametrization to a hypothesis strategy usually means settling for a `strategies.sampled_from(existing_parameter_set)` implementation and leaving any smarter generation logic to future edits. https://git.schokokeks.org/derivepassphrase.git/commit/3a69028fe108068a7c7ba6e0cdeeefc18df56e7d software@the13thletter.info (Marco Ricci) Fri, 19 Jun 2026 21:31:13 +0200 3a69028fe108068a7c7ba6e0cdeeefc18df56e7d Let the stubbed SSH agent tolerate incomplete request messages, or multiple request messages at once, within the same `sendall` call. Furthermore, change the error type to OSError (EBADF) for I/O on closed socket connections (mirroring the behavior of UNIX domain sockets) and when closing the connection, assert that no incomplete requests have been issued to the agent. With this change, the stubbed SSH agent socket now usefully models the communication channel between agent and client, and can be sensibly used to simulate communication and protocol errors (or their absence). This differentiates it—in terms of scope and use cases—from the agent protocol response queue, which monkeypatches the client instead of faking a server, and which operates on full request/response messages. Add some commentary to the stubbed SSH agent socket docstring to this effect. https://git.schokokeks.org/derivepassphrase.git/commit/27f35e7c4101164e42e08051b0698a55735f8322 software@the13thletter.info (Marco Ricci) Thu, 18 Jun 2026 06:15:10 +0200 27f35e7c4101164e42e08051b0698a55735f8322 When calling `bytes` on the SSH agent protocol number enums, return their corresponding serialization as request codes or response codes. (A follow-up to 57e3b1ed832e865e9f9e8316f930b1beae3714f0.) https://git.schokokeks.org/derivepassphrase.git/commit/729c89799dc49635698c8f73a59ba79eb3c584a0 software@the13thletter.info (Marco Ricci) Tue, 16 Jun 2026 22:19:26 +0200 729c89799dc49635698c8f73a59ba79eb3c584a0 In attribute declarations, `griffe`/`mkdocstring-python` elides the object on which the outermost method is called (but correctly autolinks the method itself). This looks good if the initializer is something like `base64.b64_decode(data)` (which gets shortened to `b64_decode(data)`), and terrible if the initializer is something like `base64.b64_decode(data).decode()` (which gets shortened to `decode()`). So, to get nicer API docs, rewrite some obvious cases where the object would otherwise be elided in the "class-bound method + self argument" style instead. https://git.schokokeks.org/derivepassphrase.git/commit/3790413fb35878eb8500e29e7c6923104869d854 software@the13thletter.info (Marco Ricci) Tue, 16 Jun 2026 19:55:01 +0200 3790413fb35878eb8500e29e7c6923104869d854 https://git.schokokeks.org/derivepassphrase.git/commit/c2efe74d47243d97f87240eee0045cbb58abff53 software@the13thletter.info (Marco Ricci) Tue, 16 Jun 2026 19:47:25 +0200 c2efe74d47243d97f87240eee0045cbb58abff53 Again, instead of magic strings floating around in the test suite, use the already existing enum instead. https://git.schokokeks.org/derivepassphrase.git/commit/090f87b133247b5f688f5101f0229829616b22dd software@the13thletter.info (Marco Ricci) Mon, 15 Jun 2026 22:27:21 +0200 090f87b133247b5f688f5101f0229829616b22dd Instead of having all these magic strings floating around all over the test suite, use a dedicated enum for consistency, discoverability, and typo-resistance. https://git.schokokeks.org/derivepassphrase.git/commit/7bccff34588cfb6ac90bc0d277a40cab5b9a5cf2 software@the13thletter.info (Marco Ricci) Mon, 15 Jun 2026 21:36:53 +0200 7bccff34588cfb6ac90bc0d277a40cab5b9a5cf2