<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/arti/src/reload_cfg.rs, branch arti-v1.6.0</title>
<subtitle>mirror of https://gitlab.torproject.org/tpo/core/arti
</subtitle>
<id>http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.6.0</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.6.0'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2025-05-29T14:21:17Z</updated>
<entry>
<title>*: suppress cognitive_complexity warnings from nightly</title>
<updated>2025-05-29T14:21:17Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2025-05-21T14:48:35Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=5327d3e22a83b8469a5d4191d92e1364344ddc93'/>
<id>urn:sha1:5327d3e22a83b8469a5d4191d92e1364344ddc93</id>
<content type='text'>
Apparently clippy nightly is better (or worse?) about detecting
complex functions than before, so I'm suppressing these warnings
where they occur.

I have mixed feelings about these warnings:  On the plus side,
they really do help to detect functions that are twistier than they
need to be.  On the minus side, they get confused by tracing macros,
and the "allows" do pile up.  But on the plus side, those "allows"
do provide a way to find functions that need to be refactored,
and they are never uglier than the functions they decorate.
</content>
</entry>
<entry>
<title>arti: Disable RPC reconfiguration for now</title>
<updated>2024-12-19T21:12:25Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2024-12-11T16:53:01Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=04bc3d2e0444c8a7112e813f20d83d58b279df45'/>
<id>urn:sha1:04bc3d2e0444c8a7112e813f20d83d58b279df45</id>
<content type='text'>
</content>
</entry>
<entry>
<title>tor-config: Document the limitations of the FileWatcher.</title>
<updated>2024-10-16T15:59:27Z</updated>
<author>
<name>Gabriela Moldovan</name>
<email>gabi@torproject.org</email>
</author>
<published>2024-10-16T15:38:00Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=960ff90c2e595928389b2c8feaf2e052d7dc9f58'/>
<id>urn:sha1:960ff90c2e595928389b2c8feaf2e052d7dc9f58</id>
<content type='text'>
</content>
</entry>
<entry>
<title>arti: Temporarily disable a flaky test.</title>
<updated>2024-09-05T16:57:02Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2024-09-05T16:56:27Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=9ca840b12bea42f8bfdd691a8b6208257ca3609b'/>
<id>urn:sha1:9ca840b12bea42f8bfdd691a8b6208257ca3609b</id>
<content type='text'>
This effectively reverts 71e3d52f5aeb34ca7bca80053079a8c7505b99ac,
which was itself a revert of disabling this test the first time.

Sadly it still doesn't seem to be reliable.  We have agreed on IRC to
disable it for now.
</content>
</entry>
<entry>
<title>Merge branch 'slow-test' into 'main'</title>
<updated>2024-09-05T10:39:48Z</updated>
<author>
<name>Ian Jackson</name>
<email>iwj@torproject.org</email>
</author>
<published>2024-09-05T10:39:48Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=30cb69520890b7a85f436de0d40dfa95ef0c95d8'/>
<id>urn:sha1:30cb69520890b7a85f436de0d40dfa95ef0c95d8</id>
<content type='text'>
arti: Make the config watcher debounce interval configurable.

Closes #1589

See merge request tpo/core/arti!2387</content>
</entry>
<entry>
<title>arti: Make the config watcher debounce interval configurable (fmt).</title>
<updated>2024-09-04T13:13:42Z</updated>
<author>
<name>Gabriela Moldovan</name>
<email>gabi@torproject.org</email>
</author>
<published>2024-09-04T13:10:43Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=d952b2bd75135c95d8400da49f81439c0d36e79f'/>
<id>urn:sha1:d952b2bd75135c95d8400da49f81439c0d36e79f</id>
<content type='text'>
</content>
</entry>
<entry>
<title>arti: Make the config watcher debounce interval configurable.</title>
<updated>2024-09-04T13:13:32Z</updated>
<author>
<name>Gabriela Moldovan</name>
<email>gabi@torproject.org</email>
</author>
<published>2024-09-04T13:07:16Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=15ade3cd9be04c81200681b32fedd042bf515072'/>
<id>urn:sha1:15ade3cd9be04c81200681b32fedd042bf515072</id>
<content type='text'>
Previously, the `reload_cfg::test::watch_multiple` test would take about
3s to run. This test modifies 3 files and waits for the corresponding
`reconfigure()` events to fire. Because of the
`sleep(DEBOUNCE_INTERVAL)` in `run_watcher`, it would wind up waiting
for about 1s for each of them.

This makes the event debouncing optional, and disables it in the tests.

Closes #1589
</content>
</entry>
<entry>
<title>Revert "arti: Temporarily disable a flaky test."</title>
<updated>2024-08-29T09:12:52Z</updated>
<author>
<name>Gabriela Moldovan</name>
<email>gabi@torproject.org</email>
</author>
<published>2024-08-28T17:59:05Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=71e3d52f5aeb34ca7bca80053079a8c7505b99ac'/>
<id>urn:sha1:71e3d52f5aeb34ca7bca80053079a8c7505b99ac</id>
<content type='text'>
This reverts commit ececf6be2eaffc201666cd3413dc19c025be66de.
</content>
</entry>
<entry>
<title>arti: Write the test config atomically.</title>
<updated>2024-08-29T09:12:48Z</updated>
<author>
<name>Gabriela Moldovan</name>
<email>gabi@torproject.org</email>
</author>
<published>2024-08-28T17:55:31Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=45f2c61d205c4ea3a232254d069503a8875f5c29'/>
<id>urn:sha1:45f2c61d205c4ea3a232254d069503a8875f5c29</id>
<content type='text'>
The flakiness from the `watch_single_file` test was caused by the race
between the config write, and the fake SIGHUP "signal" sent on
`sighup_tx`: sometimes, the sighup would get handled between creating
the config file and writing its contents. In those cases, the config
received in `TestModule::reconfigure` would be `Default::default()`,
which caused an assertion to fail (because the test is expecting to
receive the `ArtiConfig` it wrote to disk).

Closes #1549
</content>
</entry>
<entry>
<title>tor-config: Rename watch_file to watch_path.</title>
<updated>2024-08-27T13:35:30Z</updated>
<author>
<name>Gabriela Moldovan</name>
<email>gabi@torproject.org</email>
</author>
<published>2024-08-27T11:30:19Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=5619aa0ed22a2421defa53189564baea24a0bf16'/>
<id>urn:sha1:5619aa0ed22a2421defa53189564baea24a0bf16</id>
<content type='text'>
`FileWatcher::watch_file` can be used with arbitrary paths.
</content>
</entry>
</feed>
