https://git.schokokeks.org/derivepassphrase.git/tree/eec18c81f32f558435e222848d8cd1688b4ae26eRecent commits to derivepassphrase.git (eec18c81f32f558435e222848d8cd1688b4ae26e)2025-11-30T09:35:38+01:00tag:gitlist.org,2012:commit/eec18c81f32f558435e222848d8cd1688b4ae26eFormat and lint all files2025-11-30T09:35:38+01:00Marco Riccisoftware@the13thletter.info
<pre></pre>
tag:gitlist.org,2012:commit/b315e5bfd56052306d724f7dfa2f9c3b09300595Fix type errors due to click 8.2.02025-11-29T22:35:16+01:00Marco Riccisoftware@the13thletter.info
<pre>`click` 8.2.0 broke compatibility in an unexpectingly violent way,
removing previously public symbols without any transition period. Thus,
the code may or may not type check, depending on which version of
`click` is installed. We thus disable type checking or otherwise type
check on a more coarse level whereever we used one of the now-removed
symbols.
</pre>
tag:gitlist.org,2012:commit/bdf95bab1e404e34f6a68c5b2bf72d510cd23556Fix typing of the dummy vault configuration settings in the constructor2025-11-27T21:59:27+01:00Marco Riccisoftware@the13thletter.info
<pre>One of our tests, a "manual sanity-check" kind of test, tries to use the
`tests.data.DUMMY_CONFIG_SETTINGS` symbol as keyword arguments in the
`vault.Vault` constructor. This appeared to work with older `mypy`
versions, but now raises an error about extra keys in the symbol that
the constructor does not accept as keyword arguments. (Because the
dummy config settings are actually typed as vault config "services"
settings, which *do* allow more settings than the constructor uses as
arguments.)
So, we now arrange for a second symbol with effectively the same
contents as the dummy config settings, but explicitly typed as
constructor arguments, to be used in the "manual sanity-check" test
instead.
(Implementation-wise, we introduce a new base type
`_types.VaultConstructorArgs`, and let
`_types.VaultConfigServicesSettings` inherit from that. This is easier
than attempting to constrain the latter type after the fact. We
introduce the new base type directly in the `_types` module, even though
it is otherwise only used in the tests, because the derived type (from
the `_types` module) also needs access during construction.)
</pre>
tag:gitlist.org,2012:commit/790092cf0125f73dd864aaefbac58a78cd65007cAdd CPython 3.14 to the list of test environments2025-11-26T21:02:16+01:00Marco Riccisoftware@the13thletter.info
<pre>By now, CPython 3.14 has been released, as has a more recent version of
`hatch` that knows where to obtain CPython 3.14. It is thus viable to
officially test with CPython 3.14 with only standard `hatch` installs.
</pre>
tag:gitlist.org,2012:commit/4fa4b813455a4a9b1ac7885b4b417046eac4971cFix more broken tests on The Annoying OS2025-11-26T20:50:58+01:00Marco Riccisoftware@the13thletter.info
<pre>The broken tests relate to SSH agent handling. We now have a fake SSH
agent, and I mistakenly believed that because this agent is always
available, tests no longer needed to ensure agent accessibility; the
fake agent would always be available. But that's not how the SSH agent
test fixture works: you still need to explicitly *request* the agent as
part of your setup. Otherwise you will run into the usual "no agent
could be located" or "no agent is supported on this system" error
situations (which is exactly what was happening on The Annoying OS).
The only thing that really changed is that we now know that *some* of
the test fixture instances (the ones with fake agents) will not
auto-skip due to lack of support.
</pre>
tag:gitlist.org,2012:commit/7ee21c33badaf33be2a8be188b7d1c8ec9123e07Fix broken links in the documentation caused by renaming or splitting modules2025-11-26T20:49:34+01:00Marco Riccisoftware@the13thletter.info
<pre></pre>
tag:gitlist.org,2012:commit/34d0f5f5b758821133cfe59446fa344978d6f763Split the basic command-line tests, again2025-11-26T20:46:42+01:00Marco Riccisoftware@the13thletter.info
<pre>(This is part 11 of a series of refactorings for the test suite.)
Split the basic command-line tests into four thematic groups, in four
separate test files:
* tests for common subsystems of the `derivepassphrase` CLI, plus
miscellaneous basic tests
* basic tests for the `derivepassphrase vault` CLI
* tests for the configuration management options of the
`derivepassphrase vault` CLI
* tests for the note handling machinery of the `derivepassphrase
vault` CLI
Also update the documentation to reflect the module split.
</pre>
tag:gitlist.org,2012:commit/d0604f6598ac3650f0cc3a74e22e35f9cf3e02a5Fix missing documentation in the test suite2025-08-31T21:24:09+02:00Marco Riccisoftware@the13thletter.info
<pre>Update the documentation (files, navigation) to reflect the test files
split and the introduction of the `tests.data` and `tests.machinery`
packages. Additionally, turn the package descriptions in the `tests`
module docstring into proper hyperlinks.
</pre>
tag:gitlist.org,2012:commit/1500a6493e49a09f3d3db9a5a7edc8890420c647Fix some documentation issues with the heavy-duty command-line inteface tests2025-08-31T21:18:26+02:00Marco Riccisoftware@the13thletter.info
<pre>Fix both docstrings and inline commentary.
</pre>
tag:gitlist.org,2012:commit/b78a8508b929e71c1efcd18958a201ec13724dffRefactor the heavy-duty command-line interface tests2025-08-31T21:09:13+02:00Marco Riccisoftware@the13thletter.info
<pre>(This is part 10 of a series of refactorings for the test suite.)
In the heavy-duty command-line tests, factor out common test setups and
common hypothesis strategies. In particular, share the hypothesis
strategies and the skeletal procedure for both affected state machines
because they offer more or less the same transition rules.
For the hypothesis test machinery, fix some types and some import
aliases that affect the heavy-duty command-line tests.
</pre>