py-tortoise-orm: updated to 1.1.7
1.1.7
Added
Tests for model validators.
Fixed
Reorder delete model operations in migrations to avoid foreign key constraint errors.
Return value generated by db_default on create instead of None.
Column comment alteration now works correctly for MySQL and PostgreSQL; fixed db_default handling for MySQL.
Fix docstrings for a few classes.
Changed
Improved Pydantic JSON dump performance.
graphics/mmdr: Add new port
Mmdr is a fast native Rust Mermaid diagram renderer. No browser required. Mmdr
renders diagrams 100–1400x faster than mermaid-cli by eliminating browser
overhead. With the built-in font cache (warm after first run), tiny diagrams
reach 500–900x (and --fastText exceeds 1600x).
https://github.com/1jehuang/mermaid-rs-renderer
[NFCI][sanitizer_common] Realign #ifdefs in sanitizer_internal_defs.h (#186861)
Currently it is very hard to tell these nested ifdefs apart. This patch
fixes that, while trying to be as light-touch as possible.
[ASan][test-only] Remove superfluous guards in stack_container_dynamic_lib.c (#188469)
As noted in https://github.com/llvm/llvm-project/pull/188406 comments,
the documentation recommends guarding only with
__has_feature(address_sanitizer). This patch updates the test to follow
the same pattern by removing the
__SANITIZER_DISABLE_CONTAINER_OVERFLOW__ checks. Having this macro
defined results in the common_interface_defs.h header defining the
contiguous container functions as no-ops anyway.
This is a followup to https://github.com/llvm/llvm-project/pull/188406.
py-cryptography py-cryptography_vectors: updated to 46.0.6
46.0.6 - 2026-03-25
* **SECURITY ISSUE**: Fixed a bug where name constraints were not applied
to peer names during verification when the leaf certificate contains a
wildcard DNS SAN. Ordinary X.509 topologies are not affected by this bug,
including those used by the Web PKI. Credit to **Oleh Konko (1seal)** for
reporting the issue. **CVE-2026-34073**
kea: move pool-in-subnet validation logic mostly to KeaPoolsField; closes #10040
While here use getValues() consistently and move the trim() calls to the
latest point in time to avoid generalized trimming of input (the subnet
notation isn't allowed to be trimmed).
An alternative would have been to allow " ?- ?" as a split-regex since the
trim() itself will allow the leading an trailing whitespaces of the pool line,
too.
Suggested by: @Astranox
[SPIR-V] Emit OpSpecConstantComposite for composites with spec constant operands (#188557)
- The SPIR-V spec requires that OpConstantComposite must not reference
spec constant operands. When a composite contains non-constant
constitued, OpSpecConstantComposite should be emitted instead of
OpConstantComposite
- Avoid creating function pointer types when the
SPV_INTEL_function_pointers extension is unavailable, falling back to i8
as the pointee type
- Re-enable spirv-val validation in tests that previously failed due to
this issue, and un-XFAIL the block_w_struct_return and global_block
transcoding tests
related to #60133
fixes #186756
[OpenMP][test] Remove %flags-use-compiler-omp-h (#188789)
With the standalone and project builds removed,
`OPENMP_TEST_COMPILER_HAS_OMP_H`/`config.test_compiler_has_omp_h` is set
to constant 1, which causes the `config.omp_header_directory` search
path NOT to be added to `%flags-use-compiler-omp-h`, causing the system
`omp.h` used, or the only test actually using it
(`omp50_taskdep_depobj.c`) failing if that one is not available.
The intention of `OPENMP_TEST_COMPILER_HAS_OMP_H` was to use gcc's
`omp.h` which declares `omp_depend_t` differently than our `omp.h`
(https://reviews.llvm.org/D108790). Using `OPENMP_TEST_C_COMPILER=gcc`
was used to test libomp's GOMP compatibility layer, but testing it is
currently unmaintained and has no buildbot (60 failing tests out of 389
with gcc-13, not including OMPD and OMPT). If updating testing for GOMP,
then gcc's own `omp.h` must be used for all tests: using the GOMP ABI
requires using GOMP's `omp.h`.
Closes: #187879
[SPIRV] Add bitreverse expansion for kernel (#186412)
The OpBitReverse is available when Shader or SPV_KHR_bit_instructions
extension is enabled. For targets without these capabilities, introduce
software emulation of G_BITREVERSE based on the parallel bit reversal
algorithm:
https://graphics.stanford.edu/~seander/bithacks.html#ReverseParallel
The emulation supports 8/16/32/64-bit scalars and vectors using bitwise
operations (shifts, AND, OR). A helper lambda avoids undefined behavior
when computing masks for 64-bit types.
Tests added for both emulation and native paths across all supported
types.
Assisted-by: Claude Code
libclc: Partially implement nonuniform subgroup reduce functions (#188929)
For AMDGPU these are identical to the uniform case. Stub out the missing
cases with traps to avoid test failures from undefined symbols while
keeping the structure consistent.
Add some tests for an ancient NetBSD sh bug
This adds 78 sub-tests to the t_expand:alternative test-case.
In old NetBSD shells - which means anything from May 1994 (when CSRG
BSD 4.4 lite was merged into NetBSD) until (early hours UTC) 26 Mar 2026,
12 of these new 78 sub-tests would fail.
The issue being tested here was fixed about 32 hours ago, along with the
completely unrelated fix for the recently introduced land mine off by one bug.
All these new sub-tests will pass in a /bin/sh from HEAD now.
No other shell I have to test (except bosh) fails any of these added
78 sub-tests (and bosh, which also fails plenty of the existing ones, fails
less of the new ones than the NetBSD sh did - and different sub-tests).
Of course, since I am adding tests to deliberately provoke what I already
knew from reading the source would fail in our shell, that is perhaps an
unfair comparison.
[11 lines not shown]
audio/rubberband: update to 4.0.0
Version 4.0.0 is a major release which adds a new API, RubberBandLiveShifter, which is simpler to use than the general RubberBandStretcher interface in cases where only pitch-shifting is required. For more general purposes the original interface is still the proper one.
The rest of the API is otherwise unchanged, so the library continues to be binary compatible with the 2.x and 1.x releases for existing applications. Code written to use earlier versions of the library can link and run against this version without alteration.
