| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
The affected crates follow our regular versioning.
They all get bumped to 0.26.0.
Done with
```
for crate in $(./maint/list_crates |grep '^arti-\|tor-' ); do
cargo set-version --bump minor -p $crate;
done
```
|
| |\
| |
| |
| |
| | |
clippy: deny `mod_module_files`
See merge request tpo/core/arti!2689
|
| | |
| |
| |
| |
| |
| | |
Denies 'mod.rs' files for consistency.
https://rust-lang.github.io/rust-clippy/master/index.html#mod_module_files
|
| | | |
|
| |\ \
| |/
|/|
| |
| |
| |
| | |
rpc-connect: Remove cfg(unix) of SYSTEM_DEFAULT_CONNECT_POINT
Closes #1776
See merge request tpo/core/arti!2667
|
| | |
| |
| |
| |
| |
| |
| | |
When we switched this definition to use `cfg_if`,
we overlooked the `#[cfg(unix)]`.
Fixes #1776.
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| | |
This lets us bail when another process has bound to our connect
point, rather than blocking indefinitely.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Grab an associated lock file...
- ... then delete the socket file (if it's present) ...
- ... then bind to it.
On exit:
- remove the socket
- then drop the lock.
|
| | | |
|
| |/ |
|
| | |
|
| | |
|
| |
|
|
|
| |
(We want a separate read and write socket before we return,
and once we've done the type-erasure, we can't do try_clone().)
|
| | |
|
| |
|
|
|
|
|
|
| |
In 1.83, this warning triggers on many of our crates.
We're thinking of fixing them all, but for now,
we're going to disable the warning.
This is part of #1765.
|
| |
|
|
|
|
|
|
|
|
| |
Done using:
```
for crate in $(./maint/list_crates | rg '^(tor|arti-)'); do
cargo set-version -p $crate 0.25.0
done
```
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The non-{arti-,tor-} crates are:
```
./maint/list_crates | rg -v '^(tor|arti)'
oneshot-fused-workaround
slotmap-careful
test-temp-dir
fslock-guard
hashx
equix
caret
fs-mistrust
safelog
retry-error
```
We split them in the following categories:
* crates with no changes (no version bumps):
```
maint/changed_crates -v "arti-v$LAST_VERSION" 2>&1 >/dev/null | grep -i "no change" | grep -v '\(tor\|arti\)-'
oneshot-fused-workaround: No change.
test-temp-dir: No change.
caret: No change.
```
* crates that only have non-functional changes (bump the patch version):
- slotmap-careful
- fslock-guard
- hashx
- equix
- fs-mistrust
- safelog
- retry-error
* crates where APIs were broken (bump minor):
None
The bumps from this commit were created using this script:
```
PATCH="
slotmap-careful
fslock-guard
hashx
equix
fs-mistrust
safelog
retry-error
"
for crate in $PATCH; do
cargo set-version --bump patch -p $crate;
done
```
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
("Server support" here means binding to a socket and reading a
cookie file.)
|
| |
|
|
|
| |
("Client support" here means connecting to a socket and reading a
cookie file.)
|
| | |
|
| |
|
|
|
| |
In particular, we only allow binding/connecting to localhost,
and we only support None auth for Unix connections.
|
| |
|
|
| |
The cookie authentication protocol will need these.
|
| |
|
|
| |
(Cookie authentication is described in rpc-cookie-sketch.md)
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
While doing so, tidy up the errors that we detect when parsing
a connect point, so that we can differentiate ones that indicate an
unsupported connect-point type.
This means that fewer types now implement Deserialize;
that's probably a good thing.
|
|
|
See doc/dev/rpc-book/src/rpc-connect-sketch.md for details.
|
