mirrors/arti.git/crates/tor-error, branch arti-v1.1.11mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.112023-12-04T16:33:36ZBump patchlevel versions in preparation for release2023-12-04T16:33:36ZNick Mathewsonnickm@torproject.org2023-12-04T16:22:58Zurn:sha1:606905bd1fa3307a77a02463fa863f4c2b7cb890
These crates had backward-compatible changes, and get a patchlevel
bump only:
fs-mistrust
tor-error
tor-config
tor-rtcompat
tor-rtmock
This crate exposes no non-CLI APIs, and gets a patchlevel bump only:
arti
In every crate, change rust-version to 1.70.2023-11-28T16:35:51ZNick Mathewsonnickm@torproject.org2023-11-28T16:35:51Zurn:sha1:1b53c4ca3059fc395c98e2e6d0eb3b58f37c8ec1tor-error: fmt_ending_ok: Permit messages ending in ascii ellipsis2023-11-20T18:22:30ZIan Jacksonijackson@chiark.greenend.org.uk2023-11-20T18:16:36Zurn:sha1:7c272ed251e475dea6a28e45431a2a0bbdb8185f
Tbis will result in "some message ...: the error" which I think is OK.
We don't use a Unicode single-character ellipsis because that
character can be hard to read at font sizes which are otherwise OK for
text, and because use of non-ascii in logfiles and error messages is
unecessary and might cause unnecessary trouble (for example, if the
log messages end up going somewhere which isn't 100% valid UTF-8).
tor-error: fmt_ending_ok: Implement with a direct match2023-11-20T18:22:30ZIan Jacksonijackson@chiark.greenend.org.uk2023-11-20T17:45:23Zurn:sha1:d1e71dc2aa96c98c0c1204a8fe19d6a6fe4c7efc
Possibly at some point in the past, matching a slice directly wasn't
possible. But it is now.
Update patchlevel for crates with nontrivial changes.2023-09-05T16:22:19ZNick Mathewsonnickm@torproject.org2023-09-05T16:22:19Zurn:sha1:e251baa9a77415f3c605ff462a8ac0b3fa37660a
These are:
```
hashx
equix
tor-async-utils
tor-error
tor-config
tor-rtmock
tor-llcrypto
tor-bytes
tor-hscrypto
tor-hspow
tor-cert
tor-linkspec
tor-cell
tor-proto
tor-netdoc
tor-netdir
tor-chanmgr
tor-guardmgr
tor-dirmgr
tor-keymgr
tor-hsclient
tor-hsservice
arti-client
arti
```
Run maint/add_warning to add lint block everywhere2023-08-23T09:34:00ZIan Jacksonijackson@chiark.greenend.org.uk2023-08-22T14:28:12Zurn:sha1:42df88d6bf6dbb460d2e5e1cd4838aafaffbe9actor-error, arti: Bump backtrace to 0.3.68.2023-08-15T15:34:31ZGabriela Moldovangabi@torproject.org2023-08-15T15:34:31Zurn:sha1:31645f4f373e821482b95ee4b9e1bd5856ed76aa
Previously we were using backtrace 0.3.39, which has a [bug] that causes
it to segault in some circumstances. I experienced this bug while trying
to fix the minimal-versions build in !1508.
[bug]: https://github.com/rust-lang/backtrace-rs/issues/267
tor-error: Remove KeystoreFsPermissions variant.2023-08-08T15:46:20ZGabriela Moldovangabi@torproject.org2023-08-08T15:40:28Zurn:sha1:5d0fb5177f50f87132cbc7d0a95c6f63d4de51d7
According to the `ErrorKind` lumping guidelines, `KeystoreFsPermissions`
should be lumped with `FsPermissions`: they represent the same type
of error, and their "location" is the same ("Host").
Prompted by https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/1315#note_2916455
Run add_warnings on all files.2023-08-04T11:45:04ZNick Mathewsonnickm@torproject.org2023-08-04T11:45:04Zurn:sha1:cec6d0ce33b4b5cebbce57f55faec83397e9c953Merge branch 'bump_versions_117' into 'main'2023-08-01T15:40:26ZNick Mathewsonnickm@torproject.org2023-08-01T15:40:26Zurn:sha1:3422169ff4158e56764e2f3c3d2fea31e8031fcd
Vesion bumps for 1.1.7.
See merge request tpo/core/arti!1458