<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-chanmgr, branch arti-v1.2.8</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.8</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.2.8'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2024-09-30T13:04:32Z</updated>
<entry>
<title>Bump arti- and tor- crates to 0.23.0</title>
<updated>2024-09-30T13:04:32Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2024-09-30T13:04:32Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=d6890da4b1f87fd5e834aeb0cc9a7cd4b1d99e88'/>
<id>urn:sha1:d6890da4b1f87fd5e834aeb0cc9a7cd4b1d99e88</id>
<content type='text'>
Per our policy, every one of these gets a minor bump.

Generated with:

```
for crate in $(./maint/list_crates | grep '^\(tor\|arti\)-' ); do
    cargo set-version --bump minor -p $crate;
done
```
(Note the use of `-` at the end end of the grep pattern to prevent
matching the `arti` crate.)
</content>
</entry>
<entry>
<title>Minor bumps on non-tor/arti crates</title>
<updated>2024-09-30T12:56:28Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2024-09-30T12:56:28Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=b29dd6d7f90cf077e8809a1ab317e23535e165c8'/>
<id>urn:sha1:b29dd6d7f90cf077e8809a1ab317e23535e165c8</id>
<content type='text'>
These crates are not in the tor/arti namespace,
but we have given them MSRV bumps:

```
oneshot-fused-workaround
slotmap-careful
fslock-guard
hashx
equix
caret
fs-mistrust
safelog
test-temp-dir
retry-error
```

We are counting this as a breaking change.
Since all of these crates are at 0.x.x,
we have indicated the breaking change with a minor version bump.

This commit was generated with the following script:

```
BUMPS="
oneshot-fused-workaround
slotmap-careful
fslock-guard
hashx
equix
caret
fs-mistrust
safelog
test-temp-dir
retry-error
"

for crate in $BUMPS; do
    cargo set-version --bump minor -p $crate;
done
```
</content>
</entry>
<entry>
<title>Merge branch 'msrv-1.77-and-rusqlite-update' into 'main'</title>
<updated>2024-09-26T14:24:02Z</updated>
<author>
<name>David Goulet</name>
<email>dgoulet@torproject.org</email>
</author>
<published>2024-09-26T14:24:02Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=2ad24dd46615d908cefa68f5a9752d4863b89b6c'/>
<id>urn:sha1:2ad24dd46615d908cefa68f5a9752d4863b89b6c</id>
<content type='text'>
Upgrade MSRV to 1.77 , and rusqlite to 0.32.1

See merge request tpo/core/arti!2451</content>
</entry>
<entry>
<title>Merge branch 'upgrades-20240925' into 'main'</title>
<updated>2024-09-26T12:07:09Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2024-09-26T12:07:09Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=3f478308f0680bc6c9b36ad1c36fdfe8115dc8cf'/>
<id>urn:sha1:3f478308f0680bc6c9b36ad1c36fdfe8115dc8cf</id>
<content type='text'>
Upgrade dependencies in preparation for next week's releases.

See merge request tpo/core/arti!2450</content>
</entry>
<entry>
<title>Upgrade MSRV to 1.77</title>
<updated>2024-09-26T01:54:22Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2024-09-25T14:46:08Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=ff9e93a2a10ef02f436c6f7d7a05739a818b094a'/>
<id>urn:sha1:ff9e93a2a10ef02f436c6f7d7a05739a818b094a</id>
<content type='text'>
This will allow us to upgrade to the latest version of rusqlite.
</content>
</entry>
<entry>
<title>Upgrade to derive_more version 1.0.0</title>
<updated>2024-09-25T14:37:18Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2024-09-25T14:37:18Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=6a12c2ba8515226a772d5f4a81930bf42d67535a'/>
<id>urn:sha1:6a12c2ba8515226a772d5f4a81930bf42d67535a</id>
<content type='text'>
The `derive_more` crate broke backward compatibility with this version,
so this change involved quite a few manual fixups.
With luck, they'll keep compatibility for some while in the future.
</content>
</entry>
<entry>
<title>socks users: copy the correct amount in our drain logic.</title>
<updated>2024-09-24T20:55:25Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2024-09-24T20:55:25Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=dceeb82f7d1154894ab9c7c607d68f8335bb9615'/>
<id>urn:sha1:dceeb82f7d1154894ab9c7c607d68f8335bb9615</id>
<content type='text'>
When calling copy_within, we want to copy the amount of data that
we're keeping; previously, we were copying an extra `action.drain`
bytes, which could have led to a panic.

Spotted by Opara.
</content>
</entry>
<entry>
<title>socks users: detect closed sockets.</title>
<updated>2024-09-24T20:35:07Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2024-09-24T18:16:42Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=0c595818f713916d94b7b0e4062f953fad7c9799'/>
<id>urn:sha1:0c595818f713916d94b7b0e4062f953fad7c9799</id>
<content type='text'>
Without this check, our socks code can enter an infinite loop
if a socket is closed at the wrong time.

Resolves TROVE-2024-011.

Fixes #1635.
</content>
</entry>
<entry>
<title>rtcompat: Rename TcpProvider to NetStreamProvider.</title>
<updated>2024-09-24T13:10:11Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2024-09-19T11:55:22Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=8c2d84000e4d5ba74e7b6b4e9dac3fc700f618b5'/>
<id>urn:sha1:8c2d84000e4d5ba74e7b6b4e9dac3fc700f618b5</id>
<content type='text'>
(And similarly rename TcpListener to NetStreamListener,
along with their TcpStream/TcpListener associated types.)

These types are about to become generic over addresses,
and therefore shouldn't be named after TCP.

Renaming was done mostly with Rust Analyzer,
except for some macros that needed to be hand-edited.

(I'll revise the comments in the next commit;
this one is all about renaming.)
</content>
</entry>
<entry>
<title>rtcompat: Remove accept() from TcpListener</title>
<updated>2024-09-24T13:10:11Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2024-09-18T22:57:09Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=168f55df05f4b56fd61423c020ce62e93f1d7a9f'/>
<id>urn:sha1:168f55df05f4b56fd61423c020ce62e93f1d7a9f</id>
<content type='text'>
It's redundant with the incoming() method (which turns the
TcpListener into a Stream of connections), and nothing actually used
it outside of tests.

Removing this method allows us to simplify our TcpListener code a
good deal, as can be seen by some of the implementations we removed
from our example and testing code.
</content>
</entry>
</feed>
