py-test-lazy-fixtures: updated to 1.4.1
1.4.1
Bump astral-sh/setup-uv from 6 to 7 in the github-actions group
Fix NameError on Python 3.14 for TYPE_CHECKING-only annotations (use FORWARDREF)
Bump the github-actions group across 1 directory with 4 updates
py-pdf: updated to 6.16.2
6.16.2
Bug Fixes (BUG)
- Make remove_from_tree() work on outline items
- Be more lenient about space width in layout mode text extraction
- Do not scale the text leading by the font size
- Update annotation appearance stream matrix on page transform
- Allow repeated page references
Robustness (ROB)
- Improve RC4 fallback when cryptography can't provide it
py-time-machine: updated to 3.5.0
3.5.0 (2026-08-25)
Support None as a destination for travel() and Traveller.move_to(), meaning the current time. Use this with tick=False to freeze time at the present moment, matching freezegun’s behaviour when freeze_time() is called with no arguments.
Extend the Migration CLI to migrate aliased imports: import freezegun as fg and from freezegun import freeze_time as ft, plus calls using such aliases.
Extend the Migration CLI to migrate the pytest.mark.freeze_time marker in module-level and class-level pytestmark assignments.
Extend the Migration CLI to migrate freeze_time() calls and markers that pass tz_offset with a literal zero value. The argument is dropped, since a zero offset has no effect.
Extend the Migration CLI to migrate freeze_time() calls and markers that pass real_asyncio. The argument is dropped, whatever its value, since time-machine does not mock time.monotonic(), so asyncio event loops always see real time.
Extend the Migration CLI to migrate freeze_time() calls and markers with no destination argument, which freeze at the current time. None is added as the destination, using the new support for None destinations (above).
Extend the Migration CLI to migrate freeze_time() calls and markers that pass ignore. The argument is dropped, since it works around problems with freezegun’s module patching, which time-machine’s C-level mocking doesn’t have.
Make the Migration CLI report freezegun-related usages that it recognizes but cannot migrate, with their positions, like:
example/tests.py:9:2: freeze_time usage not migrated
[8 lines not shown]
[WebAssembly][GlobalISel] Implement pointer and memory ops (v2) (#219072)
Implements a variety of pointer and memory related ops
(`G_GLOBAL_VALUE`, `G_PTR_ADD`, `G_LOAD`, `G_STORE`, etc.).
Split from #157161
-----
TODO (in future PR)
- Move `G_PTRTOINT`, `G_INTTOPTR`, `G_PTRMASK` selection to tablegen
(for all targets)
- MAYBE try to shuffle `G_GLOBAL_VALUE` selection elsewhere (e.g.
legalizer). Doesn't seem worth it?
-----
Reapplication of #206885 with some fixes and extensions.
libgcrypt: updated to 1.12.3
Noteworthy changes in version 1.12.3 (2026-08-26)
* Bug fixes:
- Avoid theoretical drive-by loading of netapi32.dll and
shell32.dll.
- Validate hash algorithm for use with RSA modulus.
- Validate parameters of Balloon KDF.
- Validate parallelism of Argon2 KDF.
- Fix parsing quoted parts and CRLF/LFCR in s-expression.
- Support BUFLEN check for GCRYMPI_FMT_SSH.
- Fix RSA PSS verify message length checking.
- Avoid a NULL ptr deref due to a unsupported genkey flag for
ECC.
- Assert 32 KiB input cap in gcm_ctr_encrypt.
- Fix assertion failure in OCB when a buffered block becomes block
65536.
[40 lines not shown]
bnxt: Add led(4) identification support
Query the firmware for the LEDs on each physical port and expose
/dev/led/bnxt* only when alternate blinking is supported. Configure
every LED in the advertised group for identification and restore its
default firmware state before a function reset.
This follows the DPDK and Linux bnxt HWRM identification paths.
Reviewed against: DPDK, Linux
Reviewed by: Sumit Saxena <sumit.saxena at broadcom.com>
Sponsored by: BBOX.io
(cherry picked from commit 98b5640786f874949e441bee7c4ad5740cd6a649)
bnxt: Add led(4) identification support
Query the firmware for the LEDs on each physical port and expose
/dev/led/bnxt* only when alternate blinking is supported. Configure
every LED in the advertised group for identification and restore its
default firmware state before a function reset.
This follows the DPDK and Linux bnxt HWRM identification paths.
Reviewed against: DPDK, Linux
Reviewed by: Sumit Saxena <sumit.saxena at broadcom.com>
Sponsored by: BBOX.io
(cherry picked from commit 98b5640786f874949e441bee7c4ad5740cd6a649)
bnxt: Add led(4) identification support
Query the firmware for the LEDs on each physical port and expose
/dev/led/bnxt* only when alternate blinking is supported. Configure
every LED in the advertised group for identification and restore its
default firmware state before a function reset.
This follows the DPDK and Linux bnxt HWRM identification paths.
Reviewed against: DPDK, Linux
Reviewed by: Sumit Saxena <sumit.saxena at broadcom.com>
Sponsored by: BBOX.io
(cherry picked from commit 98b5640786f874949e441bee7c4ad5740cd6a649)
[mlir][LLVM] Verify that constant attribute and result types match
`llvm.mlir.constant` only checked that the kind of the value attribute suits
the kind of the result type, never that the types themselves agree. All of the
following verified:
%0 = llvm.mlir.constant(1 : index) : i64
%1 = llvm.mlir.constant(1 : i8) : i16
%2 = llvm.mlir.constant(dense<1> : vector<4xi32>) : vector<4xi64>
Translation ignores the attribute type and uses the result type, so the
attribute type was effectively decorative for integers, and passes that read it
back could observe a type that has nothing to do with the value.
Require exact type equality for integer attributes and exact element type
equality for integer elements attributes, mirroring the `AllTypesMatch`
constraint `arith.constant` gets from ODS. The op cannot use that trait itself
because `value` is an `AnyAttr` that also holds `StringAttr` and `ArrayAttr`.
The element type check is also run on the scalable vector path, which
[11 lines not shown]
[mlir] Build llvm.mlir.constant attributes from the result type (#218607)
Many conversion patterns created `llvm.mlir.constant` with a value
attribute whose type does not match the result type. The most common
case was pairing an `index`-typed attribute with the converted index
type:
```
llvm.mlir.constant(1 : index) : i64
```
but there were also plain width and signedness mismatches, e.g. NVGPU's
`makeI64Const` built `i64` constants from `i32` attributes, and the NVVM
`fdiv` expansion used `ui32` attributes on `i32` values.
Translation to LLVM IR ignores the attribute type and uses the result
type, so the emitted IR was correct, but the attribute type is
meaningless in this state and anything that reads it back sees the wrong
type. Derive the attribute from the result type in every case; where the
[21 lines not shown]
ufshci: handle a recovery reset before the SIM attach
When the first start attempt fails early, the recovery reset
runs the start sequence again without a SIM. That pass still
looked up the WLUN, so it dereferenced a NULL SIM and panicked.
Attach the SIM whenever it does not exist yet. Also make the
WLUN lookup return NULL when there is no SIM.
Reviewed by: imp (mentor)
Sponsored by: Samsung Electronics
Differential Revision: https://reviews.freebsd.org/D58947
ufshci: build valid fake responses for manual completion
The manual completion wrote the fake response to the wrong
descriptor for task management slots. It also left the task tag
at zero, which tripped the task tag check under INVARIANTS.
Write the fake response where the completion path reads it.
Copy the task tag from the request.
Reviewed by: imp (mentor)
Sponsored by: Samsung Electronics
Differential Revision: https://reviews.freebsd.org/D58946
ufshci: build valid fake responses for manual completion
The manual completion wrote the fake response to the wrong
descriptor for task management slots. It also left the task tag
at zero, which tripped the task tag check under INVARIANTS.
Write the fake response where the completion path reads it.
Copy the task tag from the request.
Reviewed by: imp (mentor)
Sponsored by: Samsung Electronics
Differential Revision: https://reviews.freebsd.org/D58946
ufshci: reject new requests on a failed controller
A failed controller accepted new requests, but nothing ever
completed them, so the caller waited forever. The admin retry
path could also resubmit a request to a dead queue.
Reject new submits and admin retries on a failed controller.
The submit check runs under the queue lock, so it cannot race
with the queue walk in the fail path.
Reviewed by: imp (mentor)
Sponsored by: Samsung Electronics
Differential Revision: https://reviews.freebsd.org/D58948
ufshci: handle a recovery reset before the SIM attach
When the first start attempt fails early, the recovery reset
runs the start sequence again without a SIM. That pass still
looked up the WLUN, so it dereferenced a NULL SIM and panicked.
Attach the SIM whenever it does not exist yet. Also make the
WLUN lookup return NULL when there is no SIM.
Reviewed by: imp (mentor)
Sponsored by: Samsung Electronics
Differential Revision: https://reviews.freebsd.org/D58947
ufshci: reject new requests on a failed controller
A failed controller accepted new requests, but nothing ever
completed them, so the caller waited forever. The admin retry
path could also resubmit a request to a dead queue.
Reject new submits and admin retries on a failed controller.
The submit check runs under the queue lock, so it cannot race
with the queue walk in the fail path.
Reviewed by: imp (mentor)
Sponsored by: Samsung Electronics
Differential Revision: https://reviews.freebsd.org/D58948
