summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
...
| * | | | CHANGELOG: Document changes up to nowIan Jackson2024-06-261-0/+125
| | | | |
* | | | | Merge branch 'client-rend-stub' into 'main'gabi-2502024-06-262-4/+4
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | vanguards: Make client rend circuits be STUB+. Closes #1474 See merge request tpo/core/arti!2230
| * | | | | tor-circmgr: Make client rendezvous circuits EXTENDED instead of SHORT.Gabriela Moldovan2024-06-251-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This updates the code to match the spec. This fixes TROVE-2024-008. Closes #1474
| * | | | | doc/dev/notes: vanguards: Make client rend circuits be STUB+.Gabriela Moldovan2024-06-251-1/+1
| | |/ / / | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | According to the [vanguards spec], client rendezvous circuits should be STUB+: * lite: `C -> G -> L2 -> Rend` * full: `C -> G -> L2 -> L3 -> Rend` [vanguards spec]: https://gitlab.torproject.org/tpo/core/torspec/-/blob/e5ace3667dcbbf893c6b632fd4e3f16114fd2a0e/spec/vanguards-spec/index.md
* | | | | Merge branch 'osx' into 'main'Ian Jackson2024-06-262-21/+18
|\ \ \ \ \ | |_|/ / / |/| | | | | | | | | | | | | | | | | | | | | | | | Fix macos build test by bodging the Cargo.lock Closes #1472 See merge request tpo/core/arti!2234
| * | | | Enable the build-repro CI job in MR jobsIan Jackson2024-06-261-4/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Hopefully this will not be too slow. Fixes #1472.
| * | | | Revert "Disable macos build tests"Ian Jackson2024-06-261-1/+2
| | | | | | | | | | | | | | | | | | | | This reverts commit a6801c10584558316ff38f354167812d0c697549.
| * | | | Downgrade to cc 1.0.93 in Cargo.lockIan Jackson2024-06-261-16/+15
|/ / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | As proposed in https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/2231#note_3043322 I made this commit by: * Taking the hunk to add `cc = "1.0.93"` from !2231. * Running `cargo fetch` * Staging everything except the additions of cc to `Cargo.toml` and `Cargo.lock` Here is the output I got from cargo: Updating crates.io index Locking 5 packages to latest compatible versions Downgrading addr2line v0.22.0 -> v0.21.0 (latest: v0.23.0) Downgrading backtrace v0.3.73 -> v0.3.71 (latest: v0.3.73) Downgrading cc v1.0.100 -> v1.0.93 (latest: v1.0.101) Downgrading gimli v0.29.0 -> v0.28.1 (latest: v0.30.0) Downgrading object v0.36.0 -> v0.32.2 (latest: v0.36.0) Downloaded cc v1.0.93 Downloaded derive-deftly v0.13.1 Downloaded 2 crates (149.8 KB) in 1.52s
* | | | Merge branch 'update2' into 'main'gabi-2502024-06-261-32/+12
|\ \ \ \ | |/ / / |/| | | | | | | | | | | Update to derive-deftly 0.13.1 See merge request tpo/core/arti!2232
| * | | Update to derive-deftly 0.13.1Ian Jackson2024-06-261-32/+12
|/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This fixes build breakage in the build-repro test. derive-deftly 0.13.0 has an MSRV violation, due to a breach by cargo of the Rust stability guarantee: d-d 0.13.0 works with Rust 1.56 but not 1.76. References: https://gitlab.torproject.org/Diziet/rust-derive-deftly/-/issues/103 https://github.com/rust-lang/cargo/issues/14147#issuecomment-2189915460
* | | Merge branch 'no-arti-hyper' into 'main'Ian Jackson2024-06-258-756/+20
|\ \ \ | | | | | | | | | | | | | | | | Remove arti-hyper See merge request tpo/core/arti!2225
| * | | Remove arti-hyperIan Jackson2024-06-257-736/+17
| | | | | | | | | | | | | | | | | | | | | | | | This has been obsolete for a very long time. We have already published a version with a "won't be updated" warning.
| * | | Stop building examples/gsoc2023/download-managerIan Jackson2024-06-253-20/+3
|/ / /
* | | Merge branch 'feat' into 'main'gabi-2502024-06-253-2/+3
|\ \ \ | | | | | | | | | | | | | | | | Run maint/fixup-features See merge request tpo/core/arti!2229
| * | | Fix formatting anomaly introduced by fixup-featuresIan Jackson2024-06-251-1/+2
| | | |
| * | | Run maint/fixup-featuresIan Jackson2024-06-253-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Precisely nailing-cargo -Eu run -p fixup-features Cargo.toml These changes are just `full` propagation. Note the `?` in the arti-relay propagation, which is essential: we don't actually *enable* arti-relay at all, with this. Also, there is a formatting anomaly, which I'll fix in a moment.
* | | | Merge branch 'update' into 'main'gabi-2502024-06-2527-289/+271
|\ \ \ \ | |/ / / |/| | | | | | | | | | | Routine dependency updates See merge request tpo/core/arti!2228
| * | | Update to base32 0.5Ian Jackson2024-06-252-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | No code changes needed. Precisely nailing-cargo -Eu upgrade --incompatible -p base32
| * | | Update to statrs 0.17Ian Jackson2024-06-252-11/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | No code changes needed. Precisely nailing-cargo -Eu upgrade --incompatible -p statrs
| * | | Update to itertools 0.13.0Ian Jackson2024-06-2521-47/+47
| | | | | | | | | | | | | | | | | | | | | | | | | | | | No code changes needed. Precisely nailing-cargo -Eu upgrade --incompatible -p itertools
| * | | Require strum 0.26.3Ian Jackson2024-06-2510-10/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We're about to update to iterools 0.13.0. We must therefore have a version of strum which is not affected by https://github.com/Peternator7/strum/issues/358 Precisely git-grep -l '^strum' | xargs perl -i~ -pe 's{"0\.26"}{"0.26.3"}' No changes to lockfile - we're already using 0.26.3, except perhaps in the minimal versions test.
| * | | Update to derive-deftly 0.13.0Ian Jackson2024-06-2514-18/+18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | No code changes needed. Precisely nailing-cargo -Eu upgrade --incompatible -p derive-deftly
| * | | Update dependencies, where semver-compatibleIan Jackson2024-06-251-202/+185
|/ / / | | | | | | | | | | | | Precisely cargo update
* | | Merge branch 'no-osxcross' into 'main'gabi-2502024-06-251-2/+1
|\ \ \ | | | | | | | | | | | | | | | | Disable macos build tests See merge request tpo/core/arti!2226
| * | | Disable macos build testsIan Jackson2024-06-251-2/+1
| |/ /
* | | Merge branch 'AtomicOptTimestamp' into 'main'Jim Newsome2024-06-243-12/+12
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | Rename OptTimestamp to AtomicOptTimestamp Closes #1412 See merge request tpo/core/arti!2218
| * | | Rename OptTimestamp to AtomicOptTimestampNeel Chauhan2024-06-243-12/+12
| |/ /
* | | Merge branch 'owner' into 'main'gabi-2502024-06-241-0/+1
|\ \ \ | |/ / |/| | | | | | | | Turn crate ownership discrepancies into a warning See merge request tpo/core/arti!2220
| * | Turn crate ownership discrepancies into a warningIan Jackson2024-06-241-0/+1
|/ / | | | | | | | | Ideally we'd tolerate situations with unaccepted ownership requests, but that information doesn't seem to be public.
* | Merge branch 'doc-warning-20240624' into 'main'Nick Mathewson2024-06-241-2/+2
|\ \ | | | | | | | | | | | | Resolve a rustdoc warning. See merge request tpo/core/arti!2215
| * | Resolve a rustdoc warning.Nick Mathewson2024-06-241-2/+2
| | |
* | | Merge branch 'rpc-docs-part1' into 'main'Nick Mathewson2024-06-241-0/+156
|\ \ \ | | | | | | | | | | | | | | | | Write a README for tor-rpcbase See merge request tpo/core/arti!2210
| * | | Write a README for tor-rpcbaseNick Mathewson2024-06-241-0/+156
| | |/ | |/|
* | | Merge branch 'owners' into 'main'Ian Jackson2024-06-247-67/+186
|\ \ \ | |_|/ |/| | | | | | | | Better crate ownership check, and run it in CI See merge request tpo/core/arti!2201
| * | Update Release.md to reference new ownership scriptIan Jackson2024-06-241-1/+1
| | |
| * | maint/crates-io-utils.sh: Try to deconfuse shellcheckIan Jackson2024-06-241-0/+6
| | |
| * | Remove check-crate-owners scriptIan Jackson2024-06-241-35/+0
| | | | | | | | | | | | | | | | | | | | | | | | This is superseded now. (I wish I had noticed it; perhaps I could have souped it up rather than writing a whole new thing, but I think the result would have been much the same.)
| * | Check crate ownership in CI, but only on mainIan Jackson2024-06-241-0/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | I think that the effect of this will be as follows: * MR branches will never run this, so when the crate ownership is wrong, development can continue. * When a new crate is first published, it will transition from "ignored" to "complaining". This will happen on the first CI run on main after "cargo publish" is run. But it *won't* happen on the CI run on the publication tag. The intent is that we discover a failure to `git add` while the release technician who published the new crate is still around.
| * | maint/cargo-crate-owners: More sophisticated ownership check scriptIan Jackson2024-06-241-0/+90
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Compared to check-crate-owners: 1. Checks for uniformity, rather than having an embedded list of intended maintainers. 2. Uses curl | jq, rather than `cargo owner`. This is necessary for: 3. Ignores crates which have never been published. This is necessary to be able to run this in CI, since there may be new crates in the workspace. 4. Prints the ownership information rather differently - just the usernames. This is a consequence of using curl | jq.
| * | maint/crates-io-utils.sh: Add preserving tmp featureIan Jackson2024-06-241-2/+8
| | | | | | | | | | | | This is useful for debugging.
| * | maint/crates-io-utils.sh: Add exit status control featureIan Jackson2024-06-241-1/+5
| | |
| * | maint/crates-io-utils.sh: Break out from cargo-publishIan Jackson2024-06-242-30/+62
| | |
| * | shellcheck: check *.sh files tooIan Jackson2024-06-241-1/+4
| |/ | | | | | | | | We (will) use `*.sh` for shell include files. We're about to make one of these.
* | Merge branch 'fslock-retry' into 'main'Nick Mathewson2024-06-246-10/+150
|\ \ | |/ |/| | | | | | | | | TorClientBuilder: Add the ability to retry when fslock fails Closes #1464 See merge request tpo/core/arti!2198
| * Add a maximum to local_resource_timeout.Nick Mathewson2024-06-242-8/+33
| |
| * local_resource_timeout: Change wait interval to 50 ms.Nick Mathewson2024-06-241-1/+1
| |
| * Rename fslock_timeout to local_resource_timeoutNick Mathewson2024-06-241-11/+16
| | | | | | | | Name chosen to match the error kind that we're detecting.
| * Clarify documentation about blocking.Nick Mathewson2024-06-241-2/+4
| |
| * arti: wait a short while on startup if lockfiles are unavailable.Nick Mathewson2024-06-241-1/+1
| |
| * TorClientBuilder: Wait for a little while if the lockfiles are held.Nick Mathewson2024-06-243-4/+111
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This commit adds a parameter to TorClientBuilder that control how long we should retry constructing a TorClient if we get a LocalResourceInUse error. When this parameter is not set, we default to 500 milliseconds for async entry points and 0 milliseconds for sync entry points. (`LocalResourceInUse` usually means that a lockfile is held by somebody else; but when the resource is some other type, we typically want the same behavior anyway.) (I really don't want to introduce delays by default for the create_unbootstrapped case, since it previously had no delay at all.) There is now also an async entry point to create an unbootstrapped TorClient. Closes #1464.
generated by cgit v1.2.3 (git 2.46.0) at 2026-08-27 12:01:36 +0000