<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/arti/Cargo.toml, branch arti-v1.1.7</title>
<subtitle>mirror of https://gitlab.torproject.org/tpo/core/arti
</subtitle>
<id>http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.7</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.7'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2023-08-01T14:57:55Z</updated>
<entry>
<title>Increment patchlevel versions of crates with minor changes</title>
<updated>2023-08-01T14:57:55Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-08-01T14:57:55Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=3acdf102c705314aec63679e97240bb7d981d1c8'/>
<id>urn:sha1:3acdf102c705314aec63679e97240bb7d981d1c8</id>
<content type='text'>
These crates are at version 0.x.y, so we don't need to distinguish
new-feature changes from other changes:

```
tor-basic-utils
fs-mistrust
tor-error
tor-geoip
tor-checkable
tor-linkspec
tor-netdoc
tor-netdir
tor-persist
tor-ptmgr
tor-hsservice
```

This crate has a breaking change, but only when the semver-breaking
feature `experimental-api` is enabled:

```
tor-config
```

This crate is at version 1.x.y, but has no new public APIs, and
therefore does not need a minor version bump:

```
arti
```
</content>
</entry>
<entry>
<title>Update minor versions on crates that have had breaking changes</title>
<updated>2023-08-01T14:51:25Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-08-01T14:51:25Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=6f2ae5960393b64c1d7615d2d523e050d3bebe5a'/>
<id>urn:sha1:6f2ae5960393b64c1d7615d2d523e050d3bebe5a</id>
<content type='text'>
These crates had first-order breaking changes:

```
retry-error
tor-keymgr
tor-proto
tor-hsclient
tor-rtmock
```

Additionally, these broke because they re-exposed RetryError:

```
tor-circmgr
```

Additionally, these broke because they may re-expose something from
tor-proto:

```
    arti-client
    tor-chanmgr
    tor-dirclient
    tor-dirmgr
    tor-guardmgr
```

Additionally, these broke for other fiddly reasons:

`tor-ptmgr` implements traits from tor-chanmgr, which has a breaking
change above.

`arti-hyper` exposes types from arti-client in its API.
</content>
</entry>
<entry>
<title>Bump requirement to rlimit 0.10.1</title>
<updated>2023-07-20T12:15:38Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-07-20T12:15:38Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=3b7400621cda1cedafcaaeb340ae92912ec9f919'/>
<id>urn:sha1:3b7400621cda1cedafcaaeb340ae92912ec9f919</id>
<content type='text'>
There was a bug in 0.10.0 that broke MacOS.

Part of #963.
</content>
</entry>
<entry>
<title>Upgrade to latest rlimit.</title>
<updated>2023-07-17T14:12:08Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-07-17T14:12:08Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=1b3206ca0bad3211f070c269daa658bdf010d679'/>
<id>urn:sha1:1b3206ca0bad3211f070c269daa658bdf010d679</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Merge branch 'feat' into 'main'</title>
<updated>2023-07-07T19:28:05Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-07-07T19:28:05Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=ba3876b22acc60a09a877ba2fe8185c2d994e81e'/>
<id>urn:sha1:ba3876b22acc60a09a877ba2fe8185c2d994e81e</id>
<content type='text'>
arti: Build with HS client support by default

Closes #948

See merge request tpo/core/arti!1382</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>arti: Build with HS client support by default</title>
<updated>2023-07-07T11:54:08Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2023-07-07T11:53:27Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=4c0935e13a1469e6830c4c135b8e373579edbf29'/>
<id>urn:sha1:4c0935e13a1469e6830c4c135b8e373579edbf29</id>
<content type='text'>
Fixes #948
</content>
</entry>
<entry>
<title>arti Cargo.tomL: wrap default features list</title>
<updated>2023-07-07T11:52:05Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2023-07-07T11:52:05Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=61344f68a56dfe380b08f47000c3c8d3294bef00'/>
<id>urn:sha1:61344f68a56dfe380b08f47000c3c8d3294bef00</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Merge branch 'log_precision' into 'main'</title>
<updated>2023-07-06T14:37:49Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-07-06T14:37:49Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=36a92e44d9a36afa1c9b88caa1505e38ae5d5cc5'/>
<id>urn:sha1:36a92e44d9a36afa1c9b88caa1505e38ae5d5cc5</id>
<content type='text'>
arti: Add a `logging.time_granularity` option with 1s default.

Closes #551

See merge request tpo/core/arti!1376</content>
</entry>
<entry>
<title>arti: Add a `logging.time_granularity` option with 1s default.</title>
<updated>2023-07-06T13:44:09Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-07-05T17:09:20Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=512064cc19d24c111495150f8cf424b89395847b'/>
<id>urn:sha1:512064cc19d24c111495150f8cf424b89395847b</id>
<content type='text'>
This lets us provide less information in our logs: in particular, it
lets us avoid logging with microsecond precision.

Closes #551.
</content>
</entry>
</feed>
