pkgng/pkgng 2282f1dlibpkg pkg_repo.c

pkg_repo: Fix incompatible pointer

Fix incompatible variable pointer which causes compile to fail in Linux
systems.

Fix variable clevel_buf that was 'char **'' which is corrected type to 'char *'
DeltaFile
+1-1libpkg/pkg_repo.c
+1-11 files

FreeNAS/freenas 3181bdfsrc/middlewared/middlewared/plugins/zfs snapshot_crud.py, src/middlewared/middlewared/pytest/unit/utils/zfs test_guard.py test_no_second_registry.py

Consolidate the managed-dataset registries and guard every mutator

## Problem
"Is this a dataset middleware manages?" was answered by five separate registries with four membership sets and three matching algorithms: `INTERNAL_PATHS` in `plugins/zfs/utils.py`, `INTERNAL_DATASETS` in `plugins/pool_/dataset_query_utils.py`, `internal_datasets_filters` in `plugins/pool_/dataset.py`, inline literals in `alert/source/datasets.py`, and `INVALID_DATASETS` in `plugins/zettarepl.py`. None had unit coverage, and they had drifted: `<pool>/ix-applications` was creatable and then permanently invisible because one entry carried a trailing slash the others lacked, `<pool>/ix-apps-data` was hidden forever on a substring match, and the replication registry did not know about the apps datasets at all.

"May this caller change it?" was answered by a `bypass` field on seven public snapshot request models. It was declared `SkipJsonSchema`, which hides a field from the generated docs and JSON schema but does not block it at validation, so any caller holding `SNAPSHOT_WRITE` could send `bypass: true` and defeat every guard. `exclude_internal_paths` on `ZFSResourceQuery` was the same defect on the read side: any caller holding `ZFS_RESOURCE_READ` could enumerate every managed dataset, boot pool included. The root cause in both cases is that an authorization decision was encoded as request data -- a property of the caller modelled as a field of the request, on a model shared between the public method and the private one.

Separately, ten public mutators had no protection at all and none of them funnelled through a guarded implementation: `pool.dataset.promote`, `rename`, `set_quota`, `get_quota`, `lock`, `change_key` and `inherit_parent_encryption_properties`, both `zfs.tier` mutators, and `pool.snapshot.rename`. `promote` was the worst of them, since managed children are frequently clones and promoting one reparents its origin snapshot. `pool.snapshot.rename` turned out to be unreachable in any case: it passed a snapshot id to `zfs.resource.rename`, which rejects any name containing `@`, so the endpoint could not succeed for any valid input and had no test coverage.

