py-daphne: updated to 4.2.3
4.2.3 (2026-07-21)
* Added ``--websocket-max-message-size`` and ``--websocket-max-frame-size`` CLI
flags to the ``runserver`` management command for use in development.
net-mgmt/netbox: Update to 4.6.7
Changelog:
Performance Improvements:
* Skip cached scope rebuild for sites and locations when scope fields
are unchanged
* Avoid extraneous database queries when fetching custom field data via
the GraphQL API
* Avoid an extra database query when including rack reservation units
via the GraphQL API
* Avoid extraneous database queries when fetching the IP address or
prefix family via the GraphQL API
Bug Fixes:
* Correctly evaluate IP availability for users whose permissions are
constrained by a custom field on a related object
* Filter circuit group assignments by member type to avoid displaying
assignments belonging to a virtual circuit with the same ID
[5 lines not shown]
net-mgmt/py-netutils: Update to 1.18.0
* Add new JINJA2 option and make it default to have a good out-of-box
experience when Jinja2-aware configuration sanitization is needed.
Changelog:
https://github.com/networktocode/netutils/releases/tag/v1.18.0
net-mgmt/netbox: Update to 4.6.7
Changelog:
Performance Improvements:
* Skip cached scope rebuild for sites and locations when scope fields
are unchanged
* Avoid extraneous database queries when fetching custom field data via
the GraphQL API
* Avoid an extra database query when including rack reservation units
via the GraphQL API
* Avoid extraneous database queries when fetching the IP address or
prefix family via the GraphQL API
Bug Fixes:
* Correctly evaluate IP availability for users whose permissions are
constrained by a custom field on a related object
* Filter circuit group assignments by member type to avoid displaying
assignments belonging to a virtual circuit with the same ID
[4 lines not shown]
[SPARC] Add patterns for i64->i32 and i64->i16 BSWAP-STOREs (#210483)
The lack of those is causing instruction selection to fail.
Also, for completeness, add variants of extending/truncating ops for
LOAD-BSWAP pairs too.
(cherry picked from commit 7afc89970fc3675d77e92aa091b65c078cacdcff)
workflows/release-binaries: Move environment declaration to upload job (#212687)
This is the only job that actually needs to use the environment secrets,
so the environment must be declared. We were using secrets in the
prepare job to do a permissions check, but this is unnecessary, because
that job does not do anything that is security sensitive.
Only the upload job needs to have these permission checks and these are
already included in the upload-release-artifact composite action.
(cherry picked from commit 02bde0716776a742164941e05cb026e750763b04)
[clang][llvm][AArch64] Set hardening fn attrs on synthetic functions (#211013)
Compiler-synthesized functions such as `__llvm_gcov_writeout`,
`__llvm_gcov_reset` and `__llvm_gcov_init` were previously never
receiving the AArch64 hardening function attributes (ptrauth-returns,
ptrauth-auth-traps, ptrauth-indirect-gotos and
aarch64-jump-table-hardening) since the attributes were only emitted by
Clang and gated by `PointerAuthOptions` structure's corresponding
fields. See `setPointerAuthFnAttributes` and
`initPointerAuthFnAttributes` member functions of `TargetCodeGenInfo`.
This patch resolves this in the same manner as #83153 does for several
other attributes. Particularly, Clang now emits corresponding 4 module
flags (conditionally on whether the related feature is enabled) with Max
behavior, and LLVM's `Function::createWithDefaultAttr` derives the
matching function attributes from them. Max behavior with conditional
emission is safe because none of these features affect ABI, so promoting
an absent flag on module merge cannot break compatibility.
(cherry picked from commit 2f8eb5b4be3eba5c7f58470d6538d00df53a55fc)
[RISCV] Fix incorrect lowering of VECTOR_INTERLEAVE on fixed vectors (#212642)
This is the sibling patch of #207254, as it turns out VECTOR_INTERLEAVE
has the same problem on fixed vectors as well.
Instead of converting individual operands into scalable vectors, this
patch puts each of the operands directly onto stack using the fixed
vector version of segmented store intrinsics, before loading them back.
---------
Co-authored-by: Luke Lau <luke at igalia.com>
(cherry picked from commit ff9b99207b5d4ec73554defc1e3c1ac50f8ff1d8)
[DWARFLinker] Keep DW_TAG_enumerator children of a live enumeration_type (#212849)
Swift allows functions inside enums:
enum Foo: Int {
case bar = 0
func baz() { ... }
}
DW_TAG_enumeration_type "Foo"
DW_TAG_enumerator "bar"
DW_TAG_subprogram "baz" DW_AT_declaration
...
DW_TAG_subprogram DW_AT_low_pc(...) DW_AT_specification -> "baz"
dieNeedsChildrenToBeMeaningful() did not list DW_TAG_enumeration_type,
so the parent walk skipped the enum's children.
[4 lines not shown]
[LowerAtomic] Clear elementwise flag when lowering atomic load (#213401)
The lower atomic pass demotes atomic loads to non atomic by
calling setAtomic(NotAtomic), but left the elementwise flag untouched.
Since elementwise is only valid on atomic operations, this produced a
non-atomic elementwise load, which the verifier rejects with "non-atomic
load cannot be elementwise".
Reference: https://github.com/llvm/llvm-project/pull/204556
[InstCombine] Don't change the type of elementwise atomic loads (#213414)
Skip load type canonicalization for elementwise atomic loads, which
would
otherwise drop the vector type and produce an invalid scalar elementwise
load.
Reference: https://github.com/llvm/llvm-project/pull/204556
