summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
...
* | CHANGELOG: Fix another sentenceNick Mathewson2022-04-011-2/+2
| |
* | CHANGELOG: rephrase a sentence.Nick Mathewson2022-04-011-3/+3
| |
* | Merge branch 'upgrade_pre_020' into 'main'Nick Mathewson2022-04-014-33/+34
|\ \ | | | | | | | | | | | | Run cargo upgrade/update in preparation for 0.2.0 See merge request tpo/core/arti!444
| * | Upgrade async-broadcast => 0.4.0Nick Mathewson2022-04-011-1/+1
| | |
| * | Final "cargo update" before 0.2.0Nick Mathewson2022-04-011-30/+31
| | |
| * | Upgrade rlimit -> 0.8.0Nick Mathewson2022-04-012-2/+2
| | |
* | | CHANGELOG: spelling fixesNick Mathewson2022-04-011-2/+2
| | |
* | | First attempt at a changelog for 0.2.0Nick Mathewson2022-04-011-18/+122
| | |
* | | Merge branch 'dir-munger-v2' into 'main'Nick Mathewson2022-03-3114-8/+391
|\ \ \ | |/ / |/| | | | | | | | | | | | | | Implement a directory munger to simulate pathological cases in arti-testing (v2) Closes #397 See merge request tpo/core/arti!442
| * | Re-order attributes so that we can build with Rust 1.53.Nick Mathewson2022-03-315-15/+15
| | |
| * | Typo fix.Ian Jackson2022-03-311-1/+1
| | |
| * | Directory filtering in arti-testing.Nick Mathewson2022-03-315-1/+229
| | | | | | | | | | | | | | | | | | | | | | | | | | | This feature allows us to detect different failing cases for arti#329 that would otherwise be hard to induce. It works by filtering consensus directory objects and/or microdescriptor objects before introducing them to the directory manager. Closes #397.
| * | tor-netdoc: Conditionally expose document fields.Nick Mathewson2022-03-318-0/+119
| | | | | | | | | | | | | | | | | | | | | | | | This commit uses the `visibility` and `visible` crates to conditionally make certain structs and their fields public (respectively). This is incredibly dangerous to use for anything besides testing, and I've tried to write the documentation for the feature accordingly.
| * | tor-checkable: add experimental api for exposing wrapped objects.Nick Mathewson2022-03-312-0/+38
| | |
| * | Reformat tor-checkable/Cargo.tomlNick Mathewson2022-03-311-6/+4
| | |
* | | Merge branch 'retry_tuning_1' into 'main'Nick Mathewson2022-03-314-16/+44
|\ \ \ | | | | | | | | | | | | | | | | Minor retry tuning to improve behavior under failing conditions. See merge request tpo/core/arti!439
| * | | dirmgr: Use a different idiom in retry loopNick Mathewson2022-03-311-3/+2
| | | | | | | | | | | | | | | | | | | | Replace the next delay field immediately rather than taking it and _then_ setting it. This way, it's never in an incorrect state.
| * | | Use a lower default for max_retries.Nick Mathewson2022-03-302-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The older default seems (experimentally) to be ridiculously high. Generally, if we can't build a circuit within a handful attempts, that circuit has already timed out... unless there is a fast-failure condition, in which case we're just hammering the network (or our view of it.) Found with `arti-testing` for #329.
| * | | circmgr: limit circuit attempts when launch_parallelism > 1.Nick Mathewson2022-03-301-1/+21
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Previously, if we had launch_parallelism > 1, and we were willing to retry building a circuit max_retries times, then we'd launch up to max_retries * launch_parallelism circuits before giving up. Ouch! With this patch, we try to keep the total number of circuits planned and attempted to the actual max_retries limit. Part of #329; found with arti-testing.
| * | | dirmgr: fix bugs in algorithm for retrying downloadsNick Mathewson2022-03-301-13/+22
| |/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | The previous algorithm had two flaws: * It would wait even after the final attempt, when there were no more retries to do. * It would fail to wait between attempts if an error occurred. This refactoring fixes both of these issues, and adds some comments.
* | | Merge branch 'typos' into 'main'Ian Jackson2022-03-311-1/+1
|\ \ \ | |/ / |/| | | | | | | | Fix typo See merge request tpo/core/arti!441
| * | Fix typoDimitris Apostolou2022-03-301-1/+1
|/ /
* | README.md for arti-testing.Nick Mathewson2022-03-301-0/+53
| |
* | Merge branch 'fallback_status_v2' into 'main'Ian Jackson2022-03-3027-331/+1212
|\ \ | | | | | | | | | | | | | | | | | | Refactor FallbackDir handling and implement a retry-after-delay mechanism. Closes #406 and #220 See merge request tpo/core/arti!433
| * | Merge branch 'fallback_status_v2' into mainIan Jackson2022-03-3027-331/+1212
|/| | | | | | | | | | | | | | | | | Manual merge for just this branch as per https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/433#note_2791982 https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/433#note_2791993
| * | Run cargo fmt one more time for good measure.Nick Mathewson2022-03-301-2/+2
| | |
| * | Use derive_more to derive AsRef.Nick Mathewson2022-03-303-12/+5
| | |
| * | Reformat tor-guardmgr/Cargo.toml.Nick Mathewson2022-03-301-18/+18
| | |
| * | Reformat several Cargo.toml files with 100-char-wide lines.Nick Mathewson2022-03-303-27/+8
| | |
| * | Fix some Rustdoc links.Nick Mathewson2022-03-304-5/+5
| | |
| * | Refactor FirstHopId into type-differentiated formNick Mathewson2022-03-309-185/+348
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The FirstHopId type now records an enum that stores whether the hop is a guard or a fallback. This change addresses concerns about remembering to check the type or source of an Id before passing it down to the FallbackState or GuardSet. Making this change required an API change, so that dirmgr can report success/failure status without actually knowing whether it's using a fallback or a guard.
| * | Rename Guard=>FirstHop, GuardId=>FirstHopIdNick Mathewson2022-03-308-77/+91
| | | | | | | | | | | | | | | This is preparation for having separate GuardId and FirstHopId types that distinguish which back-end they index.
| * | FallbackState: Use itertools::merge_join_by.Nick Mathewson2022-03-301-100/+8
| | | | | | | | | | | | | | | This replaces a hand-coded replacement that was probably a little less efficient.
| * | Fold fallback::Status::reset() into its (only) caller.Nick Mathewson2022-03-301-7/+2
| | |
| * | Rename FallbackState::lookup_mut => get_mut.Nick Mathewson2022-03-301-12/+12
| | |
| * | Rename FallbackSet => FallbackState.Nick Mathewson2022-03-303-15/+15
| | |
| * | DirPathBuilder::pick_path: re-order match cases for clarity.Nick Mathewson2022-03-301-16/+18
| | |
| * | Refactor select_guard_with_expand to use match and log errors.Nick Mathewson2022-03-301-10/+13
| | |
| * | ListKind: Use an exhaustive match to future-proof.Nick Mathewson2022-03-301-1/+4
| | |
| * | Clarify documentation about GuardUsable constructorsNick Mathewson2022-03-301-4/+10
| | |
| * | Add a TODO about an unslightly type.Nick Mathewson2022-03-301-0/+2
| | |
| * | Clean up a rustdoc linkIan Jackson2022-03-301-1/+1
| | |
| * | guardmgr::fallback::set: basic unit tests.Nick Mathewson2022-03-301-10/+190
| | |
| * | Rename ExternalFailure => ExternalActivity.Nick Mathewson2022-03-304-18/+17
| | |
| * | Replace the fallback directories when they change in the config.Nick Mathewson2022-03-303-0/+127
| | | | | | | | | | | | | | | | | | The code here uses a new iterator type, since I couldn't find one of these on crates.io. I tried writing the code without it, but it was harder to follow and test.
| * | Add status tracking to FallbackDir.Nick Mathewson2022-03-308-25/+286
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We do this by creating a new FallbackSet type that includes status information, and updating the GuardMgr APIs to record success and failure about it when appropriate. We can use this to mark FallbackDirs retriable (or not). With this change, FallbackDir is now stored internally as a Guard in the GuardMgr crate. That's fine: the FallbackDir type really only matters for configuration.
| * | Implement Ord for Ed25519Identity.Nick Mathewson2022-03-302-1/+2
| | |
| * | Update semver_status from recent round of movement.Nick Mathewson2022-03-301-0/+4
| | |
| * | dirmgr: do not pass fallbacks to the CircMgr.Nick Mathewson2022-03-301-6/+1
| | | | | | | | | | | | | | | | | | | | | This is the final step in allowing the CircMgr to use the GuardMgr's view of the fallbacks. Compilation is restored and tests pass.
| * | circmgr: Use guard-manager's view of the fallbacks when possible.Nick Mathewson2022-03-304-14/+49
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | If we're building a path with the guard manager involved, we now ask the guard manager to pick our first hop no matter what. We only pick from the fallback list ourselves if we're using the API with no guard manager. This causes some follow-on changes where we have to remember an OwnedChanTarget object in a TorPath we've built, and where we gain the ability to say we're building a path "from nothing extra at all." Those are all internal to the crate, though. Closes #220, by making sure that we use our guards to get a fresh netdir (if we can) before falling back to any fallbacks, even if our consensus is old. Compilation should be fixed in the next commit.
generated by cgit v1.2.3 (git 2.46.0) at 2026-08-27 17:35:33 +0000