| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
| |
derive-deftly 0.10.x rejects unrecognised `#[deftly]` attributes.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is the combination of a number of separate commits, many of which
were generated by seddery, and then rebased and squashed.
Cargo.toml
perl -i~ -pe 's{^derive-adhoc}{derive-deftly = "0.10"}' crates/*/Cargo.toml
(not regenerated during rebase)
update Cargo.lock
`cargo fetch` without --locked
(regenerated during rebase)
seddery
git-ls-files | grep '\.rs$' | xargs perl -i~ -pe 's{^use derive_adhoc}{use derive_deftly}'
git-ls-files | grep '\.rs$' | xargs perl -i~ -pe 's{\bdefine_derive_adhoc\b}{define_derive_deftly}g'
git-ls-files | grep '\.rs$' | xargs perl -i~ -pe 's{\bAdhoc\b}{Deftly}g if m{derive}'
git-ls-files | grep '\.rs$' | xargs perl -i~ -pe 's{\#\[derive_adhoc\b}{#[derive_deftly}g'
git-ls-files | grep '\.rs$' | xargs perl -i~ -pe 's{use derive_adhoc}{use derive_deftly}'
git-ls-files | grep '\.rs$' | xargs perl -i~ -pe 's{\bderive_adhoc\b}{derive_deftly_adhoc} if m{use.*deftly}'
git-ls-files | grep '\.rs$' | xargs perl -i~ -pe 's{\bderive_adhoc!}{derive_deftly_adhoc!}'
(not regenerated during rebase)
Manually add `#[derive_deftly_adhoc]` where needed.
seddery
git-ls-files | grep '\.rs$' | xargs perl -i~ -pe 's{\#\[adhoc\b}{#[deftly}g'
git-ls-files | grep '\.rs$' | xargs perl -i~ -pe 's{\bderive_adhoc_template}{derive_deftly_template}'
(not regenerated during rebase)
Manually fix up an import
Manually update some builder attrs
Manually fix up tor_rtmock::time_core
This was missed in my seddery, due to me rebasing the branch and not
redoing the seddery.
|
| |
|
|
|
| |
This was incorrect usage, as pointed out in
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/2052#note_3012727
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
It bothered me that when I added a `MockCoarseTimeProvider` to the
mock time providers, I had to manually grep to check that there
weren't places the time was updated where I ought to also update the
coarse time.
Prove that the code is right by hiding all the times together in a
struct that prevents un-synchronised updates.
This is part 1, where we move the fields from simple_time::State to
the new struct.
|
| | |
|
| |
|
|
|
|
| |
We're going to put more in here.
(Yes, I know we just invented this...)
|
| |
|
|
|
| |
Modules with the same name as external crates don't work well with our
MSRV.
|
| | |
|
| |
|
|
| |
We must also impl CoarseTimeProvider for mocked runtimes.
|
| | |
|
| |
|
|
| |
This reduces duplication a little.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
This makes it synchronous. The trait bounds on the return type
have also been relaxed to not require Clone
|
| |
|
|
|
|
|
| |
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
|
| | |
|
| |
|
|
|
| |
Always reify a default SimpleMockTimeProvider, and then apply the
starting_wallclock to it. This will make the next change fit.
|
| |
|
|
|
|
|
|
| |
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.
|
| | |
|
| |
|
|
| |
cargo fmt, precisely.
|
| | |
|
| |
|
|
| |
This was a slip.
|
| |
|
|
|
| |
Adding "/// " to every line causes rustfmt to have conniptions about
the trailing whitespace.
|
| |
|
|
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| |
|
|
| |
This is clearer, I think.
|
| |
|
|
| |
This is clearer, I think.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
The module-level docs here are less visible and also not where most of
the other stuff was.
|
| | |
|
| | |
|
| |
|
|
| |
And introduce a table showing the situations.
|
| |
|
|
|
| |
We don't need it any more; we won't call wake again.
So, call .wake() rather than .wake_by_ref().
|
| |
|
|
|
|
| |
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.
|
| |
|
|
|
| |
This helped me diagnose
https://gitlab.torproject.org/tpo/core/arti/-/issues/1040
|
| |
|
|
| |
We're going to want to add something to it.
|
| | |
|
| |
|
|
|
| |
Now we're making breaking changes anyway, in or mock crate, it is a
convenient time to get rid of this.
|
