| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Done with the commands below.
The following crates have had various changes, and should get a
patchlevel bump. Since they are pre-1.0, we do not need to
distinguish new APIs from other changes.
```
cargo set-version --bump patch -p arti-client
cargo set-version --bump patch -p safelog
cargo set-version --bump patch -p tor-bytes
cargo set-version --bump patch -p tor-cert
cargo set-version --bump patch -p tor-circmgr
cargo set-version --bump patch -p tor-config
cargo set-version --bump patch -p tor-consdiff
cargo set-version --bump patch -p tor-dirclient
cargo set-version --bump patch -p tor-dirmgr
cargo set-version --bump patch -p tor-error
cargo set-version --bump patch -p tor-hsservice
cargo set-version --bump patch -p tor-linkspec
cargo set-version --bump patch -p tor-llcrypto
cargo set-version --bump patch -p tor-netdir
cargo set-version --bump patch -p tor-netdoc
cargo set-version --bump patch -p tor-proto
cargo set-version --bump patch -p tor-rpcbase
cargo set-version --bump patch -p tor-socksproto
```
This crate has new features, but no new non-experimental Rust APIs.
So even though it is post-1.0, it gets a patchlevel bump.
```
cargo set-version --bump patch -p arti
```
|
| |
|
|
|
|
|
|
|
|
| |
Done with:
```
cargo set-version --bump minor -p tor-hsclient
cargo set-version --bump minor -p arti-rpcserver
cargo set-version --bump minor -p tor-hscrypto
cargo set-version --bump minor -p tor-cell
```
|
| |
|
|
|
| |
Some of these seem spurious: it looks like fixup-features resolved
an issue and then complained about it too. I'll investigate further.
|
| | |
|
| | |
|
| |
|
|
| |
`ArtiPathComponent` is a more generic version of `HsClientSpecifier`.
|
| |\
| |
| |
| |
| | |
tor-hsclient: Use estimated timeouts
See merge request tpo/core/arti!1342
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
Replacing RPT_IPT_TIMEOUT is not entirely straightforward.
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| |\ \
| |/
|/|
| |
| | |
tor-netdoc: Handle anomalous numbers of introduction points
See merge request tpo/core/arti!1332
|
| | |
| |
| |
| | |
None of the existing NetdocErrorKinds seemed right.
|
| |\ \
| | |
| | |
| | |
| | | |
tor-hsclient: Reimplement Debug for MockCirc
See merge request tpo/core/arti!1324
|
| | | |
| | |
| | |
| | |
| | | |
This is less code. Also it now dumps the connect_called field which
was introduced in the meantime.
|
| |\ \ \
| |/ /
|/| |
| | |
| | |
| | |
| | | |
tor-hsclient: Use proper CircParameters
Closes #935
See merge request tpo/core/arti!1340
|
| | | |
| | |
| | |
| | | |
Fixes #935
|
| |\| |
| | |
| | |
| | |
| | | |
tor-hsclient: Handle handshake completion error correctly
See merge request tpo/core/arti!1336
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
Thsi is a bit of a mouthful now, but it is comprehensible.
As per
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/1336#note_2917235
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
See
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/1336#note_2917236
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
We need to handle errors during the handshake. That also produces a
`tor_proto::Error` but we want to print a different message for that,
so let's rename this before adding the new variant.
|
| | |/
| |
| |
| | |
It was wrong where ti was.
|
| | |
| |
| |
| | |
Since arti!1233 this is trivial.
|
| |/
|
|
|
| |
For some reason this wasn't used in the actual errors,
although it *was* used in the types of the functions etc.
|
| |\
| |
| |
| |
| | |
tor-hsclient: Discuss intro circuit extend-and-reuse
See merge request tpo/core/arti!1298
|
| | | |
|
| | |
| |
| |
| | |
This is a summary of a discussion I had on IRC.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
Conceptually this is a fixup to
HS configuration: Add retry parameters to configuration
which erroneously removed these comments - they were intended to apply
to *all* these parameters, not just the max attempts.
Not marking it as fixup! because that would involve merge conflicts.
|
| | |
| |
| |
| |
| |
| |
| | |
Explain why this fallback to MAX is good.
Discussion
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/1305#note_2915927
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
Apply deferred rustfmt churn.
|
| | |
| |
| |
| |
| | |
Invent a trait a la circmgr config for the hs client connector config.
Plumb a suitable value all the way through to the code that will use it.
|
| | |
| |
| |
| |
| |
| |
| | |
I think these should go in `[circuit_timing]`. That section already
has some retry parameters, so is not strictly *timing*.
This is not honoured yet.
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
1. Fix a use of 10ms that should have been TIMEOUT_SLOP.
2. Increase BODGE_YIELD by a factor of 5.
Now this test should tolerate being hung up for 125ms. I am hoping
that this will fix the CI failure
https://gitlab.torproject.org/Diziet/arti/-/jobs/302457
which fails at the line comparing circuit1 with circuit2a.
(I can't repro that locally.)
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| | |
Without this, the expiry task can end up choosing a 600s timeout
starting *after we advanced the clock*.
Fixes #923
|
| | |
| |
| |
| |
| |
| |
| |
| | |
The provided impl for Mutex is hopeless: it prints just some internal
flags and doesn't acquire the mutex for printing purposes.
At some point we might want to factor this out as a general function
on `Arc<Mutex<...>>` but not now.
|
| |\ \
| | |
| | |
| | |
| | | |
Upgrade to itertools 0.11.0
See merge request tpo/core/arti!1306
|
| | | |
| | |
| | |
| | | |
The breaking changes here do not seem to affect us.
|