CVS commit: pkgsrc/net/xfr

["pin" <pin%netbsd.org@localhost>]

Module Name:    pkgsrc
Committed By:   pin
Date:           Fri May  1 15:45:09 UTC 2026

Modified Files:
        pkgsrc/net/xfr: Makefile cargo-depends.mk distinfo

Log Message:
net/xfr: update to 0.9.11

UDP TUI clarity. Two issues from real users — @brettowe (#70) and @pythonwood (#72) — pointed at the same weakness: the running TUI was confusing about what its UDP numbers meant. This release 
rewires the live data path so the values you see during a test match what the test actually saw.
Fixed

    Live UDP packet-loss counter during the run (#70) — the Packet Loss line was stuck at 0.0% for the entire test and only updated to the real value at completion. With -t 0 (infinite mode) the real 
value was never visible. Server now ships cumulative UdpIntervalProgress { packets_received, packets_lost } on every Interval message; client derives the percent locally and the TUI updates it live. 
Reported by @brettowe.
    Final UDP loss accounting only counts valid xfr packets — UdpStats.packets_received and packets_sent now exclude short, malformed, or foreign datagrams that can't be header-decoded. Previously 
such datagrams inflated packets_received and silently understated the final loss percent.

Added

    Throughput sparkline tints by per-interval loss severity (#70) — clean intervals stay the graph color, light loss (<1% per-interval rate) tints warning, heavy loss (≥1%) tints error. A 
single-packet hiccup and a heavy drop burst no longer collapse to the same flat tint. Magnitude unknown stays the graph color — honest "no signal."
    Freshness signal for the Packet Loss line — renders dimmed --% when paired against a pre-0.9.11 server or before any UDP traffic has been observed, so unknown is visually distinct from a fresh 
0.0% reading.

Changed

    Jitter rolling-window label (#72) — the running display now reads Jitter: 0.86 ms (10s avg: 0.03 ms). The previous (10s: …) form read like a stuck timer; @pythonwood opened an issue thinking the 
display was broken on a v0.9.10-client → v0.9.6-server pairing.

Wire-protocol note

AggregateInterval gains an optional udp_progress field (raw counts, not a derived percent — the client owns the math). Cross-version compatibility preserved with serde(default, skip_serializing_if = 
"Option::is_none"). Verified for both 0.9.10 ↔ 0.9.11 directions in tests; pythonwood's mismatched-version pairing in #72 is a deliberate compat target.


To generate a diff of this commit:
cvs rdiff -u -r1.9 -r1.10 pkgsrc/net/xfr/Makefile \
    pkgsrc/net/xfr/cargo-depends.mk pkgsrc/net/xfr/distinfo

Please note that diffs are not public domain; they are subject to the
copyright notices on the relevant files.

Modified files:

Index: pkgsrc/net/xfr/Makefile
diff -u pkgsrc/net/xfr/Makefile:1.9 pkgsrc/net/xfr/Makefile:1.10
--- pkgsrc/net/xfr/Makefile:1.9 Thu Apr 23 13:14:25 2026
+++ pkgsrc/net/xfr/Makefile     Fri May  1 15:45:09 2026
@@ -1,6 +1,6 @@
-# $NetBSD: Makefile,v 1.9 2026/04/23 13:14:25 pin Exp $
+# $NetBSD: Makefile,v 1.10 2026/05/01 15:45:09 pin Exp $
 
-DISTNAME=      xfr-0.9.10
+DISTNAME=      xfr-0.9.11
 CATEGORIES=    net
 MASTER_SITES=  ${MASTER_SITE_GITHUB:=lance0/}
 GITHUB_TAG=    v${PKGVERSION_NOREV}
Index: pkgsrc/net/xfr/cargo-depends.mk
diff -u pkgsrc/net/xfr/cargo-depends.mk:1.9 pkgsrc/net/xfr/cargo-depends.mk:1.10
--- pkgsrc/net/xfr/cargo-depends.mk:1.9 Thu Apr 23 13:14:25 2026
+++ pkgsrc/net/xfr/cargo-depends.mk     Fri May  1 15:45:09 2026
@@ -1,4 +1,4 @@
-# $NetBSD: cargo-depends.mk,v 1.9 2026/04/23 13:14:25 pin Exp $
+# $NetBSD: cargo-depends.mk,v 1.10 2026/05/01 15:45:09 pin Exp $
 
 CARGO_CRATE_DEPENDS+=  adler2-2.0.1
 CARGO_CRATE_DEPENDS+=  aho-corasick-1.1.4
Index: pkgsrc/net/xfr/distinfo
diff -u pkgsrc/net/xfr/distinfo:1.9 pkgsrc/net/xfr/distinfo:1.10
--- pkgsrc/net/xfr/distinfo:1.9 Thu Apr 23 13:14:25 2026
+++ pkgsrc/net/xfr/distinfo     Fri May  1 15:45:09 2026
@@ -1,4 +1,4 @@
-$NetBSD: distinfo,v 1.9 2026/04/23 13:14:25 pin Exp $
+$NetBSD: distinfo,v 1.10 2026/05/01 15:45:09 pin Exp $
 
 BLAKE2s (adler2-2.0.1.crate) = 4d391e0fcde91c7435ee9a5503fee4a5346f549f1b45e482ce3e1e151d90f8f5
 SHA512 (adler2-2.0.1.crate) = 555b2b7ba6f8116acccd0bcd16ed34cc78162c81023cff31a8566ffcd456c03832089fca2d5b668ceaac4fe8f922d31aa9c487f226a36cace294ff4a219bd91d
@@ -1275,9 +1275,9 @@ Size (writeable-0.6.2.crate) = 25181 byt
 BLAKE2s (x509-parser-0.18.1.crate) = a5f2838a9880a6e075ead6b25c4078314403bbd5f9d59df631663b87ee4edee4
 SHA512 (x509-parser-0.18.1.crate) = a30af92885d157b837832b7a3242fc8dbe5eacbce97ce5cb92a8c5e948324ec38150ca709734eb191a914f4f34d4d521ba313b72a57541a62cb254e8808535ef
 Size (x509-parser-0.18.1.crate) = 102625 bytes
-BLAKE2s (xfr-0.9.10.tar.gz) = 4dff1da1677d54887ef257335abf93402e46a897e6930951f5d542528a8b3f2c
-SHA512 (xfr-0.9.10.tar.gz) = b133d61044b8890d18acdb846b7164ab914f8bcdfc16647dc5f61c35c33a24c0c4408f7df1397e418cfbc5dc723595c6a5cd2326d6f1a98433b7c906c72d6f9a
-Size (xfr-0.9.10.tar.gz) = 784738 bytes
+BLAKE2s (xfr-0.9.11.tar.gz) = a9416201c2fd553067d52d3d53fc1e29d9343dba26f509c7cf78afef626077c5
+SHA512 (xfr-0.9.11.tar.gz) = b214daa5a2314cbf47649b32284f1f98b1ffc400b149fa7d491185c5901bece02b822cdf588e1691fbabbbe7ef3da215d878e68cd5e76b5d3a19a8d0775c7921
+Size (xfr-0.9.11.tar.gz) = 793722 bytes
 BLAKE2s (yasna-0.5.2.crate) = 25391034f1d4c9715add3175629a012024dc2a34fa85b4dc85c4dce2c100742a
 SHA512 (yasna-0.5.2.crate) = 7532b6d06b34b0a5e2b769c5d2647f910bec481d98482bf9cea212f1bd1466336d7cb117d0c2e240e7673b2825f1d091619f79814bad836d25cf3a6ca2be63e5
 Size (yasna-0.5.2.crate) = 34859 bytes