summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
...
| * | | tor-hsservice: ipt_mgr: Adjust API for mock RNGIan Jackson2023-10-161-4/+4
| | | | | | | | | | | | | | | | | | | | We're want to be able to return a mutable borrow of a field in the mock state. This means we must make `Rng` a GAT.
| * | | tor-hsservice: Narrow some dead code allowsIan Jackson2023-10-166-2/+7
| | | |
| * | | tor-hsservice: timeout_track: Change semantics to do what's neededIan Jackson2023-10-161-32/+68
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The key point is this: +//! I.e., the timeout tracker tells you when (in the future) +//! any of the comparisons you have made, might produce different answers. +//! So, that can be used to know how long to sleep for when waiting for timeout(s). That's how the code in ipt_mgr.rs uses this. Without this change, things go wrong in the following case: we've got at least one good IPT, but not quite enough, and the others are taking too long. Ie, the timeout for "we should publish" is in the past. We decide to publish (correctly) but this *past* timeout should be disregarded. Disregarding past timeouts is correct if the code which is making the comparisons acts on the timeout when it occurs.
| * | | tor-hsservice: timeout_track: Provided shortest() for all trackersIan Jackson2023-10-161-0/+25
| | | |
| * | | tor-hsservice: timeout_track: Mark some unused variablesIan Jackson2023-10-161-2/+2
| | | |
| * | | tor-hsservice: timeout_track: Add a dead code allowIan Jackson2023-10-161-0/+1
| | | | | | | | | | | | | | | | For the same reason as the allow(unreachable_pub).
| * | | tor-hsservice: ipt_mgr: Improve waiting publish messageIan Jackson2023-10-161-10/+18
| | | | | | | | | | | | | | | | | | | | | | | | This involves plumbing the duration through. Also it involved breaking out the multiplication by two into an addition, since if we were to change the factor we'd want to print the scaled value.
| * | | tor-hsservice: ipt_mgr: Add several debug/trace messagesIan Jackson2023-10-161-4/+22
| | | | | | | | | | | | | | | | | | | | We're going to improve the "establishing_very_recently" one in a moment.
| * | | tor-hsservice: ipt_mgr: Fix a message styleIan Jackson2023-10-161-1/+2
| | | | | | | | | | | | | | | | | | | | Add a colon. This is going to be the style for our trace and debug output.
| * | | tor-hsservice: ipt_mgr: Avoid looping with a zero timeoutIan Jackson2023-10-161-0/+3
| | | | | | | | | | | | | | | | | | | | If the time we're supposed to wait is zero, something has gone wrong. We'd probably just go round again and loop indefinitely.
| * | | tor-hsservice: ipt_mgr: Apply a limit to loopingIan Jackson2023-10-161-0/+10
| | | | | | | | | | | | | | | | This is a backstop to stop us just spinning. Instead, we crash.
| * | | tor-hsservice: ipt_mgr: Actually wait for (fast-ish) IPTsIan Jackson2023-10-161-0/+4
| | | | | | | | | | | | | | | | | | | | We never called the `started_establishing_very_recently` machinery. Do so.
| * | | tor-hsservice: ipt_mgr: Remove vestigial expiry time code (2)Ian Jackson2023-10-161-10/+1
| | | | | | | | | | | | | | | | | | | | lifetime is passed in the IptSet and doesn't want to be made absolute here.
| * | | tor-hsservice: ipt_mgr: Remove vestigial expiry time codeIan Jackson2023-10-161-4/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | This calculation is now done elsewhere: the addition of IPT_PUBLISH_EXPIRY_SLOP happens in IptSet::note_publication_attempt and the storage in the manager's data structure is done by IptManager::import_new_expiry_times.
| * | | tor-hsservice: ipt_mgr: Mark an argument as unusedIan Jackson2023-10-161-1/+1
| | | |
| * | | tor-hsservice: Better debug impl for IptLocalIdIan Jackson2023-10-161-1/+5
| | | |
| * | | tor-rtmock: MockRuntime::test_with_various: Print what we're doingIan Jackson2023-10-161-1/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Without this, it can be a bit confusing since you just get the output (if any) of all the test runs, concatenated. It seems sensible to put the framing centrally. And, this would be helpful if the test fails for any reason.
| * | | tor-rtmock: MockExecutor: Provide n_tasks accessorIan Jackson2023-10-162-0/+16
|/ / /
* | | Merge branch 'by_type_remove' into 'main'Nick Mathewson2023-10-161-10/+0
|\ \ \ | | | | | | | | | | | | | | | | tor-cell: Remove unused by_type() function See merge request tpo/core/arti!1664
| * | | tor-cell: Remove unused by_type() functionNeel Chauhan2023-10-131-10/+0
| | |/ | |/|
* | | Merge branch 'fix-after-script-usage' into 'main'Nick Mathewson2023-10-141-7/+2
|\ \ \ | |/ / |/| | | | | | | | | | | | | | move usage of ./maint/preserve out of after_script Closes #1061 See merge request tpo/core/arti!1663
| * | remove artifact generation from rust-latest-test-all-featurestrinity-1686a2023-10-131-5/+0
| | |
| * | move usage of ./maint/preserve out of after_scripttrinity-1686a2023-10-131-3/+3
|/ /
* | Merge branch 'todos_proto' into 'main'Nick Mathewson2023-10-1212-129/+205
|\ \ | | | | | | | | | | | | tor-proto: Resolve a few TODO HSS entries. See merge request tpo/core/arti!1658
| * | Add downgrade-dependencies exceptions to make tor-proto build right.Nick Mathewson2023-10-121-1/+3
| | |
| * | proto::stream::incoming: Use bit-array representation for command listNick Mathewson2023-10-123-7/+125
| | | | | | | | | | | | | | | This should be smaller and faster than vec, and save some allocations. It could also avoid a tiny sidechannel.
| * | tor-proto: remove a now-unneeded allow in stream::incomingNick Mathewson2023-10-121-2/+0
| | |
| * | hss: use Arc to avoid copying on k_hss_ntor.Nick Mathewson2023-10-123-15/+8
| | | | | | | | | | | | (We try to avoid making tons and tons of copies of a secret key.)
| * | Remove the (fairly bogus) HsNtorServiceInput type.Nick Mathewson2023-10-125-103/+66
| | | | | | | | | | | | This will let avoid some copying inside our HSS code.
| * | proto: Remove a TODO about merging two functions.Nick Mathewson2023-10-121-2/+0
| | | | | | | | | | | | | | | There is some similarity, but there's not really a logical way to combine the two that actually results in less, clearer code.
| * | Lower and downgrade a TODO about StreamID and NonZeroU16.Nick Mathewson2023-10-122-2/+6
| | |
* | | Merge branch 'proto' into 'main'Alexander Færøy2023-10-121-0/+2
|\ \ \ | |/ / |/| | | | | | | | tor-proto: Add a FIXME about an allow See merge request tpo/core/arti!1657
| * | tor-proto: Add a FIXME about an allowIan Jackson2023-10-121-0/+2
|/ /
* | Merge branch 'bug1051' into 'main'gabi-2502023-10-113-4/+188
|\ \ | | | | | | | | | | | | Implement build_auth_clients() See merge request tpo/core/arti!1642
| * | Implement build_auth_clients()Neel Chauhan2023-10-113-4/+188
| | |
* | | Merge branch 'oneshot' into 'main'Nick Mathewson2023-10-1138-44/+117
|\ \ \ | |/ / |/| | | | | | | | | | | | | | Provide and mandate Fuse type veneer around oneshot Closes #1059 See merge request tpo/core/arti!1656
| * | oneshot: Apply deferred rustfmt churnIan Jackson2023-10-1117-28/+21
| | | | | | | | | | | | cargo fmt, precisely.
| * | oneshot: Deprecate futures::channel::oneshotIan Jackson2023-10-111-0/+5
| | |
| * | oneshot: Use veneer in arti-rpcserverIan Jackson2023-10-111-1/+2
| | |
| * | oneshot: Use veneer in tor-hsrproxyIan Jackson2023-10-113-1/+4
| | |
| * | oneshot: Use veneer in tor-dirmgrIan Jackson2023-10-114-2/+5
| | |
| * | oneshot: Use veneer in tor-hsclientIan Jackson2023-10-112-2/+2
| | |
| * | oneshot: Use veneer in tor-hsserviceIan Jackson2023-10-115-6/+7
| | |
| * | oneshot: Use veneer in tor-circmgrIan Jackson2023-10-115-5/+8
| | |
| * | oneshot: Use veneer in tor-ptmgrIan Jackson2023-10-114-2/+7
| | |
| * | oneshot: Use veneer in tor-guardmgrIan Jackson2023-10-114-2/+5
| | |
| * | oneshot: Use veneer in tor-chanmgrIan Jackson2023-10-113-1/+3
| | |
| * | oneshot: Use veneer in tor-protoIan Jackson2023-10-116-9/+15
| | |
| * | oneshot: Use veneer in tor-rtmockIan Jackson2023-10-114-2/+4
| | |
| * | oneshot: Avoid (one) use of .try_recv()Ian Jackson2023-10-111-2/+4
| | | | | | | | | | | | | | | | | | It's not so straightforward to provide this (we'd need to poll the FusedFuture and make a dummy a Context and so on), but this is just used once in a test where we can replace it with use of `poll!`
generated by cgit v1.2.3 (git 2.46.0) at 2026-08-27 18:41:21 +0000