<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-rtcompat/src/impls/tokio.rs, branch arti-v1.2.6</title>
<subtitle>mirror of https://gitlab.torproject.org/tpo/core/arti
</subtitle>
<id>http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.2.6</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.2.6'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2023-12-18T17:02:12Z</updated>
<entry>
<title>tor-rtcompat: use track-caller for thin wrappers</title>
<updated>2023-12-18T17:02:12Z</updated>
<author>
<name>Jim Newsome</name>
<email>jnewsome@torproject.org</email>
</author>
<published>2023-12-18T17:02:12Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=30c07a6c0b544a55795985ff6451f72818fda1c8'/>
<id>urn:sha1:30c07a6c0b544a55795985ff6451f72818fda1c8</id>
<content type='text'>
In particular, when the (unstable) tokio tracing feature is enabled,
every tracing line includes the name of where the current task was
created. Without this change, that ends up being the name of
intermediate trait methods like TokioRuntimeHandle::block_on, which is
not very helpful.

Adding the `track_caller` attribute causes the name of the caller of
these methods to be used instead, which is typically more helpful.

IIUC this change is not breaking in terms of semver
https://rustc-dev-guide.rust-lang.org/backend/implicit-caller-location.html.
</content>
</entry>
<entry>
<title>Upgrade async_executors dependency to 0.7.0</title>
<updated>2023-09-28T13:47:31Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-09-28T13:47:31Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=1be1b1616349749988a6483b357e6f017a13c03c'/>
<id>urn:sha1:1be1b1616349749988a6483b357e6f017a13c03c</id>
<content type='text'>
</content>
</entry>
<entry>
<title>UdpSocket: remove support for connect().</title>
<updated>2022-03-18T19:39:40Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-03-18T19:34:51Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=2aa5f45bc8bb3153fca2cc9e33b7cd951e1415c4'/>
<id>urn:sha1:2aa5f45bc8bb3153fca2cc9e33b7cd951e1415c4</id>
<content type='text'>
Currently, Arti doesn't need this.  But once it does, it will be
way better to have a separate type for connected sockets, rather
than having to error-check every time somebody gives us a socket.

Part of #410
</content>
</entry>
<entry>
<title>add simple unit test on UDP</title>
<updated>2022-03-14T20:19:20Z</updated>
<author>
<name>trinity-1686a</name>
<email>trinity@deuxfleurs.fr</email>
</author>
<published>2022-03-11T17:27:59Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=f4581ffd0438a0e07839036f36960ad41742be03'/>
<id>urn:sha1:f4581ffd0438a0e07839036f36960ad41742be03</id>
<content type='text'>
</content>
</entry>
<entry>
<title>add skeleton for DNS handling</title>
<updated>2022-03-14T19:59:35Z</updated>
<author>
<name>trinity-1686a</name>
<email>trinity@deuxfleurs.fr</email>
</author>
<published>2022-03-06T16:34:13Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=9b3be0ad47ea5eca08596d83d3a25bd3ae0c2abf'/>
<id>urn:sha1:9b3be0ad47ea5eca08596d83d3a25bd3ae0c2abf</id>
<content type='text'>
</content>
</entry>
<entry>
<title>add udp to runtime</title>
<updated>2022-03-14T19:59:33Z</updated>
<author>
<name>trinity-1686a</name>
<email>trinity@deuxfleurs.fr</email>
</author>
<published>2022-03-05T18:49:38Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=4a44ef56c0743775d49eca138a253f11e93c7a35'/>
<id>urn:sha1:4a44ef56c0743775d49eca138a253f11e93c7a35</id>
<content type='text'>
</content>
</entry>
<entry>
<title>tor-rtcompat: remove some unused code.</title>
<updated>2022-01-27T20:52:59Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-01-27T20:52:59Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=19f878b3aa7b648605487f94871ab3e5c5b949fd'/>
<id>urn:sha1:19f878b3aa7b648605487f94871ab3e5c5b949fd</id>
<content type='text'>
Nothing actually used these accessor functions, and it's not clear
what would.  We can add them later if they're needed.
</content>
</entry>
<entry>
<title>Rename `SpawnBlocking` trait to `BlockOn`.</title>
<updated>2022-01-26T19:06:58Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-01-26T18:59:37Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=bf8fa66d36298561cc868706f748049cec23f5eb'/>
<id>urn:sha1:bf8fa66d36298561cc868706f748049cec23f5eb</id>
<content type='text'>
This avoids a future confusion with the new `SpawnBlocking` trait in
async_executors v0.5, and better describes what the trait provides.
</content>
</entry>
<entry>
<title>Remove no-longer-needed tokio runtime helper macro</title>
<updated>2022-01-26T19:06:58Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-01-25T22:58:44Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=99c59a8f2b3d1d97110ecdfc1021668f88177c85'/>
<id>urn:sha1:99c59a8f2b3d1d97110ecdfc1021668f88177c85</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Unify TokioRuntime and TokioRuntimeHandle</title>
<updated>2022-01-26T19:06:58Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-01-25T21:52:33Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=668364d75d5fec06d235a684dfc6c8c89e543503'/>
<id>urn:sha1:668364d75d5fec06d235a684dfc6c8c89e543503</id>
<content type='text'>
Having separate types here doesn't justify the (very limited)
benefit of distinguishing between the case where we have created an
executor that we own and the case where we have a handle to an
already-running tokio executor.

Part of #301.
</content>
</entry>
</feed>
