<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-cell/src/relaycell, branch arti-v1.5.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.5.0</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.5.0'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2025-08-13T18:43:05Z</updated>
<entry>
<title>tor-hsservice: Change capping of PoW effort.</title>
<updated>2025-08-13T18:43:05Z</updated>
<author>
<name>Wesley Aptekar-Cassels</name>
<email>me@wesleyac.com</email>
</author>
<published>2025-08-13T18:20:11Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=8e9e5a2f6ff20360816896b971408e8bf1b5c7ea'/>
<id>urn:sha1:8e9e5a2f6ff20360816896b971408e8bf1b5c7ea</id>
<content type='text'>
This caps the PoW effort during sorting, rather than at intake.

This allows us to record efforts that are capped in our metrics
histogram while only recording metrics after the PoW solve has actually
been verified.
</content>
</entry>
<entry>
<title>Switch Cargo.toml files to edition 2024.</title>
<updated>2025-08-07T15:28:36Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2025-08-06T01:19:58Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=77b0de43b8c67cdb81befe0680a3df43b6ad37bc'/>
<id>urn:sha1:77b0de43b8c67cdb81befe0680a3df43b6ad37bc</id>
<content type='text'>
First, run

```
git grep -l "^edition =" |
    xargs perl -i -pe 's/^edition *=.*/edition = "2024"/;'
```

Second, manually verify that all Cargo.toml files have changed,
and nothing else has changed.

Third, run cargo fmt again.
</content>
</entry>
<entry>
<title>Merge branch 'msrv-fixes' into 'main'</title>
<updated>2025-08-06T02:11:30Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2025-08-06T02:11:30Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=283da978ceb5dc50ff21ebaa4b823d04e14dd0c9'/>
<id>urn:sha1:283da978ceb5dc50ff21ebaa4b823d04e14dd0c9</id>
<content type='text'>
Resolve a few issues that had been waiting for an MSRV update.

See merge request tpo/core/arti!3129</content>
</entry>
<entry>
<title>tor-cell: Check strictly-ascending property more efficiently</title>
<updated>2025-08-06T00:44:46Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2025-08-06T00:44:46Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=ab75b509ffdbb2e826ad14c04d65894d8be17b43'/>
<id>urn:sha1:ab75b509ffdbb2e826ad14c04d65894d8be17b43</id>
<content type='text'>
I had been planning to use `[]::is_sorted` here, once we had
MSRV &gt;= 1.82, but it turns out that we wanted strictly ascending
sequence, whereas `is_sorted` checks for a non-descreasing sequence.
</content>
</entry>
<entry>
<title>tor-cell: Add ProofOfWorkV1::cap_effort function.</title>
<updated>2025-08-05T23:50:24Z</updated>
<author>
<name>Wesley Aptekar-Cassels</name>
<email>me@wesleyac.com</email>
</author>
<published>2025-07-31T16:30:32Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=d173976048040852faf53ed6388730fb78b4d090'/>
<id>urn:sha1:d173976048040852faf53ed6388730fb78b4d090</id>
<content type='text'>
</content>
</entry>
<entry>
<title>tor-cell: add `FlowCtrlVersion::V0`</title>
<updated>2025-07-16T17:36:43Z</updated>
<author>
<name>Steven Engler</name>
<email>opara@torproject.org</email>
</author>
<published>2025-07-16T14:50:18Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=15422178d62506ad61b87a38f59cbc8536c5becd'/>
<id>urn:sha1:15422178d62506ad61b87a38f59cbc8536c5becd</id>
<content type='text'>
</content>
</entry>
<entry>
<title>tor-cell: remove `flowctl-cc` feature and make XON/XOFF cells stable</title>
<updated>2025-07-15T05:33:18Z</updated>
<author>
<name>Steven Engler</name>
<email>opara@torproject.org</email>
</author>
<published>2025-07-15T05:27:21Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=676dbdb43f2a930b7dc89d2a6275338064fd37bf'/>
<id>urn:sha1:676dbdb43f2a930b7dc89d2a6275338064fd37bf</id>
<content type='text'>
I don't see any further changes being needed for these types, and it
simplifies a lot of future code in tor-proto that uses these types.
</content>
</entry>
<entry>
<title>tor-cell: add a const constructor for `FlowCtrlVersion`</title>
<updated>2025-07-15T05:15:00Z</updated>
<author>
<name>Steven Engler</name>
<email>opara@torproject.org</email>
</author>
<published>2025-07-14T15:45:17Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=4ab73988d87d263f741df538e50e7ecef7d7fd57'/>
<id>urn:sha1:4ab73988d87d263f741df538e50e7ecef7d7fd57</id>
<content type='text'>
</content>
</entry>
<entry>
<title>tor-cell: add `Xon`/`Xoff` cells</title>
<updated>2025-06-09T14:09:20Z</updated>
<author>
<name>Steven Engler</name>
<email>opara@torproject.org</email>
</author>
<published>2025-06-09T14:01:28Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=2d3f0918ab866ef25fe259c6648e208a01865a93'/>
<id>urn:sha1:2d3f0918ab866ef25fe259c6648e208a01865a93</id>
<content type='text'>
</content>
</entry>
<entry>
<title>arti, cell, dirclient: Use expect instead of unwrap.</title>
<updated>2025-05-29T14:21:17Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2025-05-21T13:58:34Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=684d6a02fd044c33e9c40c15012d18853c3bc4c3'/>
<id>urn:sha1:684d6a02fd044c33e9c40c15012d18853c3bc4c3</id>
<content type='text'>
Clippy nightly detects this problem, though earlier clippy verisons
haven't.  The common element here is applying unwrap() to the result
from a write!().
</content>
</entry>
</feed>
