<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-dirmgr/src/bridgedesc.rs, branch arti-v1.3.1</title>
<subtitle>mirror of https://gitlab.torproject.org/tpo/core/arti
</subtitle>
<id>http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.3.1</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.3.1'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2024-11-25T18:20:11Z</updated>
<entry>
<title>TimerangeBound: Stop using std::ops::Bound.</title>
<updated>2024-11-25T18:20:11Z</updated>
<author>
<name>Wesley Aptekar-Cassels</name>
<email>me@wesleyac.com</email>
</author>
<published>2024-10-15T13:58:29Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=1659495eb30ae6a17058418b6d00592373cfdf65'/>
<id>urn:sha1:1659495eb30ae6a17058418b6d00592373cfdf65</id>
<content type='text'>
Fixes: #1691
</content>
</entry>
<entry>
<title>Fix typos in doc comments</title>
<updated>2024-03-06T19:52:42Z</updated>
<author>
<name>Tobias Stoeckmann</name>
<email>tobias@stoeckmann.org</email>
</author>
<published>2024-03-06T19:05:17Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=18db641cca83fa707b3a97fa2975f99063f08875'/>
<id>urn:sha1:18db641cca83fa707b3a97fa2975f99063f08875</id>
<content type='text'>
</content>
</entry>
<entry>
<title>clippy nightly: For now, locally allow blocks_in_conditions</title>
<updated>2024-01-02T15:04:18Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2024-01-02T14:51:30Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=2e459400ebc4cb40622cf2eb42803afafbc05ad4'/>
<id>urn:sha1:2e459400ebc4cb40622cf2eb42803afafbc05ad4</id>
<content type='text'>
Filed
  https://gitlab.torproject.org/tpo/core/arti/-/issues/1176
proposing a final fix.
</content>
</entry>
<entry>
<title>tor-dirclient: Rename download() to send_request() (fmt).</title>
<updated>2023-08-16T15:13:27Z</updated>
<author>
<name>Gabriela Moldovan</name>
<email>gabi@torproject.org</email>
</author>
<published>2023-08-14T00:20:20Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=0fde1d09f50794163e2a5cb3a61f59a555d98c84'/>
<id>urn:sha1:0fde1d09f50794163e2a5cb3a61f59a555d98c84</id>
<content type='text'>
</content>
</entry>
<entry>
<title>tor-dirclient: Rename download() to send_request().</title>
<updated>2023-08-16T15:13:20Z</updated>
<author>
<name>Gabriela Moldovan</name>
<email>gabi@torproject.org</email>
</author>
<published>2023-08-11T18:26:32Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=9a08f04a7698ae237e352c57ebb58456e727fc93'/>
<id>urn:sha1:9a08f04a7698ae237e352c57ebb58456e727fc93</id>
<content type='text'>
`download()` is actually a general-purpose function for sending HTTP
requests on a stream. We will soon repurpose it for `POST`-ing
descriptors, so let's rename it to `send_request`.
</content>
</entry>
<entry>
<title>Throughout: Use *_report!() macros for reporting Errors.</title>
<updated>2023-07-07T17:00:21Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-07-07T13:54:27Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=25c6fe61e4cf230210dffdac2d3c281fcb31c5a9'/>
<id>urn:sha1:25c6fe61e4cf230210dffdac2d3c281fcb31c5a9</id>
<content type='text'>
I identified the cases to replace by searching for the string
`.report()`.  There are a few that I didn't change:

  * A couple of cases that used anyhow::Error,
  * One case that reported two Errors.
  * Two cases in `tor_hsclient::err` that just did
    `error!("Bug: {}")`.

I have also not audited the cases in `tor-hsclient` where we're using
`tor_error::Report` manually.

Nonetheless, closes #949.
</content>
</entry>
<entry>
<title>s/BridgeDescManager/BridgeDescMgr/g in codebase</title>
<updated>2023-04-12T12:49:11Z</updated>
<author>
<name>Neel Chauhan</name>
<email>neel@neelc.org</email>
</author>
<published>2023-04-08T14:54:14Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=be78062bb6dcc34cc88256b23513761516d86ccc'/>
<id>urn:sha1:be78062bb6dcc34cc88256b23513761516d86ccc</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Use ErrorReport's .report() for two errors in error! in bridgedesc.rs</title>
<updated>2023-01-30T18:52:32Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2023-01-30T18:48:29Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=aa7397bc0f43f67f42ed7f2e8dbe2ecdbf302058'/>
<id>urn:sha1:aa7397bc0f43f67f42ed7f2e8dbe2ecdbf302058</id>
<content type='text'>
No functional change, just using the new idiom.
</content>
</entry>
<entry>
<title>"Fix" remaining unchecked-subtraction warnings.</title>
<updated>2023-01-27T14:16:41Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-01-27T13:20:08Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=2127c6b0883cfeedb92c1c88ccff59d63acd22a5'/>
<id>urn:sha1:2127c6b0883cfeedb92c1c88ccff59d63acd22a5</id>
<content type='text'>
In both cases I think it's fine to panic; but it's best to do so
explicitly.
</content>
</entry>
<entry>
<title>dirmgr: Spelling fixes and normali[sz]ations</title>
<updated>2022-12-06T14:02:48Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-12-06T14:02:48Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=02d340e4b20b68629b1c7bd5f8c61324407446a5'/>
<id>urn:sha1:02d340e4b20b68629b1c7bd5f8c61324407446a5</id>
<content type='text'>
</content>
</entry>
</feed>
