mirrors/arti.git/crates/tor-hsservice, branch arti-v1.2.7mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.2.72024-09-03T17:57:12ZBump all the unstable tor- and arti- crates to 0.22.0.2024-09-03T17:57:12ZGabriela Moldovangabi@torproject.org2024-09-03T17:25:54Zurn:sha1:c3c266707f2fd361a447d922c5acfbb3938d88f2
Done using:
```
for crate in $(./maint/list_crates | rg '^(tor|arti-)'); do
cargo set-version -p $crate 0.22.0
done
```
oneshot-fused-workaround: Set the initial version to 0.1.0.2024-09-03T15:22:43ZGabriela Moldovangabi@torproject.org2024-09-03T14:55:25Zurn:sha1:a88af5e93762a8cd95321a3adc31b2bc2ae3bd4d
This is the first time we're publishing this, so let's start at 0.1.0.
Fix formatting issues introduced by fixup-features.2024-09-03T10:00:30ZGabriela Moldovangabi@torproject.org2024-09-03T09:21:55Zurn:sha1:dfe02110114be3f17e439bf99f776521fd044e15Run fixup-features in preparation for release.2024-09-03T10:00:30ZGabriela Moldovangabi@torproject.org2024-09-03T09:10:10Zurn:sha1:1eea611d14630c2901962e5cba408f2b7cf456fcextract tor_async_utils::oneshot into ::oneshot-fused-workaround2024-08-28T14:27:46ZJim Newsomejnewsome@torproject.org2024-08-22T19:20:36Zurn:sha1:46f7f01092e6ac55e3e958dc3a2228b1d36e26a1
Having this in the `tor-async-utils` crate prevents us from doing both
of the following without introducing a circular dependency:
* using it in `tor-rtmock` (which we currently do, particularly in
tests).
* using `tor-rtmock` to test things in `tor-async-utils`. We don't do
this yet, but it is generally sensible to do so. In particular we
want to move the `stream_peak` module there, which is currently tested
with `tor-rtmock`.
Moving this into its own crate avoids this circular dependency.
tor-hsservice: Recreate the file watcher on every key_dir change event.2024-08-27T13:35:30ZGabriela Moldovangabi@torproject.org2024-08-27T10:48:02Zurn:sha1:59bd96ddcc073880655bd9ee18c60c85df01ae82
This ensures that if a directory used as a `key_dir` is moved (e.g.
renamed), and then moved back to its original location (the one
specified in `key_dirs`), our watcher continues watching the `key_dirs`
contents.
tor-config: Rename watch_file to watch_path.2024-08-27T13:35:30ZGabriela Moldovangabi@torproject.org2024-08-27T11:30:19Zurn:sha1:5619aa0ed22a2421defa53189564baea24a0bf16
`FileWatcher::watch_file` can be used with arbitrary paths.
tor-hsservice: Make sure we always watch the parents of the key_dirs.2024-08-27T13:35:11ZGabriela Moldovangabi@torproject.org2024-08-27T11:24:48Zurn:sha1:6de13a8b96892e40041f773b5e937e323a087b2e
This ensures that if a `key_dir` is created after we start watching it
(or if it's moved), we are still able to detect changes.
tor-hsservice: Always recreate the file watcher if the config changes.2024-08-27T13:08:38ZGabriela Moldovangabi@torproject.org2024-08-22T14:59:35Zurn:sha1:973a1c171475cf1a79e8fa13e2eb80f25914324c
While this means we will be recreating the watcher slightly more often
than necessary, this new approach is less error-prone than what we had
before.
Merge branch 'ci' into 'main'2024-08-27T11:21:42ZIan Jacksoniwj@torproject.org2024-08-27T11:21:42Zurn:sha1:c030cb301698ebfb001f618ab7b40ee0834b980d
Run tests of every crate, with all features disabled
See merge request tpo/core/arti!2350