## Solution
- **One registry, with shape as a first-class concept.** `utils/zfs/managed_datasets.py` holds the entries, and separates four things that are each edited in exactly one place: an *entry* (one table row), a *view* (a decision a caller makes), a *shape* (a matching strategy, bound per view in `VIEW_SHAPES`), and *drift* (per-cell overrides, quarantined and designed to be deleted). Retargeting a view onto a different shape is a one-line edit with no call-site changes, which is what makes the eventual convergence cheap.
- **Behaviour preserved exactly.** Each view keeps the matching algorithm its callers used before, so no listing changes and nothing is newly hidden or exposed. Converging the shapes would flip several unrelated consumers and is deliberately left as a follow-up; `SHAPE_OVERRIDES` holds the two cells that would have to go first. `.truenas_containers` keeps a row bound to the product listing only, reproducing today's behaviour while containers are addressed separately.
- **The override is off the wire.** `bypass` and `exclude_internal_paths` are gone from the public models and replaced by parameters on the `@private` implementations, which JSON-RPC cannot populate because it dispatches through the request model. The privilege is now a typed `InternalAccess` enum rather than a bool, so a stray value fails closed instead of silently permitting, and `InternalAccess.ALLOW` is a unique token that greps out the complete list of privileged callers. It is str-valued and coerced rather than identity-compared so it survives the JSON hop in `failover.call_remote`, which the audit dataset relies on. The fifteen owner call sites already passed `bypass=True`, so this is a rename rather than new burden. `v26_0_0` is left alone: the version adapter already drops fields absent from the newer model, and editing a frozen version would turn a silent drop into a hard failure for old clients.
- **Guards live at the chokepoint.** Protection sits inside the `@private` implementations, which every mutation passes through, rather than in each public method -- a missing guard at a public boundary fails open and silently, while a missing owner opt-in fails closed and loudly in that owner's own workflow. The four operations that have no chokepoint (quota, the two encryption operations, and tiering, which talks to an out-of-process daemon) are guarded at their public boundary instead, each as the first statement so the refusal precedes any lookup or feature check.
- **Gaps closed.** All ten unguarded mutators now refuse managed datasets, `pool.dataset.rename` also refuses a managed *destination* so a dataset can no longer be created at a protected name by renaming into it, `pool.dataset.delete` reports `EACCES` "is a protected path" instead of an errno-less "is an invalid location", and `pool.dataset.update` is protected explicitly rather than incidentally by the listing filter hiding its target and returning a misleading `ENOENT`. `pool.snapshot.rename` is routed at the snapshot rename endpoint and works. `mount` and `unmount` are deliberately left unguarded, with the reason recorded: they toggle visibility rather than changing content, and docker legitimately mounts the apps dataset. `replication.create_dataset` is likewise left unguarded, since replication is how users back up and restore the apps dataset and the target may be a remote system whose managed paths this one cannot reason about.
- **Coverage.** A truth table pins all six views across every shape edge, including the nested and prefix look-alikes the old registries disagreed on and one documented divergence on an input ZFS cannot produce. A scanner test blocks a sixth registry by matching dataset-name string literals -- including inside f-strings -- outside the registry module, and was checked to catch all five of the registries it replaces; its allowlist doubles as the convergence backlog and already records one hand-rolled membership test the audit had missed. Integration tests cover every guarded mutator against three managed datasets, with controls proving the guards reject nothing else.
DeltaFile
+271-0src/middlewared/middlewared/utils/zfs/managed_datasets.py
+225-0src/middlewared/middlewared/pytest/unit/utils/zfs/test_managed_datasets.py
+217-0tests/api2/test_internal_dataset_protection.py
+216-0src/middlewared/middlewared/pytest/unit/utils/zfs/test_no_second_registry.py
+60-46src/middlewared/middlewared/plugins/zfs/snapshot_crud.py
+94-0src/middlewared/middlewared/pytest/unit/utils/zfs/test_guard.py
+1,083-4642 files not shown
+1,641-33348 files

FreeBSD/ports d477151security/vuxml/vuln 2026.xml

security/vuxml: Fix giflib entry

The update to 6.1.3 already contains in files/ a patch for CVE-2026-26740 so use
lt instead of le to fix the version range.

PR:             296876
DeltaFile
+1-1security/vuxml/vuln/2026.xml
+1-11 files

LLVM/project 6886a6bflang/include/flang/Optimizer/Builder/Runtime Assign.h, flang/lib/Optimizer/Builder/Runtime Assign.cpp

[flang] - Call _FortranAAssignSimple instead of _FortranAAssign for intrinsic-type array assignments.

This patch adds support for calling _FortranAAssignSimple, a faster-path for array assignments.
`_FortranAAssignSimple` is called when ALL the following conditions are true:
1. Intrinsic element type (not derived type)
2. Matching ranks (no scalar-to-array broadcasting)
3. Non-volatile
4. Not polymorphic
5. Not explicit-length character
6. Not temporary LHS

Otherwise, uses `_FortranAAssign` (or specialized variants like `_FortranAAssignPolymorphic`, `_FortranAAssignExplicitLengthCharacter`).

