| Commit message (Collapse) | Author | Age | Files | Lines | ||
|---|---|---|---|---|---|---|
| ... | ||||||
| * | Update to derive-adhoc 0.8 | Ian Jackson | 2024-01-02 | 1 | -1/+1 | |
| | | | | | | As recommended in the d-a changelog, I'm not calling this a breaking change to our APIs. | |||||
| * | Merge branch 'msrv-followup' into 'main' | Nick Mathewson | 2023-12-04 | 1 | -4/+0 | |
| |\ | | | | | | | | | Followups from MSRV 1.70 upgrade See merge request tpo/core/arti!1785 | |||||
| | * | rtmock: Remove now-needless to_string calls. | Nick Mathewson | 2023-11-30 | 1 | -4/+0 | |
| | | | ||||||
| * | | Remove semver.md files. | Nick Mathewson | 2023-12-04 | 1 | -1/+0 | |
| | | | ||||||
| * | | Bump patchlevel versions in preparation for release | Nick Mathewson | 2023-12-04 | 1 | -4/+4 | |
| |/ | | | | | | | | | | | | | | | 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. | Nick Mathewson | 2023-11-28 | 1 | -1/+1 | |
| | | ||||||
| * | tor-rtmock: get rid of unwrap() | Saksham Mittal | 2023-11-21 | 1 | -1/+1 | |
| | | ||||||
| * | tor-rtmock: handle Receiver result inside spawn_join() | Saksham Mittal | 2023-11-21 | 2 | -3/+3 | |
| | | ||||||
| * | tor-rtmock: use expect() instead | Saksham Mittal | 2023-11-21 | 1 | -1/+2 | |
| | | ||||||
| * | tor-rtmock: change return types to be less concrete | Saksham Mittal | 2023-11-21 | 2 | -2/+2 | |
| | | ||||||
| * | tor-rtmock: change return type of spawn_join() | Saksham Mittal | 2023-11-21 | 2 | -6/+6 | |
| | | | | | | This makes it synchronous. The trait bounds on the return type have also been relaxed to not require Clone | |||||
| * | tor-rtmock: introduce spawn_join() for MockRuntime & MockExecutor | Saksham Mittal | 2023-11-21 | 2 | -0/+30 | |
| | | | | | | | | This helps abstract away the need to create a oneshot channel in order to get the return value out of an async function when using MockRuntime. ref: https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/1727#note_2965352 | |||||
| * | Upgrade to itertools 0.12.0 | Nick Mathewson | 2023-11-15 | 1 | -1/+1 | |
| | | ||||||
| * | tor-rtmock: MockRuntimeBuilder: new sleep_provider() setter | Ian Jackson | 2023-11-01 | 2 | -1/+11 | |
| | | ||||||
| * | tor-rtmock: simplify/reorganise MockRuntimeBuilder::build | Ian Jackson | 2023-11-01 | 1 | -4/+3 | |
| | | | | | | Always reify a default SimpleMockTimeProvider, and then apply the starting_wallclock to it. This will make the next change fit. | |||||
| * | Remove semver.md files from arti 1.1.10 | Nick Mathewson | 2023-10-31 | 1 | -6/+0 | |
| | | ||||||
| * | Patch version bumps in crates without breaking changes | Nick Mathewson | 2023-10-31 | 1 | -1/+1 | |
| | | | | | | | | | | | | | | | | | | | ``` These crates have new APIs: tor-async-utils ADDED tor-config ADDED tor-hscrypto ADDED tor-netdoc ADDED, plus BREAKING-experimental. These crates have patch-level changes only: tor-netdir (bugfix only). (re-exposes netdoc) arti-rpcserver (tweaks only, uses nothing that broke.) arti 1.1.10, no stable public APIs. ``` | |||||
| * | Minor version bumps in crates with breaking changes. | Nick Mathewson | 2023-10-31 | 1 | -2/+2 | |
| | | | | | | | | | | | | | | | | | | | | | | | ``` tor-basic-utils BREAKING tor-rtmock BREAKING. tor-cert BREAKING tor-cell BREAKING tor-proto BREAKING: re-exposes cell. (Also BREAKING-experimental) tor-chanmgr BREAKING: Re-exposes proto. tor-ptmgr BREAKING: re-exposes tor-chanmgr tor-guardmgr BREAKING: re-exposes proto. (Only for ClockSkew I think?) tor-circmgr BREAKING: re-exposes proto tor-dirclient BREAKING tor-hsclient BREAKING, re-exposes proto. tor-hsservice BREAKING, re-exposes proto. tor-hsrproxy BREAKING arti-client BREAKING: re-exposes proto. arti-hyper: BREAKING, re-exposes arti-client. tor-dirmgr Let's assume BREAKING, very high-level. tor-keymgr BREAKING, but experimental. ``` | |||||
| * | Run "fixup-features" in preparation for release this week. | Nick Mathewson | 2023-10-29 | 1 | -1/+1 | |
| | | ||||||
| * | tor-rtmock: MockRuntime::test_with_various: Print what we're doing | Ian Jackson | 2023-10-16 | 1 | -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 accessor | Ian Jackson | 2023-10-16 | 2 | -0/+16 | |
| | | ||||||
| * | oneshot: Apply deferred rustfmt churn | Ian Jackson | 2023-10-11 | 2 | -2/+2 | |
| | | | | | cargo fmt, precisely. | |||||
| * | oneshot: Use veneer in tor-rtmock | Ian Jackson | 2023-10-11 | 3 | -2/+3 | |
| | | ||||||
| * | tor-rtmock: simple_time: Don't export State | Ian Jackson | 2023-10-05 | 1 | -1/+1 | |
| | | | | | This was a slip. | |||||
| * | tor-rtmock: Provide a comprehensive example | Ian Jackson | 2023-10-05 | 1 | -1/+100 | |
| | | ||||||
| * | tor-rtmock: Update the rubric for current recommendations | Ian Jackson | 2023-10-05 | 1 | -3/+8 | |
| | | ||||||
| * | tor-rtmock: MockSleepProvider docs: Move example (fmt) | Ian Jackson | 2023-10-05 | 1 | -12/+12 | |
| | | | | | | Adding "/// " to every line causes rustfmt to have conniptions about the trailing whitespace. | |||||
| * | tor-rtmock: MockSleepProvider docs: Move example | Ian Jackson | 2023-10-05 | 2 | -73/+73 | |
| | | | | | | | | | | | | This example demonstrates MockSleepRuntime, which we don't want to use in new tests. It's probably worth keeping it, though, to help with comprehension of existing tests. So move it. This does rather highlight the lack of good overall example/instructions for MockRuntime. | |||||
| * | tor-rtmock: simple_time: Rename `wakers` to `futures` (fmt) | Ian Jackson | 2023-10-05 | 1 | -1/+4 | |
| | | ||||||
| * | tor-rtmock: simple_time: Rename `wakers` to `futures` | Ian Jackson | 2023-10-05 | 1 | -11/+11 | |
| | | | | | This is clearer, I think. | |||||
| * | tor-rtmock: simple_time: Rename `pq` to `unready` | Ian Jackson | 2023-10-05 | 1 | -13/+13 | |
| | | | | | This is clearer, I think. | |||||
| * | tor-rtmock: simple_time: Expand on advance and task ordering | Ian Jackson | 2023-10-05 | 1 | -2/+8 | |
| | | ||||||
| * | tor-rtmock: simple_time: Clarify/correct comments about invariant | Ian Jackson | 2023-10-05 | 1 | -2/+2 | |
| | | ||||||
| * | tor-rtmock: Add deprecation warning to MockSleepRuntime | Ian Jackson | 2023-10-05 | 1 | -1/+7 | |
| | | ||||||
| * | tor-rtmock: MockSleepProvider docs: Move deprecation discussion | Ian Jackson | 2023-10-05 | 1 | -32/+38 | |
| | | | | | | The module-level docs here are less visible and also not where most of the other stuff was. | |||||
| * | tor-rtmock: MockSleepProvider docs: Compare with SimpleMockTimeProvider | Ian Jackson | 2023-10-05 | 1 | -0/+22 | |
| | | ||||||
| * | tor-rtmock: simple_time: Clarify some things in time_until_next_timeout | Ian Jackson | 2023-10-05 | 1 | -0/+6 | |
| | | ||||||
| * | tor-rtmock: simple_time: Give formal names to the states | Ian Jackson | 2023-10-05 | 1 | -2/+21 | |
| | | | | | And introduce a table showing the situations. | |||||
| * | tor-rtmock: simple_time: take() the waker when we wake | Ian Jackson | 2023-10-05 | 1 | -2/+5 | |
| | | | | | | We don't need it any more; we won't call wake again. So, call .wake() rather than .wake_by_ref(). | |||||
| * | tor-rtmock: Provide SimpleTimeProvider: clarify .sleep() innards | Ian Jackson | 2023-10-03 | 1 | -4/+6 | |
| | | | | | | | Making the SleepFuture first means we don't call .wake_any() with the other invariants violated. This doesn't actually matter with the code as it stands, but it's less confusing this way. | |||||
| * | tor-rtmock: MockRuntime: in advance_*, warn to stderr about looping | Ian Jackson | 2023-10-03 | 1 | -1/+21 | |
| | | | | | | This helped me diagnose https://gitlab.torproject.org/tpo/core/arti/-/issues/1040 | |||||
| * | tor-rtmock: Break out advance_inner | Ian Jackson | 2023-10-03 | 1 | -10/+31 | |
| | | | | | We're going to want to add something to it. | |||||
| * | tor-rtmock: Add a deprecation warning to MockSleepProvider | Ian Jackson | 2023-10-03 | 2 | -0/+14 | |
| | | ||||||
| * | tor-rtmock: Abolish deprecated Runtime::advance() | Ian Jackson | 2023-10-03 | 2 | -17/+1 | |
| | | | | | | Now we're making breaking changes anyway, in or mock crate, it is a convenient time to get rid of this. | |||||
| * | tor-rtmock: Fix doc refs to advance_* | Ian Jackson | 2023-10-03 | 1 | -2/+2 | |
| | | ||||||
| * | tor-rtmock: Rename MockRuntime::jump_to to jump_wallclock | Ian Jackson | 2023-10-03 | 2 | -2/+3 | |
| | | | | | | | This was named after the method from MockSleepRuntime. The name is confusing because it seems to imply it might do something to the monotonic time. | |||||
| * | tor-rtmock: Abolish just-introduced confusing type alias (fmt) | Ian Jackson | 2023-10-03 | 1 | -1/+1 | |
| | | ||||||
| * | tor-rtmock: Abolish just-introduced confusing type alias | Ian Jackson | 2023-10-03 | 1 | -8/+8 | |
| | | ||||||
| * | tor-rtmock: Switch MockRuntime to SimpleMockSleepProvider | Ian Jackson | 2023-10-03 | 3 | -12/+12 | |
| | | | | | | | | | | | | | | | | | For now we do this by changing the meaning of the name `MockSleepProvider` in runtime.rs. This is a bodge to reduce noise in this diff. Consequences at call sites: * If the type is named somehow, the other type must be used. * SimpleMockTimeProvider calls it jump_wallclock rather than jump_to, which is IMO a better name. (MockRuntime will change in a moment.) * SimpleMockTimeProvider's advance() function isn't async and doesn't yield. But none of the call sites actually mind that. | |||||
| * | tor-rtmock: Provide SimpleTimeProvider | Ian Jackson | 2023-10-03 | 4 | -0/+350 | |
| | | ||||||
 |
index : mirrors/arti.git | |
| mirror of https://gitlab.torproject.org/tpo/core/arti |
| summaryrefslogtreecommitdiff |