summaryrefslogtreecommitdiff
path: root/crates/tor-error
Commit message (Collapse)AuthorAgeFilesLines
* Bump the patch version of every crate that had API additionsNick Mathewson2023-02-011-1/+1
| | | | | | These crates had API or behavior changes that may affect downstream crates. Fortunately, they're all version 0.x, and don't need minor bumps for this.
* Allow clippy::unchecked_duration_subtraction in testsNick Mathewson2023-01-273-0/+3
| | | | | This panics on error, and we're fine with a panic on misbehavior in tests.
* Disable clippy::unlinlined-format-argsNick Mathewson2023-01-271-0/+1
| | | | | | | | This warning kind of snuck up on us! (See #748) For now, let's disable it. (I've cleaned it up in a couple of examples, since those are meant to be more idiomatic and user-facing.) Closes #748.
* Fix typosDimitris Apostolou2023-01-071-1/+1
|
* Merge branch 'test-lints' into 'main'eta2023-01-062-0/+18
|\ | | | | | | | | Add test lint blocks to all "mod test" See merge request tpo/core/arti!937
| * test lint blocks: Add many many automaticallyIan Jackson2022-12-122-0/+18
| | | | | | | | | | This is precisely the result of running the rune in maint/adhoc-add-lint-blocks.
* | doc: consistent summary line for the READMEsEmil Engler2022-12-201-1/+1
| | | | | | | | | | This commit introduces a consistency to the summary line of all README.md files in each and every crate.
* | tor-error: tests: Add a test case for Report and Bug wrappingIan Jackson2022-12-151-0/+11
| |
* | tor-error: Provide ErrorReport extension trait with .report() methodIan Jackson2022-12-121-0/+32
| |
* | tor_error: Promote internal StdError alias to reportIan Jackson2022-12-121-5/+5
|/ | | | | The std::error::Error repetition was getting rather repetitively repetitious, and is about to get more so.
* Remove semver.md files now that 1.1.0 is released.Nick Mathewson2022-11-301-2/+0
|
* Bump the minor version of every crate.Nick Mathewson2022-11-301-1/+1
| | | | | We made this job easy this time around: by incrementing our MSRV, we have forced ourselves to do at least a minor bump everywhere.
* Rename LocalLoginFailed to ExternalToolFailed.Nick Mathewson2022-11-291-2/+2
|
* Document better what LocalProtocolViolation does not cover.Nick Mathewson2022-11-291-1/+4
|
* ptmgr: Fill in some error-related code; resolve TODOs.Nick Mathewson2022-11-281-0/+5
|
* bump rust-version to 1.60 in every crate.Nick Mathewson2022-11-101-1/+1
|
* Use ErrorKind::TorAccessFailed for misbehaving bridgesIan Jackson2022-11-081-2/+3
| | | | (Use semantic linefeed for the doc comment.)
* Run add_warnings.Nick Mathewson2022-11-031-0/+1
|
* Require derive_more 0.99.3Ian Jackson2022-11-031-1/+1
| | | | | | | | 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.
* tor-error: Tidy up use of thiserror::ErrorIan Jackson2022-10-241-2/+4
| | | | | | | | 1. Import it, as we do elsewhere, and use that import. 2. Use thiserror to generate the Display impl, rather than derive_more, as we do for errors elsewhere. (tor_error still needs derive_more::Display for ErrorKind.)
* tor-error: Rename truncated module to miscIan Jackson2022-10-242-3/+3
| | | | | This has no external API change, but makes space for other miscellaneous errors to arrive later.
* tor-error: make HasRetryTime object-safeIan Jackson2022-10-212-1/+2
| | | | | | | | We could in the future provide a version of abs_retry_time which took an &dyn closure if that turns out to be wanted. I think this isn't a semver break because trait implementors are allowed to relax bounds.
* cargo fmt to remove blank linesIan Jackson2022-10-121-1/+0
| | | | | | | Apparently cargo fmt doesn't like these, which my perl rune didn't delete. This commit is precisely the result of `cargo fmt`.
* Replace all README copies in src/lib.rs with includesIan Jackson2022-10-121-7/+1
| | | | | | | | The feature we want is `#[doc = include_str!("README.md")]`, which is stable since 1.54 and our MSRV is now 1.56. This commit is precisely the result of the following Perl rune: perl -i~ -0777 -pe 's{(^//!(?!.*\@\@).*\n)+}{#![doc = include_str!("../README.md")]\n}m' crates/*/src/lib.rs
* Allow "clippy::single_char_pattern" in tests.Ian Jackson2022-10-121-0/+1
| | | | | | | This lint exists for perf reasons, and this is rarely relevant in tests. Using double quoted str is generally cognitively less burdensome.
* Merge branch 'bridge-parse' into 'main'Ian Jackson2022-10-031-1/+0
|\ | | | | | | | | Parse (and format) bridge lines See merge request tpo/core/arti!745
| * tor-error::internal: Remove a redundant suppressionIan Jackson2022-09-301-1/+0
| | | | | | | | Spotted this in passing.
* | Merge branch 'socks_client' into 'main'Nick Mathewson2022-10-032-0/+9
|\ \ | | | | | | | | | | | | Implement a SOCKS client handshake See merge request tpo/core/arti!746
| * | New ErrorKind::LocalProtocolFailed.Nick Mathewson2022-09-272-0/+9
| |/ | | | | | | | | This type is by analogy to `RemoteProtocolFailed`; we'll use it for cases when the Socks proxy refuses to talk to us.
* / Bump crates that have had no API changes.Nick Mathewson2022-10-031-1/+1
|/
* force no inlining on internal_macro_testtrinity-1686a2022-09-091-0/+1
| | | | it may fix this test when running in release, where the function gets inlined, so its name does not appear in the backtrace
* Add a dbg!() to diagnose #570.Nick Mathewson2022-09-081-0/+9
| | | | | This won't fix anything, but it will let us see what the backtrace looks like when it fails.
* Update patch-versions on crates without API changes.Nick Mathewson2022-09-011-1/+1
| | | | | | | Since our last round of releases, these crates have had either trivial changes, or changes that did not affect their APIs. Therefore we are bumping their versions, but not changing which versions of them other crates depend on.
* enable doc_auto_cfg feature on every crate when documenting for docs.rstrinity-1686a2022-08-242-0/+4
|
* Bump crate and dependency versions.Nick Mathewson2022-06-241-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | These were done with the following commands: ``` cargo set-version -p tor-basic-utils --bump patch cargo set-version -p fs-mistrust --bump minor cargo set-version -p tor-error --bump patch cargo set-version -p tor-config --bump patch cargo set-version -p tor-units --bump patch cargo set-version -p tor-rtcompat --bump minor cargo set-version -p tor-llcrypto --bump patch cargo set-version -p tor-bytes --bump minor cargo set-version -p tor-socksproto --bump minor cargo set-version -p tor-cert --bump minor cargo set-version -p tor-cell --bump minor cargo set-version -p tor-proto --bump minor cargo set-version -p tor-netdoc --bump patch cargo set-version -p tor-netdir --bump minor cargo set-version -p tor-persist --bump patch cargo set-version -p tor-chanmgr --bump minor cargo set-version -p tor-guardmgr --bump minor cargo set-version -p tor-circmgr --bump patch cargo set-version -p tor-dirclient --bump patch cargo set-version -p tor-dirmgr --bump minor cargo set-version -p arti-client --bump patch cargo set-version -p arti --bump minor cargo set-version -p arti-bench --bump minor cargo set-version -p arti-testing --bump minor ```
* Run maint/add_warning crates/*/src/{lib,main}.rsIan Jackson2022-06-231-0/+3
| | | | Update all lint blocks
* tor-error: Fix a broken intra-doc linkIan Jackson2022-06-101-1/+2
| | | | I didn't spot this in review amongst the other messages from Nightly.
* try to differentiate transient from nontransient errortrinity-1686a2022-06-081-1/+8
|
* lints: Make lint blocks consistentIan Jackson2022-05-311-0/+1
| | | | The remaining consequences of running add_warning
* lints: Add let_unit_value allow to all cratesIan Jackson2022-05-311-0/+1
| | | | | From running add_warning, with manual picking of the right hunks/lines.
* lints: Add lint block delimiters to every crateIan Jackson2022-05-311-0/+2
| | | | | | This was the result of: maint/add_warning crates/*/src/{lib,main}.rs and then manually curating the results.
* Move tor-error crate to the "rust-patterns" category.Nick Mathewson2022-05-271-1/+1
| | | | There is no "tor" category; crates.io warned about this.
* Semantic version changes for Arti 0.4.0 releaseNick Mathewson2022-05-271-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | I followed the following procedure to make these changes: * I used maint/changed_crates to find out which crates had changed since 0.3.0. * I used grep and maint/list_crates to sort those crates in topological (dependency) order. * I looked through semver_status to find which crates were listed as having semver-relevant changes (new APIs and breaking changes). * I scanned through the git logs of the crates with no semver-relevant changes listed to confirm that, indeed, they had no changes. For those crates, I incremented their patch-level version _without_ changing the version that other crates depend on. * I scanned through the git logs of the crates with no semver-relevant changes listed to confirm that, indeed, they had no obvious breaking changes. * I treated all crates that depend on `arti` and/or `arti-client` as having breaking changes. * I identified crates that depend on crates that have changed, even if they have not changed themselves, and identified them as having a non-breaking change. * For all of the crates, I used `cargo set-version -p $CRATE --bump $STATUS` (where `STATUS` is `patch` or `minor`) to update the versions, and the depended-upon versions.
* Placate rustfmtIan Jackson2022-05-171-5/+1
| | | | I found the previous layout *much* better. Ah well.
* Do backtrace string matching test only on some platforms.Ian Jackson2022-05-171-0/+19
| | | | | | "Fixes" #455 by suppressing the test. This is !509 redux.
* Revert "Merge branch 'backtrace' into 'main'"eta2022-05-161-6/+0
| | | This reverts merge request !509
* Do backtrace string matching test only on LinuxIan Jackson2022-05-161-0/+6
| | | | "Fixes" #455 by suppressing the test.
* Merge branch 'use-fs-mistrust'Nick Mathewson2022-05-091-0/+9
|\
| * Add new FsPermissions ErrorKind.Nick Mathewson2022-05-091-0/+9
| |
* | Bump the version of every* crate to 0.3.0Nick Mathewson2022-05-061-1/+1
|/ | | | * Except for safelog and fs-mistrust, which are new.