| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| |
|
|
| |
Due to precedence, both work the same, but the former is preferred.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
"Black" is an "opinionated" python formatter, whose opinionatedness
is somewhat in the spirit of rustfmt.
This MR runs black with default settings on all of our python code
in Arti. It was produced by the following commands
```
# Everything in python/
black python/
# Everything with a .py extension
fd '.py$' -X black
# Everything with a python shebang.
git grep -l '#! */usr/bin/env *python' | xargs black
```
|
| | |
|
| |
|
|
|
| |
Additionally, document that this tool requires particular versions
of nightly, since the rustdoc json format is unstable.
|
| | |
|
| |
|
|
| |
This is very useful when iterating through CI.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
This new feature lets us provide the "enable these options which are
needed to make the tests pass" featrure, which is different for each
of the afflicted crates. Then we can test these crates
tor-hsservice
arti
arti-client
which minimal features.
This will be important in a moment, as we're going to want to be
relying on actually minimal features tests in arti cfg.rs.
|
| | |
|
| | |
|
| |\
| |
| |
| |
| | |
Python tool to build RPC method/type documentation.
See merge request tpo/core/arti!2479
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
Uses the RPC library to extract a list of RPC methods and objects;
uses rustdoc-nightly to extract documentation for them;
outputs a markdown document.
|
| | |
| |
| |
| |
| | |
Prompted by
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/2488#note_3087164
|
| | | |
|
| |/ |
|
| |\
| |
| |
| |
| |
| |
| | |
tor-llcrypto: replace simple_asn1 dependency with der-parser
Closes #1632
See merge request tpo/core/arti!2462
|
| | | |
|
| |/ |
|
| | |
|
| | |
|
| |
|
|
| |
This will allow us to upgrade to the latest version of rusqlite.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Adding an exception for now, as per #1608
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fixes the `minimal-versions` failure:
```
error: package ID specification `[email protected]` did not match any packages
Did you mean one of these?
[email protected]
```
(we don't actually need to un-downgrade `futures-lite` anymore)
But we *do* need to un-downgrade `event-listener`
(`async-global-executor` needs `event_listener::EventListener` to be `UnwindSafe`,
and in `event-listener 3.0.0`, they are not)
|
| | |
|
| | |
|
| |\
| |
| |
| |
| |
| |
| | |
Fix reproducible build CI job for macOS
Closes #1394 and #1507
See merge request tpo/core/arti!2377
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
osxcross tries in various ways to detect which version of the compiler
we have, which version of the OS, which C++ standard library we use, and
many other things. With this variable set, osxcross seems able to detect
the environment provided by the SDK that we use.
The error messages from osxcross is as follows:
osxcross: error: cannot find libc++ headers
osxcross: error: while detecting target
This origins from its internal target detection code in target.cpp of
osxcross. This file contains a signficant amount of the detection for
paths of different versions of the macOS SDK's and macOS versions. All
of this is truly cursed.
In osxcross's main.cpp, the variable is read in:
if (char *p = getenv("MACOSX_DEPLOYMENT_TARGET")) {
target.OSNum = parseOSVersion(p);
unsetenv("MACOSX_DEPLOYMENT_TARGET");
}
and setting it thus forces the OS version to be parsed from the variable
instead of its (in our case failed) attempt at detecting the version
itself.
Fixes: tpo/core/arti#1394
|
| | | |
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | | |
Run tests of every crate, with all features disabled
See merge request tpo/core/arti!2350
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
We can't do this for every crate.
I looked at what is now matrix-check to see if I wanted to use any of
the code. But it seems too entangled with its particular purpose, and
has a lot of embedded knowledge of our crates' features. I found it
sufficiently far from what I wanted that I decided on a fresh script.
|
| | |/
| |
| |
| |
| | |
There's a TODO asking for `check` to be changed to `test`. And we're
about to invent a thing that does, sort of, the `test`.
|
| |/ |
|
| |
|
|
|
| |
Now that it's gone, we no longer need to bless its MPL-2.0 usage
or excuse it from cargo-audit.
|
| |\
| |
| |
| |
| |
| |
| | |
Test cbindgen correctness in CI
Closes #1502
See merge request tpo/core/arti!2320
|
| | |
| |
| |
| | |
Previously it didn't actually fail if there was a change.
|
| |\ \
| |/
|/|
| |
| | |
Add a few more tor employes to exclude from our acknowledgments
See merge request tpo/core/arti!2306
|
| | |
| |
| |
| |
| |
| | |
(Our practice has been that after one or two release cycles,
employees get left off the list of "thanks" in the changelog,
and instead get counted as among the people _doing_ the thanking.)
|
| | |
| |
| |
| |
| | |
The module is correctly documented as "only available on crate feature
restricted-discovery" without it.
|
| | |
| |
| |
| |
| | |
The script isn't handling the `cfg_attr` on `pub mod restricted_discovery`
very well, so we need to use the `additional_required` escape hatch.
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This makes the script work on `cfg_attr`s applied to `mod` declarations
ending in `;`.
Without this change, the script fails with
```
processing tor-hsservice
res += fn(os.path.join(dir_, file))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/builds/nickm/arti/./maint/check_doc_features", line 112, in extract_cfg_attr
end = min(subline.find(pat) for pat in ' (<' if subline.find(pat) !=-1)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
ValueError: min() arg is an empty sequence
```
when run on code with `cfg_attr`s applied to `mod` declarations.
Note: this change just improves the UX a bit, but doesn't actually fix
the issue: the script still isn't able to handle `cfg_attr`'d `mod`s: it
assumes all `#[cfg_attr(docsrs, ..)]` statements are applied to
feature-gated `pub use`s, and if there aren't any (such as in the case
of `cfg_attr`d modules, it assumes the feature gating is missing.
|
