<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/arti-config/src/arti_defaults.toml, branch derive-traits</title>
<subtitle>mirror of https://gitlab.torproject.org/tpo/core/arti
</subtitle>
<id>http://git.dilluti0n.com/mirrors/arti.git/atom?h=derive-traits</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=derive-traits'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2022-02-03T16:11:21Z</updated>
<entry>
<title>Document that `notify` behavior is strange with symlinks</title>
<updated>2022-02-03T16:11:21Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-02-03T14:52:07Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=49431f54420db007ef940e481445c5c29ee30e45'/>
<id>urn:sha1:49431f54420db007ef940e481445c5c29ee30e45</id>
<content type='text'>
(More specifically, `notify` behaves differently on different
platforms.  On some, it can watch specific directory objects on the
filesystem, and so it only notices when _those_ directories change.
If you change a symlink so that the canonical configuration file
location is now in some other directory, `notify` won't notice.  But
on other platforms, notify just does "stat()" in a loop. On those,
it _will_ notice if the configuration file changes.)
</content>
</entry>
<entry>
<title>Make configuration-watching configurable and off-by-default.</title>
<updated>2022-02-01T21:04:59Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-02-01T20:36:30Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=1fbea7cd1e58af06eae5a65d6e6ca56a5cabb3f7'/>
<id>urn:sha1:1fbea7cd1e58af06eae5a65d6e6ca56a5cabb3f7</id>
<content type='text'>
I'm slightly concerned about whether this is behavior people would
expect to have on-by-default, so let's make this off-by-default for
now.

Maybe the `application` and `system` sections should merge?
</content>
</entry>
<entry>
<title>Make max_file_limit configurable</title>
<updated>2022-01-28T11:17:49Z</updated>
<author>
<name>Neel Chauhan</name>
<email>neel@neelc.org</email>
</author>
<published>2022-01-28T11:17:49Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=417809123c7101de64aa8e1e27c3a76a862dec1d'/>
<id>urn:sha1:417809123c7101de64aa8e1e27c3a76a862dec1d</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Tracing configuration for logfiles, per-target filters</title>
<updated>2022-01-10T18:23:11Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-01-07T15:52:43Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=1a16f5a7d63e63b606f8cc21ad948803ef1a8245'/>
<id>urn:sha1:1a16f5a7d63e63b606f8cc21ad948803ef1a8245</id>
<content type='text'>
Previously we could only configure one global tracing filter that
applied to stdout and journald.  There was no support for log files,
either.

This patch fixes both issues, by substantially revising the
configuration format: There are now separate filters for each log
file, for journald, and for the console log.  Because we want to
allow multiple logfiles, they have to go into an array in the
configuration.

The configuration logic has grown a bit complicated in its types,
since the tracing_subscriber crate would prefer to have the complete
structure of tracing Layers known statically. That's fine when you
know how many you have, and which kinds there will be, but for
the runtime-configuration case we need to mess around with
`Box&lt;dyn Layer ...&gt;`.

I also had to switch from tracing_subscriber's EnvFilter to its
Targets filter.  It seems "EnvFilter" can only be applied as a Layer
in itself, and won't work as a Filter on an individual Layer.

Closes #166.

Closes #170.
</content>
</entry>
<entry>
<title>Rename timeout_rules to stream_timeouts.</title>
<updated>2021-12-07T19:03:14Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2021-12-07T19:03:14Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=46c917d127519fbf917c391afc30fa83c794061e'/>
<id>urn:sha1:46c917d127519fbf917c391afc30fa83c794061e</id>
<content type='text'>
(There are other timeout rules, after all.)

Also, rename stream_timeout to connect_timeout, to make it more clear
when it applies.
</content>
</entry>
<entry>
<title>Merge branch 'revised_preemptive_config' into 'main'</title>
<updated>2021-12-07T17:51:42Z</updated>
<author>
<name>eta</name>
<email>tor@eta.st</email>
</author>
<published>2021-12-07T17:51:42Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=2614fb736ee4e66a8145a05ef0b1a28cde6d022a'/>
<id>urn:sha1:2614fb736ee4e66a8145a05ef0b1a28cde6d022a</id>
<content type='text'>
Usability: renaming and documentation in preemptive circuit config

See merge request tpo/core/arti!176</content>
</entry>
<entry>
<title>Merge branch 'bug252' into 'main'</title>
<updated>2021-12-07T17:27:38Z</updated>
<author>
<name>eta</name>
<email>tor@eta.st</email>
</author>
<published>2021-12-07T17:27:38Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=47c3163ce5038ea411874a3694ad9679caaaf473'/>
<id>urn:sha1:47c3163ce5038ea411874a3694ad9679caaaf473</id>
<content type='text'>
Make DNS fields in arti-client/src/client.rs configurable

Closes #252

See merge request tpo/core/arti!171</content>
</entry>
<entry>
<title>Clarify names and docs for predictive circuits.</title>
<updated>2021-12-07T17:09:05Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2021-12-07T17:00:20Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=48f77a93c0f030a6060965d96142adaf78c62f44'/>
<id>urn:sha1:48f77a93c0f030a6060965d96142adaf78c62f44</id>
<content type='text'>
Also, use humantime_serde, rather than a number of seconds, to indicate
configuration time.
</content>
</entry>
<entry>
<title>Rename circuits_preemptive to preemptive_circuits</title>
<updated>2021-12-07T17:06:53Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2021-12-07T16:38:33Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=c2e20a242a3041b08afbc17f0420809fab2efc5d'/>
<id>urn:sha1:c2e20a242a3041b08afbc17f0420809fab2efc5d</id>
<content type='text'>
This obeys a few conventions:
  * adjective before noun
  * config objects end with "config"
</content>
</entry>
<entry>
<title>Rename ClientDNSConfig -&gt; ClientTimeoutConfig</title>
<updated>2021-12-07T16:43:58Z</updated>
<author>
<name>Neel Chauhan</name>
<email>neel@neelc.org</email>
</author>
<published>2021-12-07T16:43:58Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=9c66b68c5af448c2a806d9d914e913c44325a0d4'/>
<id>urn:sha1:9c66b68c5af448c2a806d9d914e913c44325a0d4</id>
<content type='text'>
</content>
</entry>
</feed>
