<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-cell, 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>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>Bump MSRV from 1.70 to 1.75.</title>
<updated>2024-09-16T21:18:31Z</updated>
<author>
<name>Wesley Aptekar-Cassels</name>
<email>me@wesleyac.com</email>
</author>
<published>2024-09-16T21:18:31Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=4d1ec233ceadfd1326d0643bd215051e71f95b84'/>
<id>urn:sha1:4d1ec233ceadfd1326d0643bd215051e71f95b84</id>
<content type='text'>
</content>
</entry>
<entry>
<title>tor_bytes: Rename new_truncated_for_test to new_incomplete_for_test</title>
<updated>2024-09-12T11:48:38Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2024-09-11T15:51:40Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=5314741adecad01014a069c4f0ed5018e0f6c207'/>
<id>urn:sha1:5314741adecad01014a069c4f0ed5018e0f6c207</id>
<content type='text'>
No semver implications since this wasn't in the last release.
</content>
</entry>
<entry>
<title>tor-bytes: Only report Truncated for errors at the outer level</title>
<updated>2024-09-11T13:19:19Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2024-09-11T13:13:08Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=1632c48a5a2f5744970b841628261d6062881dee'/>
<id>urn:sha1:1632c48a5a2f5744970b841628261d6062881dee</id>
<content type='text'>
This is item 1 from
  https://gitlab.torproject.org/tpo/core/arti/-/issues/1614#note_3074562
and the alternative to item 2 presented in the 2nd half of
  https://gitlab.torproject.org/tpo/core/arti/-/issues/1614#note_3074648

(Item 3 was done earlier, but now we change the behaviour.)

Fixes #1614.
</content>
</entry>
<entry>
<title>tor-bytes: Error: provide and call Error::incomplete_error</title>
<updated>2024-09-11T13:19:19Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2024-09-11T11:32:08Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=12c2fbe076cfcff8d734b24d6aef243d09c64d15'/>
<id>urn:sha1:12c2fbe076cfcff8d734b24d6aef243d09c64d15</id>
<content type='text'>
We introduce the new constructor and call it at the error generation
sites.  But there is still not yet any functional change.

Change the type of Truncated's field to be Sensitive.

The original reason for not doing this no longer applies, since we
don't generally want to open-code construction of this variant.
Conveniently, changing the type means we get to find all the sites
where one *is* constructed and adjust them.

In reader.rs and tor-proto we can just call incomplete_error.

In tor-cell, there's a call site where we previously provided an
underestimate, and where the Reader isn't available.  We adjust that
ad-hoc but this is fine because the error variant will
change.  (relaycell is using a Reader from from_slice.)
</content>
</entry>
<entry>
<title>tor-bytes: Add a Reader constructor for use in tests</title>
<updated>2024-09-11T13:19:19Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2024-09-11T12:04:46Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=98e563764b428e4f1aa87dc34e5fa6b5cf296938'/>
<id>urn:sha1:98e563764b428e4f1aa87dc34e5fa6b5cf296938</id>
<content type='text'>
We could call from_possibly_incomplete_slice in these, but that's
confusing and distracting.

Here we add this constructor, and document it (in terms of the
constructor to come), and change the call sites.

No functional change.  Doing this now will prevent unwanted changes to
test behaviours when we change the behaviour of Readers made by
Reader::from_slice.
</content>
</entry>
</feed>
