[lldb] Implement delayed breakpoints
This patch changes the Process class so that it delays *physically*
enabling/disabling breakpoints until the process is about to
resume/detach/be destroyed, potentially reducing the packets transmitted
by batching all breakpoints together.
Most classes only need to know whether a breakpoint is "logically"
enabled, as opposed to "physically" enabled (i.e. the remote server has
actually enabled the breakpoint). However, lower level classes like
derived Process classes, or StopInfo may actually need to know whether
the breakpoint was physically enabled. As such, this commit also adds a
"IsPhysicallyEnabled" API.
https://github.com/llvm/llvm-project/pull/192910
[lldb][NFC] Move BreakpointSite::IsEnabled/SetEnabled into Process
The Process class is the one responsible for managing the state of a
BreakpointSite inside the process. As such, it should be the one
answering questions about the state of the site.
https://github.com/llvm/llvm-project/pull/192910
[libc++][NFC] Remove `pointer_traits<__wrap_iter>` partial specialization (#178864)
Since commit b5270ba20dc3d84df9d880be11d57667f04c6c28, it was decided
that `__wrap_iter` wasn't intended to perform runtime check, so it's
`operator->` won't check whether the iterator is deferenceable. (See
https://llvm.org/PR178521.)
Currently, `pointer_traits<__wrap_iter>` partial specialization is
provided and makes `__to_address`/`to_address` call the member
`to_address` instead of `operator->`. But given these operations are
equivalent and `__wrap_iter::operator->` is improbable to have
behavioral change in the future, perhaps it would be better to remove
the partial specialization.
The changes have no negative impact on compile time, and sometimes have
a negligible positive impact.
Drive-by: Also remove inclusion of `<__memory/addressof.h>` from
`<__iterator/wrap_iter.h>` as we don't need to call `addressof` or its
equivalent internal version.
[IR] LangRef: document behavior of double-lifetime.start (#184296)
lifetime.start after lifetime.start is defined to reset the contents of the
allocation to uninitialized memory.
[lldb][NFC] Move BreakpointSite::IsEnabled/SetEnabled into Process
The Process class is the one responsible for managing the state of a
BreakpointSite inside the process. As such, it should be the one
answering questions about the state of the site.
https://github.com/llvm/llvm-project/pull/192910
[KnownBits][APInt] Optimize isConstant (NFC) (#191919)
`isConstant` used is quite often and should be as lightweight as
possible. Add `APInt::isInverseOf` and utilize it for `isConstant`. It
is equivalent to `LHS == ~RHS`, but avoids intermediate allocations.
py-test-codspeed: updated to 4.4.0
4.4.0
We now collect buildtime and runtime environment data to warn users about differences in their runtime environment when comparing two runs against one another.
This data includes toolchain metadata like version and build options, as well as a list of dynamically loaded linked libraries.
fix: fix segfault caused by multiple activate_stack_trampoline
fix: Exclude setup time from benchmark in walltime mode
feat: collect Python toolchain information via instrument hooks environment API
md4c: updated to 0.5.3
0.5.3
Changes:
* Avoid repeated prefix `language-` in code block language specification if
the input already explicitly includes the prefix.
Contributed by [Zach Newton](https://github.com/znewt99).
* Permissive autolink extensions (`MD_FLAG_PERMISSIVExxxAUTOLINKS`) are now
tiny bit more permissive, allowing `+` and `-` characters to be anywhere
in the path portion of the URL. This also improves compatibility with GFM.
* Make Unicode-specific code compliant to Unicode 18.0.
Fixes:
[30 lines not shown]
Load auth_rpcgss at boot to fix Kerberos NFS after manual start
gssproxy writes 1 to `/proc/net/rpc/use-gss-proxy` once at startup. If
the proc file doesn't exist yet (`auth_rpcgss` not loaded), it silently
gives up. v0.9.2 adds a 10-second retry timer for this case,
but TrueNAS ships v0.9.1.
When NFS is started manually with auto-start disabled, `gssproxy` has
already started and given up. The kernel's `use_gss_proxy` flag stays -1
and the first Kerberos client locks it to 0 (one-shot latch), breaking
`RPCSEC_GSS` until reboot. Loading `auth_rpcgss` early ensures the proc
file exists before gssproxy starts.
Tested with NFS auto-start disabled and rebooting. Before fix,
`use-gss-proxy` stayed -1 after manual NFS start and a raw
`RPCSEC_GSS_INIT` request locked it to 0. After fix, `use-gss-proxy`
is 1.
(cherry picked from commit f592af1014970a81a98b7a03052c2b7fdc557380)
(cherry picked from commit eb0cd965ec7795ede47665fd93dc8f5e7bf793a1)
net/xfr: update to 0.9.8
[0.9.8] - 2026-04-17
Added
Separate send/recv reporting in bidir tests (issue #56) — --bidir now reports per-direction bytes and throughput in the summary instead of just the combined total, which was useless on asymmetric links. Plain text shows Send: X Recv: Y (Total: Z); JSON adds bytes_sent, bytes_received, throughput_send_mbps, throughput_recv_mbps; CSV gets four new columns; TUI shows ↑ X / ↓ Y in the throughput panel. Unidirectional tests are unchanged (the existing bytes_total/throughput_mbps is already the single-direction number).
Fixed
Fast, accurate TCP teardown (issue #54) — replaced the blocking shutdown() drain on the send path with SO_LINGER=0 on Linux, so cancel and natural end-of-test no longer wait for bufferbloated send buffers to ACK through rate-limited paths. Fixes the "Timed out waiting 2s for N data streams to stop" warning matttbe reported with -P 4 --mptcp -t 1sec.
Sender-side byte-count accuracy — stats.bytes_sent is now clamped to tcpi_bytes_acked before abortive close, removing a quiet ~5-10% overcount where the send-buffer tail discarded by RST was being reported as transferred. Download and bidir tests are the primary beneficiaries.
macOS preserves graceful shutdown — non-Linux platforms lack tcpi_bytes_acked, so the Linux abortive-close path is cfg-gated; other platforms still use shutdown() for accurate accounting.
[0.9.7] - 2026-04-16
Added
Early exit summary (issue #35) — Ctrl+C now displays a test summary with accumulated stats instead of silently exiting. Works in both plain text and TUI modes. Double Ctrl+C force-exits immediately.
DSCP server-side propagation — --dscp flag is now sent to the server and applied to server-side TCP/UDP sockets for download and bidirectional tests. Previously only client-side sockets were marked.
Non-Unix --dscp warning — platforms without socket TOS support now show a visible warning before the test starts, instead of silently no-oping.
[10 lines not shown]
net/termscp: update to 1.0.0
Released on 2026-04-18
Added
rework TransferProgress to track bytes with lazy estimation
replace dual progress bar components with single TransferProgressBar
simplify progress bar layout to single component
update progress bar display for new unified data model
update transfer loop to use unified TransferProgress
consolidate theme progress bar fields into single transfer_progress_bar
CI
Codeberg mirroring
run test workflows once
check fmt with nightly toolchain
add linux and windows aarch64 build targets
[132 lines not shown]
shells/starship: update to 1.25.0
1.25.0 (2026-04-18)
Features
add Maven module (#7189) (70b0f73)
add statusline subcommand for Claude Code integration (#7234) (b8ee821)
battery: Update default unknown_symbol (#7278) (88d384f)
directory: add support for regexes in substitutions (#7145) (2e8f26e)
env_var: include $symbol in default format (#7262) (3885e81)
git_status: add variables to track worktree and index changes (#5655) (0110bf5)
python: add option to replace generic venv-names with parent dir (#7112) (083ab00)
vcs: Introduce the VCS module (#6388) (0dd5a4f)
Bug Fixes
aws: isolate tests from host AWS config files (#7196) (e910f47)
aws: support $duration for sso_session (#7100) (8108cc9)
direnv: accept null loadedRC state (#7317) (56b8901)
[6 lines not shown]
finance/rex: update to 0.2.6
Updates
Improve start up time to near instant by moving update checker to a separate thread
Changes
Update checker by @TheRustyPickle in #127
Version bump by @TheRustyPickle in #128
NAS-140626 / 27.0.0-BETA.1 / Prevent duplicate device attachment on VMs and containers (#18763)
## Problem
Currently, users can add the same USB or PCI device multiple times to
the same VM or container. This results in duplicate device assignments,
causing libvirt to fail with an error during startup.
## Solution
Added validation to ensure device uniqueness for both libvirt devices.
A validation error is now raised if the same device is added more than
once to a VM or container, preventing invalid configurations.
[mlir] targeted verification for transform "inlining"
When merging named transform sequences into their include locations,
rely on the InlinerDialectInterface implementation newly added to the
transform dialect instead of the full verification after the fact. This
enables us to only verify aspects of the IR that may change in a way
compatible with the rest of the infra, reducing the overall cost of the
process.
