Recent commits to derivepassphrase.git (6372560fd2c27a91c55769659a1748a0cc3ca5d1)

Update translations template

2025-03-16T13:33:37+01:00

</pre>

Merge topic branch 'vault-cli-objectification' into master

2025-03-16T13:23:38+01:00

* vault-cli-objectification:
  Reimplement the `vault` CLI as methods of a context object
</pre>

Reimplement the `vault` CLI as methods of a context object

2025-03-16T13:23:05+01:00

Introduce a "vault context" object holding the associated data for the
call to the `derivepassphrase vault` CLI, and implement the actual CLI
as a collection of methods on this object.  The "vault context" object
mostly just wraps the click context object and encodes the dispatch
table for the CLI operations.  The main advantage of this modelling is
the much smaller size per, and lower cyclomatic complexity of, each CLI
operation.

As an implementation detail, the old implementation of the
`get_user_config` inner function's error handling branch for `OSError`
had coverage testing purely by accident, because `get_user_config` was
being called unconditionally, very early in the CLI control flow.  The
refactored CLI however reads the user configuration only as needed for
the specific operation. So this error handling branch needs a new,
separate test.

As a further implementation detail, the `is_param_set` inner function no
longer caches its result, because it is now an object method:
`functools.cache` explicitly documents that adding a cache to object
methods causes a circular reference between the cache and the object via
the `self` parameter.  Given the actual contents of this function, there
appears to be little point in working around this memory issue just to
outfit an already cheap operation (a single `Mapping.get` call) with
a cache.

As yet another further implementation detail, checking for misleading
passphrases should work even if the passed configuration snippet is not
technically a `dict`, but rather a `Mapping`.

Finally, due to the vault context object now wrapping the click context,
it is possible (and sensible) to wrap the logging calls into methods of
the vault context object so that less out-of-bounds information needs to
be passed to the logger explicitly at the call site.
</pre>

Merge topic branch 'hatch-test-matrix' into master

2025-03-13T13:32:54+01:00

* hatch-test-matrix:
  Add PyPy 3.11 to the test matrix
</pre>

Add PyPy 3.11 to the test matrix

2025-03-13T13:21:20+01:00

</pre>

Merge topic branch 'concurrency-audit' into master

2025-03-13T13:18:24+01:00

* concurrency-audit:
  Document the results of the concurrency audit
  Lock the derivepassphrase CLI against concurrent updating
  Lock derivepassphrase internals against concurrent updating

GitHub: Closes #22.
</pre>

Document the results of the concurrency audit

2025-03-13T13:17:03+01:00

</pre>

Lock the derivepassphrase CLI against concurrent updating

2025-03-02T16:27:06+01:00

In a very coarse manner, after command-line parsing, detect whether the
CLI operation is a read-write operation or a read-only one, and if it is
read-write, run the whole operation while holding a lock.

The lock is held on a temporary file whose basename is dependent on the
full path to the `derivepassphrase` configuration directory.  The file
is stored in the system temporary directory if possible, and will be
synchronized using `msvcrt.locking` or `fcntl.flock`, whichever is
appropriate.

Coverage checking for the Windows-specific application code is disabled
because we have no Windows runners for the test suite.  The test suite
itself merely adds tests for the temporary directory function, but is
otherwise unchanged.
</pre>

Lock derivepassphrase internals against concurrent updating

2025-02-28T20:08:07+01:00

Specifically, protect the attributes of Sequin and
VaultNativeConfigParser objects (and derived objects) from concurrent
modification via threading locks, and document that they are
thread-safe.
</pre>

Merge branch 'documentation-fixes'

2025-02-21T22:52:10+01:00

* documentation-fixes:
  Document version output contents in the manpages
  Update the `--help` and `--version` texts in the manpages
  Consult the version output in the documentation where it makes sense
  Mention support for other Python distributions in README
  Fix a minor documentation nitpick in the tests
  Update the install instructions in the README
  Re-consolidate test parametrizations for notes-related tests
  Fix minor formatting errors in the manpages
  Fix minor nitpicks in tests
</pre>