This is a (perhaps final) part of the fix for https://github.com/llvm/llvm-project/issues/203915
DeltaFile
+287-0flang/test/HLFIR/assign-simple-routing.fir
+46-4flang/lib/Optimizer/HLFIR/Transforms/ConvertToFIR.cpp
+19-13flang/lib/Optimizer/OpenMP/LowerWorkdistribute.cpp
+13-0flang/lib/Optimizer/Builder/Runtime/Assign.cpp
+12-0flang/include/flang/Optimizer/Builder/Runtime/Assign.h
+2-2flang/test/HLFIR/assign-codegen.fir
+379-192 files not shown
+381-218 files

LLVM/project 5bf5520flang-rt/lib/runtime assign.cpp

more formatting fixes
DeltaFile
+3-3flang-rt/lib/runtime/assign.cpp
+3-31 files

LLVM/project 89f2b93clang/lib/StaticAnalyzer/Core ExprEngineCXX.cpp

[analyzer] Fix fragile logic in VisitCXXNewExpr (#213678)

This part of the engine code had assumed that an `evalBind` call always
produced exactly one transition. This was probably always satisfied by
the existing `eval::Bind` checkers (because the code is old and I don't
know about any bugs caused by this), but it was still fragile and
problematic to rely on this undocumented property of checkers.

This commit introduces a `for` loop to ensure that all nodes produced by
`evalBind` are handled in an identical manner (the same way as the
single node was handled previously).

(Note that not passing a `State` to `makeNodeWithBinding` is equivalent
to passing the state of the predecessor node.)

We noticed this problem during the review of the NFC commit
53ee7b167d8aee0a75c1332ca4a6aa037e0869a0 and decided to put this
(arguably non-NFC) change into a separate PR.
DeltaFile
+5-5clang/lib/StaticAnalyzer/Core/ExprEngineCXX.cpp
+5-51 files

LLVM/project 31704d8flang/test/Semantics/OpenMP map-modifiers.f90

Add a check for repeated ompx_hold modifier
DeltaFile
+8-0flang/test/Semantics/OpenMP/map-modifiers.f90
+8-01 files

FreeBSD/ports a6046e2security/vuxml/vuln 2026.xml

security/vuxml: Document www/angie vulnerabilities

PR:             297154
Approved by:    osa, vvd (Mentors, implicit)
DeltaFile
+32-0security/vuxml/vuln/2026.xml
+32-01 files

FreeBSD/src d2a5b5asys/netpfil/pf pf_if.c, tests/sys/netpfil/pf names.sh

pf: attempt to handle overlapping group and interface names

pf assumes that network groups and network interfaces share a namespace
(that is, a name is unused, a group or an interface, never both a the
same time). Unfortunately this assumption was broken when interface
renaming was introduced.
Attempt to cope with this rather than panicking. Note that this is a
band-aid, not a full solution. The correct fix is for the network stack
to go back to enforcing a single namespace for groups and interfaces.

PR:             297220
Reported by:    Robert Morris
MFC after:      1 week
Sponsored by:   Rubicon Communications, LLC ("Netgate")
DeltaFile
+23-0tests/sys/netpfil/pf/names.sh
+13-6sys/netpfil/pf/pf_if.c
+36-62 files

LLVM/project 50f1e37flang-rt/lib/runtime assign.cpp

Fix formatting issues
DeltaFile
+2-3flang-rt/lib/runtime/assign.cpp
+2-31 files

FreeBSD/src d13dffasys/netpfil/pf pf_nl.c

pf: fix securelevel off-by-one

cmd_securelevel is the securelevel at which the call should be denied.
pf (write) calls should be denied at level 3 or up (not at 2 or up as it
was), so increment these all by one.

PR:             296838
MFC after:      4 weeks
Sponsored by:   Rubicon Communications, LLC ("Netgate")
Differential Revision:  https://reviews.freebsd.org/D58377
DeltaFile
+47-47sys/netpfil/pf/pf_nl.c
+47-471 files

LLVM/project fe41b73llvm/lib/Target/AMDGPU SIISelLowering.cpp AMDGPUInstructionSelector.cpp, llvm/test/CodeGen/AMDGPU llvm.amdgcn.ballot.i32.wave64.err.ll

Reland "[AMDGPU] Fix llvm.amdgcn.ballot with return width != wavefront size" (#213635)

Reverts https://github.com/llvm/llvm-project/pull/212628

This relands #211493, which was reverted because
ockl_dm_alloc/ockl_dm_dealloc in device-libs emit an i32 ballot on
wave64, which GlobalISel cannot select (one bit per lane doesn't fit).
[#212813](https://github.com/llvm/llvm-project/pull/212813) widens the
clang ballot builtins to the wavefront size so a narrower-than-wave
ballot is no longer emitted, fixing the root cause.
DeltaFile
+15-0llvm/test/CodeGen/AMDGPU/llvm.amdgcn.ballot.i32.wave64.err.ll
+9-2llvm/lib/Target/AMDGPU/AMDGPUInstructionSelector.cpp
+9-0llvm/lib/Target/AMDGPU/SIISelLowering.cpp
+33-23 files

NetBSD/src gcss0TCsys/uvm/pmap pmap.c

   PR/60522: evbppc/RB800 hits MI pmap KASSERT failure

   Revert the pmap_protect part of

       Fix two EXECness issues
       - when creating a WX mapping via pmap_enter mark the page as EXEC
       - when pmap_protect adds X then ensure that pmap_page_syncicache is called
         for the page.

   It seems that pmap_pte_protect is designed to remove a protection and not
   add it.

   For the module loading the text is indeed mapped eXecute initially, and
   cache maintenance is currently handled by kobj_machdep and not the pmap.
VersionDeltaFile
1.108+3-3sys/uvm/pmap/pmap.c
+3-31 files

LLVM/project e701968llvm/lib/Analysis LoopAccessAnalysis.cpp, llvm/test/Analysis/LoopAccessAnalysis num-iters-for-store-load-conflict.ll

[LAA] Properly report strided access preventing store-to-load forwarding (#208791)

Original test by @fhahn in https://github.com/llvm/llvm-project/pull/191867, further reduced here.
Before this change LAA results in

> maximum safe store-load forward width of 32|0 bits

for `i32` accesses, effectively meaning that only `VF == 1` is safe, yet
not explicitly returning `false` from `couldPreventStoreLoadForward`.
This PR fixes that.
DeltaFile
+88-0llvm/test/Analysis/LoopAccessAnalysis/num-iters-for-store-load-conflict.ll
+7-0llvm/lib/Analysis/LoopAccessAnalysis.cpp
+95-02 files

FreeBSD/ports 4851f28www/angie distinfo, www/angie-module-vod Makefile

www/angie-module-vod: Update 1.9.0 => 1.9.1

This patch release fixes following bugs:
- Make thumbnail selection frame-accurate (#133)
- Honor sample aspect ratio (SAR) for thumb size calculations (#96)

Changelog:
https://github.com/dio-az/nginx-vod-module/blob/v1.9.1/CHANGELOG.md

Commit log:
https://github.com/dio-az/nginx-vod-module/compare/v1.9.0...v1.9.1

PR:             297200
Reported by:    Sebastian Oswald <sko at rostwald.de> (maintainer)
Approved by:    osa, vvd (Mentors, implicit)
MFH:            2026Q3

(cherry picked from commit 0a372f3a862c8c2969df8b01e5b2a812f1869b71)
DeltaFile
+2-2www/angie/distinfo
+2-2www/angie-module-vod/Makefile
+4-42 files

FreeBSD/ports f739dd9www/angie distinfo, www/angie-module-vod Makefile

www/angie-module-vod: Update 1.8.1 => 1.9.0

Changelog:
https://github.com/dio-az/nginx-vod-module/releases/tag/v1.9.0

PR:             296796
Sponsored by:   UNIS Labs

(cherry picked from commit 3c6813367fdd58ede4168c637cd135aa7f007d36)
DeltaFile
+2-2www/angie/distinfo
+1-1www/angie-module-vod/Makefile
+3-32 files

FreeBSD/ports fdabc3dwww/angie distinfo, www/angie-module-jwt Makefile

www/angie-module-jwt: update 3.4.4 => 3.4.5

Trigger CI on test files and workflow changes

Commit log:
https://github.com/max-lt/nginx-jwt-module/compare/v3.4.4...v3.4.5

PR:             297199
Reported by:    Sebastian Oswald <sko at rostwald.de> (maintainer)
Approved by:    osa, vvd (Mentors, implicit)
MFH:            2026Q3

(cherry picked from commit 04200cd0d6a3d2531f8d1215cf45df952f5693e0)
DeltaFile
+4-4www/angie/distinfo
+2-2www/angie-module-jwt/Makefile
+6-62 files

FreeBSD/src 459af94sys/netinet6 in6_mcast.c

netinet6: Fix some issues with passing v4-mapped groups to IPv6 sockets.

1. EFAULT was happening because sooptcopyin() from inp_join_group() was
seeing the user-space thread descriptor in the faked-up sockopt. So, do
not attempt a user copyin(); defer to C99 initialization nulling sopt_td
for us to force a KVA memcpy().

2. It seems necessary to byte-swap ipv6mr_multiaddr.s6_addr32[3] on amd64
for similar reasons as to how the user-space initialization needed for
passing an IPv4-mapped group address also requires byte-swapping of the
0x0000FFFF field for s6_addr32[2]; it is a direct assignment to a integer
member of a struct, NOT a memcpy().

3. The assignment to imr_interface within in6_v6_mreq_to_v4() was obfuscated
by a cast back to its own type due to use of the IA_SIN() macro. Elided.

With this change, the feature gap seems to be closed; tested with a simple
link-scope IPv4 group under 224.0.0.0/24 with an mlx5(4) SR-IOV VF in bhyve.


    [2 lines not shown]
DeltaFile
+5-7sys/netinet6/in6_mcast.c
+5-71 files

FreeBSD/src c8d4287usr.sbin/mtest mtest.c

mtest: Add support for exercising IPv4-mapped groups on IPv6 sockets.

This is in lieu of a full Kyua/ATF regression test, as this is an optional
feature that was beyond the scope of IETF's normative references for IPv6
multicast; support has been strictly on a best-effort basis.

Two new commands are added to mtest(8):
u mcast-addr ifname - join IPv4-mapped group on IPv6 socket
v mcast-addr ifname - leave IPv4-mapped group on IPv6 socket

Add an internal helper function __in6_v4_to_v4mapped() to perform the
converse of the IN6_IS_ADDR_V4MAPPED() check to support this use case.
Whilst __in6_v4_to_v4mapped() returns its first argument as a convenience,
avoid the temptation to dereference a pointer to that which we already hold.

Strictly the use of sockunion_t within mtest(8) more generally is a form
of controlled type punning (aliasing). Use a temporary as we overwrite
contents of su; the resultant write would overlap memory locations.


    [2 lines not shown]
DeltaFile
+72-0usr.sbin/mtest/mtest.c
+72-01 files

FreeBSD/src 4c4be9ausr.sbin/mtest mtest.c

mtest: Update my copyright on this file.
DeltaFile
+1-1usr.sbin/mtest/mtest.c
+1-11 files

LLVM/project 73a9a45libcxx/test/benchmarks/algorithms/modifying copy.bench.cpp copy_backward.bench.cpp, libcxx/test/benchmarks/containers deque_iterator.bench.cpp

[libc++] Fold deque iterator benchmarks into algorithm benchmarks (#212279)

The deque::iterator benchmarks were not truly about deque::iterator, but
about specialized algorithm implementations we have for segmented
iterators. This patch handles them as such, like we do for other
specialized algorithms like vector<bool>.
DeltaFile
+0-234libcxx/test/benchmarks/containers/deque_iterator.bench.cpp
+18-14libcxx/test/benchmarks/algorithms/modifying/move_backward.bench.cpp
+16-14libcxx/test/benchmarks/algorithms/modifying/move.bench.cpp
+13-9libcxx/test/benchmarks/algorithms/modifying/copy_backward.bench.cpp
+11-9libcxx/test/benchmarks/algorithms/modifying/copy.bench.cpp
+58-2805 files

FreeBSD/ports 2c95edewww/angie-module-lua Makefile, www/angie-module-lua/files patch-lua-config

www/angie-module-lua: Unbreak build after update

The module was updated but files/patch-lua-config still pointed
to the old working directory.

PR:             297198
Reported by:    Sebastian Oswald <sko at rostwald.de> (maintainer)
Approved by:    osa, vvd (Mentors, implicit)
MFH:            2026Q3

(cherry picked from commit 565dc2c4047d886d51024ec852352e26a7bb7c5a)
DeltaFile
+2-2www/angie-module-lua/files/patch-lua-config
+2-2www/angie-module-lua/Makefile
+4-42 files

FreeBSD/ports db905fawww/angie distinfo, www/angie-module-lua Makefile

www/angie-module-lua: Update 0.10.29R2 => 0.10.31

Changelog:
https://github.com/openresty/lua-nginx-module/releases/tag/v0.10.31

PR:             296796
Approved by:    Sebastian Oswald <sko at rostwald.de> (maintainer, implicit)
Sponsored by:   UNIS Labs

(cherry picked from commit 247f29084b10387077589822e6b9c42dd650acff)
DeltaFile
+2-2www/angie/distinfo
+1-1www/angie-module-lua/Makefile
+3-32 files

FreeBSD/ports b5b8914www/angie distinfo, www/angie-module-auth-jwt Makefile

www/angie: update 1.12.0 => 1.12.1

This patch release brings various security and bug fixes.

Changelog:
https://en.angie.software/angie/docs/oss_changes/#angie-1-12-1

PR:             297154
Reported by:    tjlegg at gmail.com
Approved by:    osa, vvd (Mentors, implicit)
Security:       CVE-2026-42533
Security:       CVE-2026-60005
Security:       CVE-2026-56434
MFH:            2026Q3

(cherry picked from commit ec945e58c5d3a62aeb623a6ccaf2d9c1921820c2)
DeltaFile
+3-3www/angie/distinfo
+3-3www/angie-module-lua/Makefile
+2-2www/angie-module-vod/Makefile
+2-2www/angie-module-headers-more/Makefile
+2-2www/angie-module-echo/Makefile
+2-2www/angie-module-auth-jwt/Makefile
+14-1418 files not shown
+32-3224 files

LLVM/project 4129e0cflang/include/flang/Optimizer/Builder/Runtime Assign.h, flang/lib/Optimizer/Builder/Runtime Assign.cpp

[flang] - Call _FortranAAssignSimple instead of _FortranAAssign for intrinsic-type array assignments.

This patch adds support for calling _FortranAAssignSimple, a faster-path for array assignments.
`_FortranAAssignSimple` is called when ALL the following conditions are true:
1. Intrinsic element type (not derived type)
2. Matching ranks (no scalar-to-array broadcasting)
3. Non-volatile
4. Not polymorphic
5. Not explicit-length character
6. Not temporary LHS

Otherwise, uses `_FortranAAssign` (or specialized variants like `_FortranAAssignPolymorphic`, `_FortranAAssignExplicitLengthCharacter`).

This is a (perhaps final) part of the fix for https://github.com/llvm/llvm-project/issues/203915
DeltaFile
+287-0flang/test/HLFIR/assign-simple-routing.fir
+46-4flang/lib/Optimizer/HLFIR/Transforms/ConvertToFIR.cpp
+19-13flang/lib/Optimizer/OpenMP/LowerWorkdistribute.cpp
+13-0flang/lib/Optimizer/Builder/Runtime/Assign.cpp
+12-0flang/include/flang/Optimizer/Builder/Runtime/Assign.h
+2-2flang/test/HLFIR/assign-codegen.fir
+379-192 files not shown
+381-218 files

LLVM/project 4a5e982llvm/lib/CodeGen/GlobalISel LegalizerHelper.cpp, llvm/test/CodeGen/AMDGPU/GlobalISel legalize-unmerge-values.mir legalize-extract-vector-elt.mir

GlobalISel: Fix floating point unmerge lowering

Bitcast to integer and use integer type for bit twiddling.
DeltaFile
+332-4llvm/test/CodeGen/AMDGPU/GlobalISel/extractelement.ll
+126-188llvm/test/CodeGen/AMDGPU/GlobalISel/legalize-extract-vector-elt.mir
+5-4llvm/test/CodeGen/AMDGPU/GlobalISel/legalize-unmerge-values.mir
+5-1llvm/lib/CodeGen/GlobalISel/LegalizerHelper.cpp
+468-1974 files

LLVM/project 22e413eflang-rt/lib/runtime tools.cpp assign.cpp, flang-rt/unittests/Runtime Assign.cpp

[flang-rt] - Lightweight runtime assignment function (AssignSimple) for intrinsic-type assignments.

This PR introduces a lightweight assignment runtime path (`_FortranAAssignSimple`) for intrinsic-type arrays
with the goal of reducing compile-time overhead seen primarily in the form of severly increased time taken by LTO.
This PR includes only the changes to the runtime (flang-rt) and as such just with this PR compile-time improvements
will not be visible.

**Problem**

When compiling Fortran code with OpenMP GPU offload and `firstprivate(allocatable_array)`, LLVM's Attributor creates excessive abstract attributes analyzing complex runtime assignment machinery:

**Symptom:**
- **Test case:** 8-element allocatable integer array with `firstprivate` clause
- **Compile time:** 24.97s (vs 0.78s for `private` - **32x slower**)
- **Root cause:** LLVM Attributor analyzing complex Fortran runtime functions

**Why this happens:**

1. `firstprivate` requires copying arrays from host to device

    [43 lines not shown]
DeltaFile
+214-0flang-rt/lib/runtime/assign.cpp
+151-0flang-rt/unittests/Runtime/Assign.cpp
+4-0flang/include/flang/Runtime/assign.h
+1-0flang-rt/lib/runtime/tools.cpp
+370-04 files

FreeBSD/ports 7a71e6fwww/angie Makefile distinfo

www/angie: Update 1.11.8 => 1.12.0

Changelog:
https://en.angie.software/angie/docs/oss_changes/#angie-1-12-0

PR:             296796
Sponsored by:   UNIS Labs

(cherry picked from commit 9e607a9c1ab3b68a79ec035f9c3e5ebde6e384cf)
DeltaFile
+3-3www/angie/distinfo
+1-1www/angie/Makefile
+4-42 files

FreeBSD/ports 0a372f3www/angie distinfo, www/angie-module-vod Makefile

www/angie-module-vod: Update 1.9.0 => 1.9.1

This patch release fixes following bugs:
- Make thumbnail selection frame-accurate (#133)
- Honor sample aspect ratio (SAR) for thumb size calculations (#96)

Changelog:
https://github.com/dio-az/nginx-vod-module/blob/v1.9.1/CHANGELOG.md

Commit log:
https://github.com/dio-az/nginx-vod-module/compare/v1.9.0...v1.9.1

PR:             297200
Reported by:    Sebastian Oswald <sko at rostwald.de> (maintainer)
Approved by:    osa, vvd (Mentors, implicit)
MFH:            2026Q3
DeltaFile
+3-3www/angie-module-vod/Makefile
+2-2www/angie/distinfo
+5-52 files

FreeBSD/ports 04200cdwww/angie distinfo, www/angie-module-jwt Makefile

www/angie-module-jwt: update 3.4.4 => 3.4.5

Trigger CI on test files and workflow changes

Commit log:
https://github.com/max-lt/nginx-jwt-module/compare/v3.4.4...v3.4.5

PR:             297199
Reported by:    Sebastian Oswald <sko at rostwald.de> (maintainer)
Approved by:    osa, vvd (Mentors, implicit)
MFH:            2026Q3
DeltaFile
+2-2www/angie/distinfo
+2-2www/angie-module-jwt/Makefile
+4-42 files