py-genshi: updated to 0.7.12
0.7.12
* Add support for Python 3.15 and PyPy 3.12
* Fix reference leak in Markup.__mod__ for mapping arguments
* Drop processing instructions (PI) and CDATA sections in HTMLSanitizer
* Track nesting depth when removing unsafe elements in HTMLSanitizer
* Update CI test matrix to add Python 3.15 release and PyPy 3.12
* Several RTD build fixes
* Update versions of GitHub actions.
py-curl: updated to 7.49.0
PycURL 7.49.0 - 2026-10-26
This release adds SSH_HOSTKEYFUNCTION and several missing libcurl SSH
constants, and accepts CurlShare subclasses in setopt. It fixes a
use-after-free when a mime part's content is replaced and makes object
teardown exception-safe by moving cleanup into tp_finalize. The build
system has also been cleaned up: custom setup.py command line options have
been removed in favor of their environment variable equivalents, and wheels
no longer install documentation and examples.
[sanitizer_common][test] Require Android API 26 for variadic-open and allow_user_segv (#236010)
On Android API 24 emulators:
- `Posix/variadic-open.cpp` fails on `O_TMPFILE` because the older
kernel returns `EISDIR` when `O_TMPFILE` is not supported.
- `Linux/allow_user_segv.cpp` fails flakily across API 24 targets (not
just `i386`) due to the legacy `debuggerd` daemon racing on `waitpid`.
Require `android-26` when running on Android for both tests.
https://lab.llvm.org/buildbot/#/builders/sanitizer-x86_64-linux-android
Assisted-by: Gemini
www/npm*: Update to 12.2.0, use upstream distfile
Fetch the official tarball from the npm registry instead of a
re-rolled one on LOCAL/sunpoet, and create the installed layout
(bin/ and node_modules/.bin symlinks, compressed manual pages,
etc/man.d/npm.conf) in do-install. The package contents are
unchanged.
While here, sort variables as suggested by portclippy and drop a
REINPLACE_CMD that did not modify anything.
Changes: https://github.com/npm/cli/releases
PR: ports/299324
Approved by: maintainer timeout
[llvm] Remove incorrect IRMover assert (#221758)
The IRMover had an assertion that failed on modules with correct code.
The assert fired in an out-of-tree frontend.
Remove the assertion to fix that.
The assertion has been there for a long time (10 years if I read git
blame correctly) as the failing case cannot be hit when loading
completely separated modules (i.e. this is not reproducible with
`llvm-link`). It is however reproducible when generating modules from
code. One peculiarity is that a named struct type needs to be used in
both, the source and target module that are linked. As types are stored
in the LLVMContext, not in the Module, I believe this is still correct
IR and the IRLinker/Mover should be able to handle that correctly.
Concretely, the assert fired when filling `MappedTypes`. The dst Module
contains `%SharedTy`,
the src Module contains `%SharedTy` (exact same type) and `%Ty2`
(structurally equivalent to `%SharedTy`).
[9 lines not shown]
cargo-nextest: updated to 0.9.150
0.9.150
Security
Fixed GHSA-vc25-qg58-w57c: with the experimental run recording feature enabled, cargo nextest run --rerun with a malicious portable recording could run arbitrary code during the build.
Reruns inherit the original run's build scope (defined as the combination of package, target, and feature selection options). Nextest versions 0.9.125 through 0.9.149 recorded the build scope as raw Cargo arguments, and passed them to Cargo unchanged. A crafted recording could therefore add any Cargo option, such as a --config that sets build.rustc-wrapper. That code ran as the invoking user during the build, before any tests started, even with a warm build cache.
Nextest now records the build scope as structured data, and passes each value to Cargo joined to its flag (for example, --package=<value>), so a recording can no longer add other Cargo options.
To ensure that everyone working on your repository uses a fixed version, set the minimum required version in .config/nextest.toml:
nextest-version = "0.9.150"
Added
cargo nextest archive has a new --zstd-long option, which enables Zstandard long-distance matching with a 128 MiB window. For large archives, this can significantly improve the compression ratio at lower compression levels. Extracting these archives needs no extra options.
[15 lines not shown]
[clang][test] Add `--normalize=` parameter to ast_dump_json_test.py (#235789)
To replace the value of the matching json field with a regex.
Also update the output to list more passed command line parameters.
I've updated two test files as examples and to test the output doesn't
change otherwise.
Assisted by claude.
Show a clear message when a legacy license is uploaded
This commit fixes an issue where uploading a legacy license surfaced the license daemon's raw "Missing PEM BEGIN marker" parser error. We now detect a legacy license before it is handed to the daemon and tell the user it is unsupported and to contact TrueNAS Support, which also avoids writing it over the installed license only to roll it back.
NAS-144887 / 28.0.0-BETA.1 / Show a clear message when a legacy license is uploaded (#20066)
This commit fixes an issue where uploading a legacy license surfaced the
license daemon's raw "Missing PEM BEGIN marker" parser error. We now
detect a legacy license before it is handed to the daemon and tell the
user it is unsupported and to contact TrueNAS Support, which also avoids
writing it over the installed license only to roll it back.
[RISCV] Reassociate exts in ext/add reduction tree (#230928)
With an ext-add-ext-add pattern, the second ext can be pushed to after
the final add if the first ext adds enough bits to guarantee that the
second add won't overflow even without the second ext.
Further optimize ext-add reduction in x264 sad_NxN, building on #230657.
AI Usage: Assisted by Codex
[LV] Add epilogue test with FP IV with same start and step (NFC) (#235987)
Add a test with an fadd and an fsub induction that share start and step
values, to make sure each resumes from its own value in the epilogue
vector loop.
Revert "[KnownFPClass] Refactor NaN sign encoding for KnownFPClass" (#235992)
Reverts llvm/llvm-project#220606
Breaks the build with GCC, since
`KnownFPClass::toFPClassMask(FPClassTest, bool)` is not a constant
expression, because the compound assignment operators (`|=`, `&=`, `^=`)
in `llvm/ADT/BitmaskEnum.h` are not `constexpr`.
ZTS: allow ctypes library discovery
Include the loader discovery tools used by Python ctypes in the
constrained Linux test path.
Reviewed-by: Brian Behlendorf <behlendorf1 at llnl.gov>
Signed-off-by: ooonea <35407790+ooonea at users.noreply.github.com>
Assisted-by: OpenAI Codex
Closes #19576
Add tests for stale mmap pages after rollback and recv -F
A file that has been mapped with mmap() keeps its pages in the Linux
page cache. If the dataset is then rolled back, or receives an
incremental stream with "zfs receive -F", and the file keeps its
object number, generation and size but has different data, reads
and new mappings kept returning the pre-rollback data until the
cache was dropped or the dataset remounted (#10931). The on-disk
data was always correct.
Add mmap_cached_rollback and mmap_cached_receive to the mmap group.
Both fault the file in through a read-only mapping, change the
dataset underneath it, and check that read() and a fresh mapping
see the new contents. The mmap_stale_check helper does the mapping
and checksumming.
Both tests fail on Linux without the zfs_rezget() page cache fix
and pass with it. They also pass on FreeBSD.
[3 lines not shown]
drm/amdgpu: free the userptr ranges when a CS fails after parser_bos
From Jesse Zhang
6ac46ae5ac561d4fc7d4246ad83d71bed0d9af9a in linux-6.18.y/6.18.59
1b4da805a0ba354a549ce07459c871c17dd94fe0 in mainline linux
