Recent commits to derivepassphrase.git (1cefab9b2c4c51366b0daa1eb06f1652ef6e53fd)

Merge topic branch 'concurrency-testing' into master

2025-05-20T20:12:39+02:00

* concurrency-testing:
  Document the new concurrency testing setup in the changelog
  Add tests for the configuration mutex
  Convert the configuration mutex to an explicit class

GitHub: Closes #23.
</pre>

Document the new concurrency testing setup in the changelog

2025-05-19T21:45:21+02:00

</pre>

Add tests for the configuration mutex

2025-05-18T23:08:44+02:00

Conceptually, we need two types of tests for the configuration mutex:
the first type asserts that the program logic works for *any* kind of
(potentially fake) configuration mutex, and the second type asserts that
the configuration mutex works for *any* set of (potentially fake)
operations.  In both cases, the fake parts usually impose a specific
order of locking or running, controllable from the outside.

We modify the `ConfigurationMutex` class to shift the management of the
lock file descriptor into the lock and unlock functions themselves,
instead of cramming them into `__enter__` and `__exit__`.  (This means
that subclasses need not deal with the lock file, or in fact, with any
of the platform-specific locking machinery.)  A custom subclass in the
`tests` namespace provides a faked mutex that imposes a specific locking
order, controllable from the outside via message passing.  This subclass
is then used with a state machine to test various sets of operations
together with the faked mutex, i.e. to provide tests of the first type.
(The standard tests, executed with the actual mutex implementation,
already provide tests of the second type.)

Regrettably, this set of tests requires concurrency support.
Specifically, because the click testing machinery needs to reset
process-wide properties for each concurrent unit, and because the tests
require this to be done in a time-overlapped manner, the tests
specifically require multiprocessing support.  Care must also be taken
to ensure that coverage management works: that it is enabled in the
subprocesses whenever it is enabled in the parent (which is
a straightforward configuration issue), and that the parent process does
not accidentally remove these coverage measurements as junk files in
case the subprocesses are spawned in specifically prepared and
automatically cleaned up temporary directories (which is a manual labor
issue).
</pre>

Convert the configuration mutex to an explicit class

2025-04-12T20:01:40+02:00

The class form is easier to monkeypatch than the generator form.
</pre>

Merge topic branch 'documentation-fixes' into master

2025-04-09T21:58:45+02:00

* documentation-fixes:
  Reintroduce explicit type annotations for vault CLI arguments
</pre>

Reintroduce explicit type annotations for vault CLI arguments

2025-04-09T21:53:48+02:00

The command-line function for the "vault" subcommand is now implemented
by accepting wildcard keyword arguments, so `mkdocstrings-python` no
longer has explicit type information for the known list of keyword
arguments to fall back on. So, explicitly (re-)annotate that list with
type information.
</pre>

Merge topic branch 'click-820-expected-incompatibilities' into master

2025-04-09T19:47:01+02:00

* click-820-expected-incompatibilities:
  Fix expected incompatibilities in the CLI machinery with click 8.2.0
</pre>

Fix expected incompatibilities in the CLI machinery with click 8.2.0

2025-04-09T19:43:39+02:00

click 8.2.0 is currently in pre-release, though a release candidate has
already been tagged as such. This candidate deprecated some internals,
which we access. Thus fix what we can reasonably assume will otherwise
be broken by click 8.2.0.
</pre>

Merge topic branch 'cleanup-lockfiles-in-test-harness' into master

2025-04-09T19:29:34+02:00

* cleanup-lockfiles-in-test-harness:
  Clean up configuration write lock files in the test suite
</pre>

Clean up configuration write lock files in the test suite

2025-04-09T19:27:50+02:00

When using a temporary, isolated `derivepassphrase` configuration
directory in the test suite, also clean up the matching configuration
write lock file, which is not located in the configuration directory.
</pre>