mirrors/arti.git/crates/tor-hsrproxy, branch arti-v1.4.3mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.4.32025-05-01T16:22:28Zrelease: Bump all unstable tor/arti crates to 0.30.02025-05-01T16:22:28ZWesley Aptekar-Casselsme@wesleyac.com2025-05-01T15:55:57Zurn:sha1:770aaa9648d42835b2c6b3b29f4051d287ddba88
```
for crate in $(./maint/list_crates | rg '^(tor|arti-)'); do
cargo set-version -p $crate 0.30.0
done
```
chore: Run fixup-features.2025-04-30T15:49:52ZWesley Aptekar-Casselsme@wesleyac.com2025-04-30T14:26:40Zurn:sha1:da4308744bf59b50dfcc28a438fda047a115812d
cargo run -p fixup-features -- --exclude examples/ --exclude maint/ Cargo.toml
The following features in arti-ureq were manually added to full or
marked non-additive:
* rustls
* native-tls
* tokio
* async-std
metrics: Discuss schema stability (currently, "no")2025-04-08T17:20:50ZIan Jacksonijackson@chiark.greenend.org.uk2025-04-08T12:17:17Zurn:sha1:63b1afba93c24519c20e95229e894d3e91cc658ator-hsrproxy: config: make ProxyActionDiscriminants private2025-04-08T17:20:50ZIan Jacksonijackson@chiark.greenend.org.uk2025-04-08T12:05:07Zurn:sha1:0818b110e24b573a217dac6c73e8ff1db31eb6fd
beta clippy pointed out that it shouldn't be exhaustive.
but `#[strum_discriminants(non_exhaustive)]` is rejected.
metrics: tor-hsrproxy: Use a bespoke type for counter outcomes2025-04-08T17:20:50ZIan Jacksonijackson@chiark.greenend.org.uk2025-04-08T11:50:17Zurn:sha1:e02da4600e7a66bee5ac3dc57b708c0942bda895
Prompted by
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/2918#note_3185872
tor-hsrproxy: Add allow(unused) if features not all enabled2025-04-08T17:20:50ZIan Jacksonijackson@chiark.greenend.org.uk2025-04-07T15:44:40Zurn:sha1:a02715d099d386a67c7a7db7702c2499df50d636
This avoids warnings from failure to cfg-decorate imports.
tor-hsrproxy: Export a connection count metric (fmt)2025-04-08T17:20:50ZIan Jacksonijackson@chiark.greenend.org.uk2025-04-02T16:23:22Zurn:sha1:016bcdbe6e93d7a565e33640c1363d5a79c7472dtor-hsrproxy: Export a connection count metric2025-04-08T17:20:50ZIan Jacksonijackson@chiark.greenend.org.uk2025-04-02T16:21:39Zurn:sha1:e9ee2f4204b5139de9946d86c942b6e62427f258
This proves the concept. Many more metrics will need to be added
throughout the codebase.
With this compiled in and enabled, I see this with curl:
> ```
> # TYPE arti_hss_proxy_connections_failed_total counter
> arti_hss_proxy_connections_failed_total{nickname="ztest",action="destroy_circuit"} 0
> arti_hss_proxy_connections_failed_total{nickname="ztest",action="ignore_stream"} 0
> arti_hss_proxy_connections_failed_total{nickname="ztest",action="forward"} 0
> arti_hss_proxy_connections_failed_total{nickname="ztest",action="reject_stream"} 0
>
> # TYPE arti_hss_proxy_connections_total counter
> arti_hss_proxy_connections_total{nickname="ztest",action="reject_stream"} 0
> arti_hss_proxy_connections_total{nickname="ztest",action="forward"} 1
> arti_hss_proxy_connections_total{nickname="ztest",action="destroy_circuit"} 0
> arti_hss_proxy_connections_total{nickname="ztest",action="ignore_stream"} 0
>
> # TYPE arti_hss_proxy_connections_ok_total counter
> arti_hss_proxy_connections_ok_total{nickname="ztest",action="destroy_circuit"} 0
> arti_hss_proxy_connections_ok_total{nickname="ztest",action="reject_stream"} 0
> arti_hss_proxy_connections_ok_total{nickname="ztest",action="ignore_stream"} 0
> arti_hss_proxy_connections_ok_total{nickname="ztest",action="forward"} 1
> ```
tor-hsrproxy: formatting in Cargo.toml2025-04-08T17:20:50ZIan Jacksonijackson@chiark.greenend.org.uk2025-04-02T16:21:28Zurn:sha1:24795f502baf522d20d79646fcd0e12691f202a0tor-hsrproxy: Move cloning into spawn2025-04-08T17:20:50ZIan Jacksonijackson@chiark.greenend.org.uk2025-04-02T14:25:17Zurn:sha1:65d8df00f87e70673cd46df699db71a66998e8aa
This means that we can use the same variable names for the clones,
which is considerably less confusing.