security/py-social-auth-core5: New port
This is the core component of the python-social-auth ecosystem, it
implements the common interface to define new authentication backends
to third parties services, implement integrations with web frameworks
and storage solutions.
Note: This port is primarily intended for use with net-mgmt/netbox,
which currently does not support newer versions of py-social-auth-core.
net-mgmt/netbox: Add Django 6.1 consumers
* Django 5.2 is currently the "default" version in the ports tree due
its long term support until April 2028. Thus ports that are assigned
to that version will exist until then.
The following ports are required to make the upgrade of
net-mgmt/netbox to the 4.7 release possible because it requires
Django 6.1.
All of the ports listed below were created on the basis of their
respective original ports:
- devel/py-dj61-django-rq
- devel/py-dj61-strawberry-graphql
- graphics/py-dj61-sorl-thumbnail
- www/py-dj61-channels
- www/py-dj61-django-auth-ldap
- www/py-dj61-django-choices-field
[16 lines not shown]
net-mgmt/netbox: Update to 4.7.5
* Remove no longer required workaround for DRF 3.18.3.
* Sort some dependencies and prune update instructions for NetBox
releases older than 3.7 while I'm here.
Netbox 4.7 contains many bugfixes/enhancements and the following new
features:
* Cooling Infrastructure Modeling
* Channelized Subinterfaces
* Multi-Protocol Application Services
* Module Bay Types
* Relocating Installed Modules
* Background Processing for REST API Requests
* Per-Object Errors for Bulk Operations
* Pre-Rendered Config Context Data
* Snapshot-Aware Event Rule Conditions
[4 lines not shown]
security/py-social-auth-core: Update to 5.2.0
* Adjust testsuite accordingly so that the results are successful
depending on the configuration.
* Note: This is an interim update to create a py-social-auth-core5 port
based on this, which is limited to the 5.x release series and adjust
CONFLICTS_INSTALL for future variants of py-social-auth-core.
Changelog since 5.0.1:
https://github.com/python-social-auth/social-core/blob/5.2.0/CHANGELOG.md
Approved by: ultima (maintainer, implicit)
MFH: 2026Q4
lang/go127: Update to 1.27.4
Changes:
go1.27.4 (released 2026-11-10) includes security fixes to cgo, the go
command, the compiler, the linker, and the net/http package, as well
as bug fixes to the assembler, the compiler, the runtime, toolchain
bootstrapping, and the crypto/fips140, crypto/hkdf, crypto/rsa,
crypto/tls, and net packages.
MFH: 2026Q4
lang/go126: Update to 1.26.11
Changes:
go1.26.11 (released 2026-11-10) includes security fixes to cgo, the go
command, the compiler, the linker, and the net/http package, as well
as bug fixes to the assembler, the compiler, the runtime, toolchain
bootstrapping, and the crypto/fips140, crypto/hkdf, crypto/rsa,
crypto/tls, net, and net/http packages.
MFH: 2026Q4
modstat: avoid copying from freed memory
If a module is unloaded after the module is looked up in kern_modstat,
but before one of the copyout's occurs, then the memory being copied
might be freed and reused leading to an information disclosure.
The LLM was particularly concerned about a TOCTOU issue in the length
of the name, but it seems likely that there are issues with all the
copyout's. As such, hold the shared lock throughout.
Reviewed by: markj
Reported by: llm-postcr
MFC after: 3 days
Sponsored by: Innovate UK
Fixes: 9b3851e9e3b1 ("- Lock down the ``module'' structure...")
Differential Revision: https://reviews.freebsd.org/D61398
[RISCV] Avoid temporary extension keys
Make ExtensionComparator transparent and compare StringRef keys
directly.
Use heterogeneous lookup for OrderedExtensionMap queries.
Avoid temporary std::string allocations in common ISA checks.
Three interleaved CTMark pairs reduce median compile time by 0.163%
and geomean by 0.293%.
Assisted-by: TRAE CLI (GPT-6)
Reviewers: lenary, arichardson, topperc, mshockwave, lukel97
Pull Request: https://github.com/llvm/llvm-project/pull/241175
[mlir][bufferization] Let a type be tensor-like for some of its instances (#240522)
Today `isa<TensorLikeType>(ty)` depends only on which type `ty` is: a
type that implements the interface is tensor-like for every instance.
This change lets the answer depend on `ty`'s parameters as well.
It adds `TensorLikeType::isTensorLike`, defaulting to true, and makes
the interface's `classof` require it through `extraClassOf`. This is the
"optional interface" pattern `extraClassOf` exists for, and which
`SymbolOpInterface` uses for optional symbols. Types which do not
override the method are unaffected.
This enables a wrapper type to be tensor-like only when the type it
wraps is. Otherwise, either all instances of the wrapper are treated as
tensor-like or none are.
Adds a test tensor-like wrapper type that is tensor-like when its
wrapped type is. Tests bufferization against wrapped tensor-like and
non-tensor-like types.
[3 lines not shown]
[AArch64] Support direct RCPC3 FP atomic loads and stores
Preserve half, bfloat, float, and double atomic loads and stores
through AtomicExpand for acquire and release orderings, and preserve
sequentially consistent stores, when RCPC3 and NEON are available.
Add SelectionDAG patterns for the RCPC3 LDAPUR and STLUR operations,
including unscaled offsets, and update the existing FP lane patterns to
match the preserved floating-point atomic nodes. Targets without the
required features continue to use integer lowering.
[Offload] Fix possible out-of-scope access in kernel launch (#240597)
Fix issue reported by @jayfoad.
In the case of synchronous kernel launch, the Asyncinfo is allocated on
the stack. When the pointer is stored in the `KernelTraceInfoRecord` it
might be eventually be accessed after being deallocated when a kernel
trap happens.
Fix it by not adding it to the KTI when is a synchronous operation (this
was the previous behavior).
Assisted by Claude.
