| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This is a bit complicated since:
- Using cbindgen with macro expansion requires a nightly rust:
so, we have to look for one.
- There are some cbindgen warnings which I cannot find any way to
suppress, so instead of giving all warnings, it seems better to
give a diff from the old list of warnings to the new list.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
This only covers the absolute minimal API in order to launch a
connection and run simple requests, and it doesn't document anything
nearly well enough. Nonetheless I think it's good enough for an
initial review, to make sure that we've got the basics right (as
well as a general consensus on the error handling API, naming, and
so forth).
|
| | |
| |
| |
| | |
(Internally, it is a boxed CStr that is always UTF-8.)
|
| |\ \
| |/
|/|
| |
| | |
CI: Fix file overlap errors on main
See merge request tpo/core/arti!2297
|
| | |
| |
| |
| |
| |
| |
| |
| | |
The -latest jobs don't actually have artifacts. But:
In the -latest jobs this can cause errors due to duplication: the
artifacts from the -recent jobs in the same pipeline result in EEXIST
errors.
|
| |/
|
|
|
| |
This will let us make the artifact processing only happen when we want
to save artifacts.
|
| |\
| |
| |
| |
| | |
Update bytemuck to 1.16.3; previous version was yanked.
See merge request tpo/core/arti!2294
|
| |/ |
|
| |\
| |
| |
| |
| |
| |
| | |
tor-dirmgr: Return an error if storage is readonly and DB is missing/incompatbile.
Closes #1497
See merge request tpo/core/arti!2283
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
missing/incompatbile.
This fixes a bug in `SqliteStore`'s constructor: previously, it would
unconditionally try to create the missing database, even if it didn't
have write access. As a result, it was impossible to reliably start
multiple concurrent arti processes configured with the same (empty or
nonexistent) cache_dir, because many of them would fail with errors such
as
```
attempt to write a readonly database: Error code 8: Attempt to write a readonly database
```
Returning a `LocalResourceAlreadyInUse` error kind here enables us to
leverage the retry loop from `TorClientBuilder::create_unbootstrapped`
(which retries on local resource errors if `local_resource_timeout` is
set).
Closes #1497
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | | |
arti: Add tests for the hss/hsc subcomands
Closes #1250
See merge request tpo/core/arti!2275
|
| | | |
| | |
| | |
| | | |
Prompted by https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/2275#note_3054040
|
| | | | |
|
| | | | |
|
| | | | |
|
| | |/
| |
| |
| | |
Closes #1250
|
| |\ \
| | |
| | |
| | |
| | | |
tor-rtmock docs: Improve discussions of mocked time
See merge request tpo/core/arti!2286
|
| | | | |
|
| | |/
| |
| |
| | |
Improve/replace some out-of-date notes in the docs.
|
| |\ \
| |/
|/|
| |
| |
| |
| | |
clippy: Disallow Path::exists().
Closes #1493
See merge request tpo/core/arti!2293
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| |/
|
|
| |
Part of #1493
|
| |\
| |
| |
| |
| | |
CI: Pin Rust compiler version (mostly)
See merge request tpo/core/arti!2290
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We replace uses of `amd64/rust:bookworm` in the `recent-*` jobs.
We add new latest-* jobs which
* aren't used for artifacts
* occur later in the pipeline
* only run on main, since we don't want them to block MRs
This is done with templates, to reuse the script parts.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Replace almost all the open-coded occurrences of `amd64/rust:bookworm`.
This rewinds us to Rust 1.79.
We can update after
https://github.com/rustsec/rustsec/issues/1217
is fixed upstream.
We're going to handle the rust-latest-* jobs specially.
There are still a few other images that look, from the name, like they
might be uncontrolled inputs into our CI, but they don't look risky.
Let's leave them for now.
|
| | |
| |
| |
| | |
So far only used by the cargo-audit job.
|
| |\ \
| |/
|/|
| |
| | |
Circuit reactor test cleanup
See merge request tpo/core/arti!2287
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| |/ |
|
| |\
| |
| |
| |
| | |
Use a pinned compiler version to run cargo audit
See merge request tpo/core/arti!2289
|
| | |
| |
| |
| |
| |
| | |
This invalidates the cache. This may not be strictly necessary, but
it will make sure that the new pinned image is used in the CI run *for
this MR*.
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This avoids CI failures like this
https://gitlab.torproject.org/nickm/arti/-/jobs/617654
arising from situations like this
cargo-audit install fails with rust 1.80
https://github.com/rustsec/rustsec/issues/1217
error[E0282]: type annotations needed for Box<_>
https://github.com/time-rs/time/issues/693
IMO we should pin many of the other images too but I suspect that may
be controversial. I'm hoping that pinning this one to get CI working
is uncontroversial (perhaps only on a temporary basis).
The other way to solve this would be to remove --locked which IMO is
going in the wrong direction, by exposing us to more rather than fewer
uncontrolled inputs from our upstreams.
|
| |\
| |
| |
| |
| | |
Fix new warnings from nightly clippy
See merge request tpo/core/arti!2288
|
| | |
| |
| |
| |
| | |
(This will either become used later, or we will remove it;
the TODO RPC will remind us.)
|
| | |
| |
| |
| |
| |
| |
| | |
This warning suggests using `[a,b]` as a Pattern
when it sees a search for `|ch| ch == a || ch == b`.
(All of our supported rust versions allow this kind of Pattern.)
|
| |/
|
|
|
| |
This warning complains when we say `where T: SomeTrait + ?Sized`
when `SomeTrait` is inherently Sized.
|
| |\
| |
| |
| |
| | |
rpclib: Use i64 rather than u64 for request IDs.
See merge request tpo/core/arti!2279
|
| | |
| |
| |
| | |
This makes it conform to the spec and match arti-rpcserver.
|