NAS-141166 / 26.0.0-RC.1 / Remove stale ARC graph names from reporting API (by Qubad786) (#19107)
## Problem
`reporting.get_data` accepted three graph names — `arcrate`,
`arcactualrate`, `arcresult` — whose backing plugin classes were deleted
during the ZFS netdata plugin rewrite. The Pydantic `Literal` and the
in-memory `__graphs` dict drifted out of sync, so passing any of them
crashed `netdata_get_data` with an uncaught `KeyError`.
## Solution
Removed the dead names from `GraphIdentifier.name`'s `Literal` and
docstring in both `v26_0_0/reporting.py` and `v27_0_0/reporting.py`.
Added a `ReportingNetdataGetDataArgs.from_previous` on each so legacy WS
clients walking the adapter chain get the dead entries silently filtered
instead of a hard rejection at the final v27 boundary. Hardened the
dispatch site in `plugins/reporting/graphs.py` to raise
`CallError(ENOENT)` for any unknown name — mirroring what
[5 lines not shown]
[mlir][spirv] Account for undefined behaviour in GLSL ops (#203086)
Add only `NoMemoryEffect` to operations with an undefined behavior and
adjust the description to match the revision 17 of the spec w.r.t. undefined
behavior.
Assisted-by: Claude Code
[SLP] Do not vectorize copyable operands of expanded binops
An operand modeled as a copyable element on one operand edge of an
expanded binop (shl X, 1 represented as add X, X) leaves the duplicated
operand edge as a plain gathered operand with no copyable. The scheduler
then decrements that operand's ScheduleData for a use calculateDependencies
never counted for it, so its unscheduled-deps counter goes negative and
trips the assertion. Reject such bundles instead.
Fixes #203193
Reviewers:
Pull Request: https://github.com/llvm/llvm-project/pull/203285
NAS-141166 / 27.0.0-BETA.1 / Remove stale ARC graph names from reporting API (#19072)
## Problem
`reporting.get_data` accepted three graph names — `arcrate`,
`arcactualrate`, `arcresult` — whose backing plugin classes were deleted
during the ZFS netdata plugin rewrite. The Pydantic `Literal` and the
in-memory `__graphs` dict drifted out of sync, so passing any of them
crashed `netdata_get_data` with an uncaught `KeyError`.
## Solution
Removed the dead names from `GraphIdentifier.name`'s `Literal` and
docstring in both `v26_0_0/reporting.py` and `v27_0_0/reporting.py`.
Added a `ReportingNetdataGetDataArgs.from_previous` on each so legacy WS
clients walking the adapter chain get the dead entries silently filtered
instead of a hard rejection at the final v27 boundary. Hardened the
dispatch site in `plugins/reporting/graphs.py` to raise
`CallError(ENOENT)` for any unknown name — mirroring what
`netdata_graph` already does — so future schema/implementation drift
surfaces as a clean RPC error rather than an unhandled exception.
net/ipv6calc: Update to version 4.4.0
General:
internal databases: update
IP2Location 8.7.0 related (relates to https://github.com/chrislim2888/IP2Location-C-Library/releases/tag/8.7.0
which has unfortunatly incompatible API changes)
ipv6calcweb/ipv6calcweb.cgi.in: add support for new fields in DB26 with 8.7.0
add support for additional data in DB26 usable with IP2Location >= 8.7.0
check IP2Location > 8.6.1 related compatibility/fallback
Extensions:
add option --has-feature <NAME>
[llvm] Fix most LLVM_ABI annotations in TableGen (#203246)
This updates most LLVM_ABI annotations in the TableGen headers to match
expected usage:
* All public APIs should be properly annotated.
* Inlined functions should not be annotated.
These changes were done by a script fixing annotations on LLVM public
headers and manually checked.
This effort is tracked in #109483.
[llvm] Fix most LLVM_ABI annotations in Frontend (#203245)
This updates most LLVM_ABI annotations in the Frontend headers to match
expected usage:
* All public APIs should be properly annotated.
* Inlined functions should not be annotated.
These changes were done by a script fixing annotations on LLVM public
headers and manually checked.
This effort is tracked in #109483.
[llvm] Fix most LLVM_ABI annotations in IR (#203244)
This updates most LLVM_ABI annotations in the IR headers to match
expected usage:
* All public APIs should be properly annotated.
* Inlined functions should not be annotated.
These changes were done by a script fixing annotations on LLVM public
headers and manually checked.
This effort is tracked in #109483.
[llvm] Fix most LLVM_ABI annotations in CAS (#203243)
This updates most LLVM_ABI annotations in the CAS headers to match
expected usage:
* All public APIs should be properly annotated.
* Inlined functions should not be annotated.
These changes were done by a script fixing annotations on LLVM public
headers and manually checked.
This effort is tracked in #109483.
Convert hardware plugin to the typesafe pattern
## Context
The hardware plugin is a directory of four mostly-private legacy services (mseries.bios, mseries.nvdimm, hardware.memory, plus hardware.virtualization). Only hardware.virtualization.variant is public over the wire; the rest return plain dicts/bools consumed internally by alert sources and usage reporting, so Pydantic models would be pure overhead.
## Solution
Applied the port-plugin pattern: lean Service shims in __init__.py that delegate to plain, fully type-annotated module functions, keeping the existing dict/primitive return shapes so no consumer changes are needed. The one public method gets check_annotations=True against the existing HardwareVirtualizationVariant models. Registered the services in main.py's ServiceContainer via nested hardware/mseries containers and added the plugin to mypy.yml.
