| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | | | |
| | | |
| | | |
| | | |
| | | | |
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.
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
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.
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
For our time provider we want a priority queue that lets us look up
entries and delete them. std's Heap doesn't do that. priority-queue
has the API we need and reasonable stats etc, and is maintained.
It has some IMO-tolerable licence wrinkles.
|
| | | | |
| | | |
| | | |
| | | | |
Nowadays there are methods for this.
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
arti: Write the minimal code needed to launch onion proxies.
See merge request tpo/core/arti!1644
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | | |
This makes some other futures Send+Sync, which lets us spawn them.
|
| | | | | | |
|
| | | | | | |
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Scripts to make release process more robust
See merge request tpo/core/arti!1646
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
(If a published crate depends on an unpublished crate, crates.io
will refuse it.)
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
None of our crates should use wildcard versions; this will help us
detect them before publishing.
|
| | |/ / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
In particular, this change should help avoid the kind of problem we
ran into as #1054 and fixed with 00e4405943498754, where a crate
changed only in which versions of our crates it depended upon,
and we didn't notice that we had to update its version too.
This commit also fixes a couple of minor issues in the
`changed_crates` script, and gives it a verbose mode.
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
tor-hsservice: ipt_set: Docs clarifications
See merge request tpo/core/arti!1647
|
| | |/ / / /
| | | | |
| | | | |
| | | | | |
Apropos a conversation in !1645
|
| |\ \ \ \ \
| |/ / / /
|/| | | |
| | | | |
| | | | |
| | | | |
| | | | | |
tor-hsservice: Share an IptsPublisherUploadView with each upload task.
Closes #1050
See merge request tpo/core/arti!1645
|
| | | | | | |
|
| | | | | | |
|
| |/ / / /
| | | |
| | | |
| | | |
| | | |
| | | | |
This enables us to specify a more accurate `worst_case_end` publish time.
Closes #1050
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
tor-hsservice: Fix semantic conflict.
See merge request tpo/core/arti!1643
|
| |/ / / /
| | | |
| | | |
| | | |
| | | | |
This fixes a compile error that resulted from a semantic conflict
between !1634 and !1638.
|
| |\ \ \ \
| | |/ /
| |/| |
| | | |
| | | | |
Initial work on top-level onion service configuration
See merge request tpo/core/arti!1638
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | | |
The old name was a copy-paste error.
|
| | | | |
| | | |
| | | |
| | | | |
This lets us write `[onion_services.allium_cepa]`.
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | | |
There are no tests for parsing it yet.
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
We plan to ship without them at first, so we may as well remove
them.
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
These don't yet attach to the rest of the ArtiConfig, or actually
launch any onion services, but they're a start.
|
| | | | | |
|
| | | | | |
|
| | | | | |
|