<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-config/src/path.rs, branch arti-v1.1.10</title>
<subtitle>mirror of https://gitlab.torproject.org/tpo/core/arti
</subtitle>
<id>http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.10</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.10'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2023-08-23T09:34:00Z</updated>
<entry>
<title>Run maint/add_warning to add lint block everywhere</title>
<updated>2023-08-23T09:34:00Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2023-08-22T14:28:12Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=42df88d6bf6dbb460d2e5e1cd4838aafaffbe9ac'/>
<id>urn:sha1:42df88d6bf6dbb460d2e5e1cd4838aafaffbe9ac</id>
<content type='text'>
</content>
</entry>
<entry>
<title>tor-config: Expand NoProjectDirs error message</title>
<updated>2023-08-08T10:12:16Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2023-08-08T10:12:16Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=849c83052ef82b9946b82a730bf6f3c2f59aaa63'/>
<id>urn:sha1:849c83052ef82b9946b82a730bf6f3c2f59aaa63</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Run maint/add_warning to actually apply new lint allows</title>
<updated>2023-07-10T12:49:51Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2023-07-10T11:19:32Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=473447a82e099fd52a674c28f5bc24b3e05208c0'/>
<id>urn:sha1:473447a82e099fd52a674c28f5bc24b3e05208c0</id>
<content type='text'>
</content>
</entry>
<entry>
<title>tor-config: Apply deferred rustfmt churn</title>
<updated>2023-03-21T16:37:50Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2023-03-21T16:37:35Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=cc399c3a291355813e87b06fb43bbad06ec7c3da'/>
<id>urn:sha1:cc399c3a291355813e87b06fb43bbad06ec7c3da</id>
<content type='text'>
</content>
</entry>
<entry>
<title>tor-config: Do minimal $ and ~ handling even without expand-paths</title>
<updated>2023-03-21T16:37:50Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2023-03-21T16:36:07Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=c18f5c35dce87296e635967535812c7b3aaf892d'/>
<id>urn:sha1:c18f5c35dce87296e635967535812c7b3aaf892d</id>
<content type='text'>
Fixes #790
</content>
</entry>
<entry>
<title>tor-config: Make CfgPathError PartialEq but only when testing</title>
<updated>2023-03-21T16:33:24Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2023-03-21T16:33:24Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=92bc9ef79054673353166a950617cf7acd8e0d50'/>
<id>urn:sha1:92bc9ef79054673353166a950617cf7acd8e0d50</id>
<content type='text'>
So, this is not a semver addition.
</content>
</entry>
<entry>
<title>tor-config: Fix build when expand-paths is disabled</title>
<updated>2023-03-21T16:33:12Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2023-03-21T16:33:12Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=a0b78837ad5fcd8b73a9901387eb1ef53337bf39'/>
<id>urn:sha1:a0b78837ad5fcd8b73a9901387eb1ef53337bf39</id>
<content type='text'>
</content>
</entry>
<entry>
<title>tor-config: paths, unexpanded: use infallible conversion</title>
<updated>2023-03-21T16:08:47Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2023-03-21T16:08:47Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=42ad8d99aa2bae2c5195cb0ecca939b7eda20e84'/>
<id>urn:sha1:42ad8d99aa2bae2c5195cb0ecca939b7eda20e84</id>
<content type='text'>
str can always be made into a PathBuf.
</content>
</entry>
<entry>
<title>Allow clippy::unchecked_duration_subtraction in tests</title>
<updated>2023-01-27T13:28:02Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-01-27T13:01:45Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=a6dd92843edf2bd4c58de62a0d562921e4191ada'/>
<id>urn:sha1:a6dd92843edf2bd4c58de62a0d562921e4191ada</id>
<content type='text'>
This panics on error, and we're fine with a panic on misbehavior in
tests.
</content>
</entry>
<entry>
<title>tor-config: Update to shellexpand 3.x</title>
<updated>2022-12-06T15:15:22Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2022-12-06T15:11:39Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=ba338bdf371250210474346bf0ac492d3bc70672'/>
<id>urn:sha1:ba338bdf371250210474346bf0ac492d3bc70672</id>
<content type='text'>
This is the new upstream version (published by me, recently).
It has the same MSRV and one breaking change:

The caller who specifies a home dir function for substituting into
strings, must now supply a string, not Path.  Previously shellexpand
would allow the caller to supply non-unicode data, and then simply not
substitute it.  That was an infelicity in the shellexpand API.

Now this infelicity is pushed into our code.  The overall behaviour of
Arti hasn't changed as a result.  And it seems reasonable to me.

shellexpand 3.x also has a module for expanding Paths instead, in
response to requests for this filed as upstream tickets.  We *could*
use that but I am not sanguine about that approach: the Pathness would
spread throughout much of our config and file handling code.

I think we should at the very least postpone trying to work with
invalid-unicode-paths as long as we can.
</content>
</entry>
</feed>
