vincenzopalazzo
/
arti
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
arti/crates/tor-error/Cargo.toml

43 lines
1.2 KiB
TOML
Raw Normal View History

tor-error: Skeleton for new crate As per doc/Errors.md. Currently there are no error kinds. Some will be added as we go along.
2022-01-12 17:16:18 +00:00
[package]
name = "tor-error"
Increment patchlevel versions of crates with minor changes 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 ```
2023-08-01 15:57:55 +01:00
version = "0.5.3"
tor-error: Skeleton for new crate As per doc/Errors.md. Currently there are no error kinds. Some will be added as we go along.
2022-01-12 17:16:18 +00:00
authors = ["Ian Jackson <iwj@torproject.org>"]
Bump every crate's edition to 2021. This is an automated change made with a perl one-liner and verified with grep -L and grep -l. Some warnings are introduced with this change; they will be removed in subsequent commits. See arti#208 for older discussion on this issue.
2022-04-25 17:19:02 +01:00
edition = "2021"
Increment MSRV to 1.65 in every crate.
2023-04-11 20:31:12 +01:00
rust-version = "1.65"
tor-error: Skeleton for new crate As per doc/Errors.md. Currently there are no error kinds. Some will be added as we go along.
2022-01-12 17:16:18 +00:00
license = "MIT OR Apache-2.0"
homepage = "https://gitlab.torproject.org/tpo/core/arti/-/wikis/home"
Fix grammar and typos
2022-04-23 12:51:44 +01:00
description = "Provides the unified type-erased error type returned by many (esp. high-level) Tor APIs."
Reformat tor-error/Cargo.toml
2022-03-31 17:34:07 +01:00
keywords = ["tor", "arti"]
repository = "https://gitlab.torproject.org/tpo/core/arti.git/"
Move tor-error crate to the "rust-patterns" category. There is no "tor" category; crates.io warned about this.
2022-05-27 19:02:17 +01:00
categories = ["rust-patterns"]
tor-error: Skeleton for new crate As per doc/Errors.md. Currently there are no error kinds. Some will be added as we go along.
2022-01-12 17:16:18 +00:00
tor-error: Introduce InternalError as a type and a kind This can contain a backtrace, which will be printed.
2022-01-21 14:57:09 +00:00
[features]
default = ["backtrace"]
Run "fixup features" in preparation for a release.
2023-08-01 13:32:20 +01:00
full = ["backtrace", "tracing", "retry-error/full"]
Run fixup-features _with_ annotations. This litters our Cargo.toml files with "XXX" entries that we should fix.
2023-05-15 13:37:35 +01:00
Revise all XXXXs from fixup-features
2023-05-15 16:00:28 +01:00
experimental = ["experimental-api", "rpc"]
experimental-api = ["rpc", "__is_experimental"]
Run fixup-features _with_ annotations. This litters our Cargo.toml files with "XXX" entries that we should fix.
2023-05-15 13:37:35 +01:00
Revise all XXXXs from fixup-features
2023-05-15 16:00:28 +01:00
rpc = ["__is_experimental"]
event_report: assert correctness of format ending (Also, document that this static assertion is the reason why you are seeing a confusing error message.)
2023-07-07 13:47:49 +01:00
tracing = ["dep:tracing", "static_assertions"]
Revise all XXXXs from fixup-features
2023-05-15 16:00:28 +01:00
__is_experimental = []
tor-error: Introduce InternalError as a type and a kind This can contain a backtrace, which will be printed.
2022-01-21 14:57:09 +00:00
tor-error: Skeleton for new crate As per doc/Errors.md. Currently there are no error kinds. Some will be added as we go along.
2022-01-12 17:16:18 +00:00
[dependencies]
tor-error, arti: Bump backtrace to 0.3.68. 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
2023-08-15 16:34:31 +01:00
backtrace = { version = "0.3.68", optional = true }
Require derive_more 0.99.3 0.99.[012] have a bug https://github.com/JelteF/derive_more/issues/114 which makes the Deref derive for bridgedesc::StateGuard not work and therefore breaks minimal-versions CI. It seems simpler to require the newer version everywhere.
2022-11-01 10:59:37 +00:00
derive_more = "0.99.3"
spawn errors: impl HasKind for futures::SpawnError This needs two kinds. We have decided to treat a non-shutdown SpawnError as "unexplained" rather than as an InternalError. There are many crates whose From<futures::task::SpawnError> for Error erroneously treat it as an internal error. We will fix them in a moment.
2022-01-21 15:45:41 +00:00
futures = "0.3"
tor-error: Add a new RetryTime type and related trait.
2022-03-31 15:43:46 +01:00
once_cell = "1"
tor-error: tracing module: Use macro to generate macros This abolishes some quintuplication. The output is identical except that: * The syntax display in the rustdoc output for the resulting macros seems to have somewhat less whitepsace. * The whimsical error messages in the examples are all identical. Ah well.
2023-07-07 17:43:26 +01:00
paste = "1"
Update minor versions on crates that have had breaking changes 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.
2023-08-01 15:51:25 +01:00
retry-error = { path = "../retry-error", version = "0.5.0" } # WRONG should be 0.4.3
event_report: assert correctness of format ending (Also, document that this static assertion is the reason why you are seeing a confusing error message.)
2023-07-07 13:47:49 +01:00
static_assertions = { version = "1", optional = true }
Upgrade to strum 0.25.
2023-06-21 14:12:36 +01:00
strum = { version = "0.25", features = ["derive"] }
spawn errors: impl HasKind for futures::SpawnError This needs two kinds. We have decided to treat a non-shutdown SpawnError as "unexplained" rather than as an InternalError. There are many crates whose From<futures::task::SpawnError> for Error erroneously treat it as an internal error. We will fix them in a moment.
2022-01-21 15:45:41 +00:00
thiserror = "1"
tor-error: Add optional tracing support The main contribution here is a set of convenience macros for logging error `Report`s. Notably, this macros always logs `Internal` and `BadAspiUsage` errors at `WARN`, unless they are already at `ERROR` or more. This is a little tricky because `tracing::event!()` requires its Level argument to be a constant.
2023-07-06 18:48:01 +01:00
tracing = { version = "0.1.36", optional = true }
tor-error: Skeleton for new crate As per doc/Errors.md. Currently there are no error kinds. Some will be added as we go along.
2022-01-12 17:16:18 +00:00
[dev-dependencies]
enable doc_auto_cfg feature on every crate when documenting for docs.rs
2022-08-17 20:13:13 +01:00
[package.metadata.docs.rs]
all-features = true
rustdoc-args = ["--cfg", "docsrs"]