| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
```bash
bump=(caret equix fs-mistrust fslock-guard futures-copy oneshot-fused-workaround retry-error safelog slotmap-careful test-temp-dir web-time-compat)
./maint/bump-nodep "${bump[@]}"
```
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
```bash
cargo set-version --bump patch -p hashx
```
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
```bash
cargo set-version --bump patch -p arti
```
|
| |/ / / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
```bash
readarray -t bump < <(maint/list-crates | grep -P '^tor-|^arti-')
for crate in "${bump[@]}"; do cargo set-version --bump minor -p "${crate}"; done
```
|
| | | | |
| | | |
| | | |
| | | | |
Signed-off-by: David Goulet <[email protected]>
|
| | | | |
| | | |
| | | |
| | | | |
Signed-off-by: David Goulet <[email protected]>
|
| | | | |
| | | |
| | | |
| | | | |
Signed-off-by: David Goulet <[email protected]>
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
We have decided that instead of "uniq_id" in logging, we'll use the
"<domaine>-[<type>]-id" syntax to indicate who is that unique ID.
This commit only renames circuit's unique ID to "circ_uniq_id".
Signed-off-by: David Goulet <[email protected]>
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This commit only affects logging. Whenever possible, log both the UniqId
and CircId.
This also changes the log lines which is now "uniq_id=" and "circ_id="
as the UniqId is internal and circ_id (CircId) is protocol level.
Signed-off-by: David Goulet <[email protected]>
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
A CircId is now a circ_id and a UniqId is a unique_id so we stop
confusing them in the code.
Furthermore, channel_id that are CircId are now circ_id. Channel IDs are
different and encoded internally into a UniqId.
This is the first step to clarify semantic before we change the logging
to log both unique ID and circ ID.
No behavior change.
Signed-off-by: David Goulet <[email protected]>
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
I'm not actually sure what I did here. I was getting a lot of confusing
results from 'cargo sort' and 'maint/cargo-sort', so I ran a bunch of
commands until 'maint/cargo-sort' was okay. ('maint/cargo-sort' still
shows some errors, but not in arti-dirauth anymore.)
But as long as the 'maint/cargo-sort' in CI is okay with the changes,
then I think it's fine.
|
| | | | | |
|
| | | | | |
|
| |/ / / |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
arti-dirauth: FilenameOrStdio: Allow incremental writing
See merge request tpo/core/arti!4253
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The calling convention for compute-mds will be easiest to implement if
we can write to the two output files in parallel.
So provide `start_writing` giving a `Writing`.
Unfortuantely this commit has quite a bit of reorganisation which is
difficult to make into something easily reviewable.
|
| | | | |
| | | |
| | | |
| | | | |
This makes the next commit infinitesimally less confusing.
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
This is a better name, and will suit us better when we reorganise this
code to allow incremental writing.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Make this a doc comment.
We're going to add an entrypoint that makes this more likely.
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
tor-cell: Add missing semver.md entries
See merge request tpo/core/arti!4257
|
| | | | | |
| | | | |
| | | | |
| | | | | |
I forgot to add these during a previous MR.
|
| |\ \ \ \ \
| |/ / / /
|/| | | |
| | | | |
| | | | | |
tor-netdoc: testing: Expose some more test utilities
See merge request tpo/core/arti!4250
|
| | | | | |
| | | | |
| | | | |
| | | | | |
Involves code motion. Review with --color-moved.
|
| | | | | |
| | | | |
| | | | |
| | | | | |
I don't understand why this suddenly, but whatever.
|
| | | | | |
| | | | |
| | | | |
| | | | | |
Involves lots of code motion. Review with --color-moved.
|
| | | | | |
| | | | |
| | | | |
| | | | | |
This whole module is gated by the very same condition.
|
| | |/ / /
| | | |
| | | |
| | | | |
I discovered this didn't work, when I tried to use it.
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
We previously interpreted the rate in the XON message as being Kbits per
second, but it's really Kbytes per second.
|
| | | | | |
|
| | | | | |
|
| | |/ /
|/| | |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
tor-proto: Small improvements to circuit handshake tests
See merge request tpo/core/arti!4254
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
Now that we read all of the cells from the connection inspector, we can
reuse the existing channel objects.
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | | |
These TODOs are for client issues, not relay isues.
|
| | | | |
| | | |
| | | |
| | | | |
Otherwise the new circuit gets closed immediately by the relay.
|
| |\ \ \ \
| |/ / /
|/| | |
| | | |
| | | | |
tor-protover,tor-proto: Add and use a new `subprotocol_restricted_set` macro
See merge request tpo/core/arti!4241
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
