mvc: guard BaseField::setNodes() against a list given for a scalar leaf (#10434)
setNodes() rejects a non-array given for a container node, but the leaf branch passed any value straight to setValue(). Posting a JSON array for a scalar/AsList field therefore reached field setters that assume a string, e.g. NetworkField::setValue() does strtolower() on it. producing a fatal "TypeError: strtolower(): array given" and an uncontrolled 500.
Mirror the container guard: throw an Exception so a mis-typed request yields a controlled error with a message for the log instead of a crash.
[libc++][test] Migrate _BitInt probe to __BITINT_MAXWIDTH__ and fix latent test bugs (#203876)
`libcxx` tests gate `_BitInt` blocks on `TEST_HAS_EXTENSION(bit_int)`,
which is not a recognized Clang extension and returns 0 in every
language mode. The blocks have been compiling as dead code, hiding
latent bugs across 23 files.
Migrate to a `TEST_HAS_BITINT` helper backed by the standard
`__BITINT_MAXWIDTH__`. The latent bugs the activation surfaces are fixed
in the same commit:
- overflow-safe `min`;
- post-P4052R0 saturating-arithmetic renames plus a
`clang-21`/`apple-clang-21` skip for `saturating.bitint.pass.cpp` (Clang
21 asserts in constexpr eval on non-byte-aligned `_BitInt`);
- an `intcmp` syntax fix;
- `byteswap.verify` directive tightening;
- a missing `<climits>` include in `byteswap.pass` (only visible under
`-fmodules`);
- C++03-compatible `static_assert` form in `digits10`; gating
[13 lines not shown]
[clang][bytecode] Check const writes more thorougly (#204529)
We used to only have a list of blocks under construction, but now we
have a list of pointers, which gives us more information.
Use this new list to diagnose a case we couldn't previously diagnose.
The test case is from `constant-expression-cxx14.cpp` and shows that a
write to a const member is invalid, even if the parent object is being
constructed right now.
[AMDGPU][doc] Refactor Barrier Execution Model
Remove everything that has to do with named barriers and put it in a series of model extensions specific to /sbarrier/named-barriers.
I had to change a few things to make it fit, in summary:
Base Model:
* Stylistic changes that make it easier to refer to specific rules. Each rule is in a rubric instead of a bullet point.
* (-) No longer defines `barrier-mutually-exclusive`
* (-) No longer defines barrier `join` and any associated rule.
New named barrier extensions
* Define "named barrier" as a sub-type of barrier objects. This makes barrier-mutually-exclusive redundant.
* Define barrier join as an op that can exclusively be done on `named barrier objects`.
* Define rules relating to join and its ordering with other barrier operations
Following these changes, the target tables changed a bit as well.
[2 lines not shown]
bsnmpd/snmp_hostres: fix hrFSTable remoteMountPoint leak
Free the previous value before re-strdup'ing, and initialise
remoteMountPoint to NULL in fs_entry_create() so the free() is safe on
the newly-created path
Observed via a dtrace leak snapshot on 15.0-RELEASE-p4:
data leaked = 1983, count = 1683
libc.so.7`malloc+0xa8
snmp_hostres.so.6`fs_tbl_process_statfs_entry+0x276
snmp_hostres.so.6`refresh_storage_tbl+0x502
snmp_hostres.so.6`op_hrStorageTable+0x1a
libbsnmp.so.7`0x2a2b1892ba3d
libbsnmp.so.7`snmp_getbulk+0x37f
Reviewed by: sjg, ngie
Differential Revision: https://reviews.freebsd.org/D57604
multimedia/vapoursynth: Update to R73 and adopt port
* Set multimedia at FreeBSD.org as maintainer
* This is the latest version that supports our aging default
Python version in tree
Changelog: https://github.com/vapoursynth/vapoursynth/releases/tag/R73
Convert truecommand plugin to typesafe pattern
This commit adds changes to convert the truecommand plugin to the typesafe pattern, splitting the old compound ConfigService into a lean GenericConfigService that delegates to a ConfigServicePart with Pydantic models, while the portal/wireguard/state logic moves into plain context-first functions and same-process calls use call2. In-process consumers of truecommand.config (truenas and security) switch from dict access to typed attribute access.
x11/mate-screensaver: remove unneeded USE_GITHUB and GH_ACCOUNT
Remove USE_GITHUB=nodefault and GH_ACCOUNT as they are not needed
with an explicit MASTER_SITES. Add back DIST_SUBDIR=mate.
x11/mate-panel: remove unneeded USE_GITHUB and GH_ACCOUNT
Remove USE_GITHUB=nodefault and GH_ACCOUNT as they are not needed
with an explicit MASTER_SITES. Add back DIST_SUBDIR=mate.
x11/mate-desktop: remove unneeded USE_GITHUB and GH_ACCOUNT
Remove USE_GITHUB=nodefault and GH_ACCOUNT as they are not needed
with an explicit MASTER_SITES. Add back DIST_SUBDIR=mate.
x11/mate-menus: remove unneeded USE_GITHUB and GH_ACCOUNT
Remove USE_GITHUB=nodefault and GH_ACCOUNT as they are not needed
with an explicit MASTER_SITES. Add back DIST_SUBDIR=mate.
x11/libmatekbd: remove unneeded USE_GITHUB and GH_ACCOUNT
Remove USE_GITHUB=nodefault and GH_ACCOUNT as they are not needed
with an explicit MASTER_SITES. Add back DIST_SUBDIR=mate.
x11/mate-applets: remove unneeded USE_GITHUB and GH_ACCOUNT
Remove USE_GITHUB=nodefault and GH_ACCOUNT as they are not needed
with an explicit MASTER_SITES. Add back DIST_SUBDIR=mate.
x11-wm/marco: remove unneeded USE_GITHUB and GH_ACCOUNT
Remove USE_GITHUB=nodefault and GH_ACCOUNT as they are not needed
with an explicit MASTER_SITES. Add back DIST_SUBDIR=mate.
x11-themes/mate-themes: remove unneeded USE_GITHUB and GH_ACCOUNT
Remove USE_GITHUB=nodefault and GH_ACCOUNT as they are not needed
with an explicit MASTER_SITES. Add back DIST_SUBDIR=mate.
x11-themes/mate-icon-theme: remove unneeded USE_GITHUB and GH_ACCOUNT
Remove USE_GITHUB=nodefault and GH_ACCOUNT as they are not needed
with an explicit MASTER_SITES. Add back DIST_SUBDIR=mate.
x11-themes/mate-backgrounds: remove unneeded USE_GITHUB and GH_ACCOUNT
Remove USE_GITHUB=nodefault and GH_ACCOUNT as they are not needed
with an explicit MASTER_SITES. Add back DIST_SUBDIR=mate.
