Set the peer's ALUA group when LIO becomes ACTIVE
On takeover, set_alua_active() wrote only the local controller group.
The peer's group kept the value this node had given it while STANDBY,
ACTIVE/OPTIMIZED. Nothing else rewrote it until the peer came back,
reached lio_ha 'synced' and called refresh_alua_states() on this node.
Until then, REPORT TARGET PORT GROUPS advertised the down peer as the
optimized path. If that remote call failed, the wrong state stayed,
because the failure is only logged.
set_alua_active() now writes both groups. The local group becomes
OPTIMIZED, and the peer's group gets the state the ACTIVE node gives
for the current ha_state: NONOPTIMIZED when synced, UNAVAILABLE when
disconnected, otherwise TRANSITIONING.
refresh_alua_states() uses the same table, so the disconnected case now
writes UNAVAILABLE rather than TRANSITIONING. That matches the table in
utils/lio/config.py, so the reconciler and the event handlers no longer
disagree about the peer's state.
ipfw: declare the ipfw_nat module
The module declaration is necessary for 'kldstat -m' to see it,
and the rc(8) uses that to detect presence of ipfw_nat.
NB: the module(9) KPI lacks a way to declare a module without
providing an empty handler and no SYSINITs.
Reported by: ambrisko
Fixes: 9bcc1e97dda8e926483b81874884211bbe4f36e9
sysutils/py-datalad: fix build by changing dependency to git from git at lite
Some dependency changed git at lite to git and this caused a conflict.
Reported by: fallout
databases/immudb: Remove expired port
2026-10-27 databases/immudb: Not actively maintained. Multiple versions behind on upstream. Please take maintainership if you use this.
[ExecutionEngine] Return GV for binary ConstantExprs in getConstantValue (#236232)
This patch restores "return GV;" for Add, Sub, and Xor constant
expressions in ExecutionEngine::getConstantValue.
Commit 0ba7764723026882df1f302765b9aa848a56960c flattened the outer
type switch in the binary operator case of
ExecutionEngine::getConstantValue, accidentally keeping the inner
"break;" statement in place of "return GV;". Without this fix, GV is
never read, and Add, Sub, and Xor constant expressions fall through to
report_fatal_error.
Assisted-by: Antigravity
[HLSL] Use icmp ne instead of trunc on boolean load (resubmission) (#234771)
Corrects [PR #221105](https://github.com/llvm/llvm-project/pull/221105),
which was reverted due to buildbot failures. Some of the builders
reported an unsupported triple for
clang/test/CodeGenHLSL/bool-vector-load.hlsl, presumably due to a lack
of DirectX support; the test now checks the generic LLVM IR. Only the
RUN and CHECK lines of that test have changed from the earlier PR.
Fixes #140824
Assisted-by: Claude Sonnet 4
tex-pdfjam: add some missing dependencies
I tried to panelize a sticker for printing with this command and it
complained at run time about missing TeX packages:
$ pdfjam --paper a4paper --nup 2x6 --noautoscale true --delta "2mm 2mm" \
--frame true -o sheet.pdf sticker.pdf 1,1,1,1,1,1,1,1,1,1,1,1
[AMDGPU] Remove unreachable buildReduction from AtomicOptimizer (NFC) (#234082)
Since #211757 the pass uses wave.reduce unless the value is divergent
and the result is used. So the DPP scan always has a used result, and
buildReduction, which it only called for an unused one, can't be
reached. Drop it and the NeedResult check before buildShiftRight.
[AMDGPU] Fix a wave.reduce crash on a move of a non-immediate (#228819)
lowerWaveReduce checks whether a uniform source is the constant 1 by
looking at the move that defines it (#212755), and reads the move's
operand with getImm() without checking that it is an immediate. A source
defined by a move of a register, a frame index or a global address hits
the assertion in getImm(). An add reduction of a uniform umin's result
does this, since the umin is lowered to a move of its source.
Use getImmOrMaterializedImm, which returns nothing unless the operand is
an immediate.