| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | | | | |
| | | | |
| | | | |
| | | | | |
This varied wildly.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
We had conflicting definitions of these links.
I have not gone through and changed *all* the crate links, just the
ones that had multiple conflicting definitions.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
We had conflicting definitions of these links.
I have not gone through and changed *all* the crate links, just the
ones that had multiple conflicting definitions.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This link target definition was included in the entry for 1.1.6, but
that anchor text in that entry has a URL for a ticket, so the
definition is not used (in that entry).
The same link anchor is defined differently several times elsewhere.
So just drop this one.
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | | |
My more pernickety script hates the extra spaces.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
I'm not sure if Markdown tolerates this being broken across a line,
but our scripting is going to have trouble with it.
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | | |
This tells us how to break the file into pieces.
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This will be used by gen_md_links, instead of the regexp-based ad-hoc
parser there.
The existing parser gets wrong things like " `#[must_use]` ",
thinking that's a link.
Use a proper Markdown parser. But, we must commit some abuse, sadly.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
I was going to want to call this from another program with a filename,
which meant I needed to unparse the arguments, which meant I wanted a
competent parser to feed things to.
As it happens my caller doesn't use this any more, but let's keep the
improvement anyway.
|
| | | | | | |
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
tor-circmgr: Replace STUB/STUB+ terminology with SHORT/EXTENDED.
Closes #1339
See merge request tpo/core/arti!2161
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
The previous STUB/STUB+ terminology was confusing, because STUB and
STUB+ are both "circuit stubs" (but STUB is shorter than STUB+).
Closes #1339
|
| | | |_|/ /
| |/| | |
| | | | |
| | | | | |
Part of #1339
|
| |\ \ \ \ \
| |_|_|/ /
|/| | | |
| | | | |
| | | | | |
proto: Explicitly enforce maxima on SENDME windows.
See merge request tpo/core/arti!2150
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
No actual bug here, just technical debt:
For `SendWindow`s, our tag system already ensured that we rejected
any SENDME that didn't correspond to an appropriate drain. Still,
it doesn't hurt to check.
For `RecvWindow`s, it would have been a protocol violation if we
ever did this, but it makes sense to make it an internal error if we
try.
Part of #1383.
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Forbid script suffixes
See merge request tpo/core/arti!2153
|
| | | | | | | |
|
| | | |/ / /
| |/| | | |
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
RPC: Enforce method name format.
Closes #823
See merge request tpo/core/arti!2149
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
(We don't give an error about unrecognized namespaces (for now),
since we have no way to opt in to them.)
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
We need to do this carefully, since we want our system to be
extensible with new namespaces.
First, when we are constructing an RpcMgr, we _warn_ about any
method names that are misformed.
Second, we add a test in the `arti` crate to fail if any method
names are invalid. This will only catch method names in crates that
`arti` depends on.
|
| | | |/ / /
| |/| | |
| | | | |
| | | | |
| | | | | |
Specifically, we want a single colon, and we want our
method names to be in snake_case.
|
| |\ \ \ \ \
| |_|/ / /
|/| | | |
| | | | |
| | | | | |
doc: Use locked build
See merge request tpo/core/arti!2157
|
| | | | | | |
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Soup up maint/cargo-publish a bit
See merge request tpo/core/arti!2158
|
| | | | | | | |
|
| | | | | | | |
|
| | |/ / / / |
|
| |\ \ \ \ \
| |/ / / /
|/| | | |
| | | | |
| | | | |
| | | | |
| | | | | |
arti: 1.2.3 release
Closes #1400 and #1409
See merge request tpo/core/arti!2156
|
| | |\ \ \ \
| |/ / / /
|/| | | | |
|
| |\ \ \ \ \
| |_|_|_|/
|/| | | |
| | | | |
| | | | | |
arti-client: Add one-hop circuit example
See merge request tpo/core/arti!2148
|
| |/ / / /
| | | |
| | | |
| | | | |
Co-authored-by: gabi-250 <[email protected]>
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
tor-circmgr: If necessary, extend the circuit to become STUB+.
Closes #1400 and #1409
See merge request tpo/core/arti!2145
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | | |
We will soon need to reuse this.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
I am about to reuse one of these on the "lite" vanguards branch. I am
renaming them to make it easier to see which one of the two I will be
using.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
One of these assertions currently fails, because we have a bug in the
vanguard path builder: if lite vanguards are enabled, we only build
2-hop circuits instead of 3.
|
| | | | | |
| | | | |
| | | | |
| | | | | |
Closes #1400
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
We're about to use this in `maybe_extend_stub_circuit` too.
Part of #1400
|