devel/llvm??: remove libxml2 discovery
In commit af979dd126ff4 the dependency on libxml2 was removed. But
libxml2 was still found for LLDB and used if it was present at configure
time.
PR: 295076
Submitted by: laurent
[VPlan] Assert that replacement types match in VPUser::setOperand (NFC). (#195891)
Add assertion to VPValue::setOperand to check if types of the new
operand matches the old operand.
This makes it easier to catch replacements with incorrect types at the
source, instead only later during verification.
A few places currently preform replacements with mis-matching types,
which only get fixed up later. Update those to avoid type-violation.
Depends on https://github.com/llvm/llvm-project/pull/195485
PR: https://github.com/llvm/llvm-project/pull/195891
sound: Remove SV_ABI_LINUX ifdef
This ifdef does not do anything, SV_ABI_LINUX is a flag.
Sponsored by: The FreeBSD Foundation
MFC after: 1 week
Reviewed by: ivy, brooks
Pull-Request: https://ron-dev.freebsd.org/FreeBSD/src/pulls/37
ansible: updated to 13.7.0
13.7.0
Major Changes
grafana.grafana
- Run molecule only when required
- migrate stack create/update/delete to stacks-api
netapp.ontap
- Updated ONTAP personality check functionality.
- na_ontap_debug - AWS Lambda support added to the module.
- na_ontap_dns - AWS Lambda support added to the module.
- na_ontap_domain_tunnel - AWS Lambda support added to the module.
- na_ontap_efficiency_policy - AWS Lambda support added to the module.
- na_ontap_export_policy - AWS Lambda support added to the module.
[19 lines not shown]
[mlir][IR] Require token producer and consumer traits
Add marker traits for operations that intentionally produce or consume the
builtin token type. The verifier now rejects token results without
TokenProducerTrait, token operands without TokenConsumerTrait, token entry
block arguments whose parent op does not produce tokens, and token block
arguments outside entry blocks.
Extend the Test dialect token ops to cover valid opt-in cases and each
verifier rejection path.
Assisted-by: Codex
mvc: remove grouped ModelRelationField option handling (#10339)
The group option collapsed multiple related model rows into a single
display entry while still storing the UUID of one concrete source row.
This makes the selected relation dependent on iteration order and is not
a stable representation of the grouped object.
References:
https://github.com/opnsense/core/commit/fe571ac442efe76c3a1efd3e6f90b8ec4cb6e7bd
Frr was the only consumer (I could grep in core and plugins, don't know if external ones exist), I reworked how the relationship is displayed there to make it more obvious to the user how items relate to each other, and also prevent that the wrong items get deleted. Configs should be more coherent now.
It's also not perfect, but more "obvious" lets say.
It also helps with the addition of internalModelUseSafeDelete in FRR.
opnsense/plugins at 0798cde
opnsense/plugins at d3c3e79
opnsense/plugins at cb9a5d6
NAS-141020 / 26.0.0-RC.1 / Restrict on-disk perms of internal container/apps dataset roots (by anodos325) (#18986)
The internal dataset trees that back containers
(/mnt/.truenas_containers/), Docker apps (/mnt/.ix-apps/), and the
per-container idmapped bind-mount parent (/run/truenas_containers/root/)
are implementation-detail paths that aren't intended to be inspected
directly by host users. They currently mount with the default of
drwxr-xr-x root:root (or 0755 from os.makedirs for the /run parent),
which is looser than necessary.
This PR pins those three directories to 0700 root:root and re-applies
the mode at the relevant entry points so the property is idempotent
across reboots and manual chmod drift.
Original PR: https://github.com/truenas/middleware/pull/18954
Co-authored-by: Andrew Walker <andrew.walker at truenas.com>
NAS-141020 / 27.0.0-BETA.1 / Restrict on-disk perms of internal container/apps dataset roots (#18954)
The internal dataset trees that back containers
(/mnt/.truenas_containers/), Docker apps (/mnt/.ix-apps/), and the
per-container idmapped bind-mount parent (/run/truenas_containers/root/)
are implementation-detail paths that aren't intended to be inspected
directly by host users. They currently mount with the default of
drwxr-xr-x root:root (or 0755 from os.makedirs for the /run parent),
which is looser than necessary.
This PR pins those three directories to 0700 root:root and re-applies
the mode at the relevant entry points so the property is idempotent
across reboots and manual chmod drift.
(cherry picked from commit 0d5d2481b7aae7045e0ca7f6375656a301be0d68)
NAS-141020 / 27.0.0-BETA.1 / Restrict on-disk perms of internal container/apps dataset roots (#18954)
The internal dataset trees that back containers
(/mnt/.truenas_containers/), Docker apps (/mnt/.ix-apps/), and the
per-container idmapped bind-mount parent (/run/truenas_containers/root/)
are implementation-detail paths that aren't intended to be inspected
directly by host users. They currently mount with the default of
drwxr-xr-x root:root (or 0755 from os.makedirs for the /run parent),
which is looser than necessary.
This PR pins those three directories to 0700 root:root and re-applies
the mode at the relevant entry points so the property is idempotent
across reboots and manual chmod drift.
(cherry picked from commit 0d5d2481b7aae7045e0ca7f6375656a301be0d68)
[RISCV][TTI] Model broadcast loads as zero-stride loads (#198446)
We have done this optimization in ISel and this PR just models it
in TTI.
---------
Co-authored-by: Luke Lau <luke_lau at icloud.com>
