| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
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!`
|
| |/ / |
|
| |\ \
| | |
| | |
| | |
| | | |
Non-working attempt to test onion service configuration.
See merge request tpo/core/arti!1640
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
It still matches the start pattern in the same way, but it takes the
_next_ match of the end pattern after the start pattern, and it
allows the end pattern to be absent.
This will make the bridge tests a little more robust, and let the
onion service tests stop saying BEGIN and END.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Since config-rs has a bug breaking its support for nested arrays
(see discussion at !1640), we're temporarily changing the format
to a single string with a "=>" in the middle.
I've opened #1058 to put things back as they were once config-rs is
fixed.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
The problem here is that, for some reason, the proxy_rule
configuration doesn't actually work. I suspect a bug in
Flatten, since the same configuration works fine if you pass
it to the hsrproxy config directly.
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When generating a keypair, `KeyMgr::generate` inserts a
single entry representing the keypair into the keystore. However, for
some keypairs, the keystore will need contain a separate entry
containing just the public part of the keypair.
This commit introduces `KeyMgr::generate_with_derived`, which generates
2 entries in the specified keystore: one for the keypair and another for
the public key, which makes it easier to insert keypairs and their
corresponding public keys into the keystore without to fall out of sync.
Previously, generating a (public, private) keypair involved generating a
new keypair with `KeyMgr::generate` and manually inserting the
corresponding public key entry.
|
| | | |
| | |
| | |
| | |
| | |
| | | |
`EncodableKey` is a trait for encoding keypairs and public keys. Keygen
only makes sense for key_pairs_ (it doesn't make sense for public keys),
so it makes sense to move `generate()` out of `EncodableKey`,
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
Implement reconfigure functions for hsservice and hsrproxy
See merge request tpo/core/arti!1651
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | | |
Our reconfigure methods take these by convention.
|
| |\ \ \ \
| |/ / /
|/| | |
| | | |
| | | | |
tor-rtmock: Docs updates (and an API fix)
See merge request tpo/core/arti!1650
|
| | | | |
| | | |
| | | |
| | | | |
This was a slip.
|
| | | | | |
|
| | | | | |
|
| |\| | |
| | | |
| | | |
| | | |
| | | | |
Provide and use a SimpleMockTimeProvider
See merge request tpo/core/arti!1639
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
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.
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
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.
|