py-owslib: updated to 0.36.0
0.36.0
1013 fix csapi failing tests
Remove legacy setuptools.command.text
remove comments from xml, because it may fail parsing it
Fix FutureWarning when truth-testing XML element
docs: update WMS example
capture dct:spatial as bbox, if it contains a box
use only pyproject configuration
delegate HTTP 401 and 403 to Python requests
Update dev setup docs to pyproject.toml
Handle WFS version mismatch
py-cbor2: updated to 6.1.2
6.1.2
- Fixed incorrect tracking of string references for definite-length text strings of length greater
than 65536
- Fixed ``cbor2.load()`` crash caused by incorrect handling
of internal read buffer extension during stream deserialization.
[Dexter] Add label nodes for line references
This patch adds a !label node to Dexter scripts, which references lines at
a position in the source program marked with "!dex_label <identifier>". Each
label use can be given a positive or negative offset, and file lookup is
based on the provided --source-root-dir (using the test file's directory if
none is provided).
[clang][bytecode] Only count taken jumps as steps (#201845)
There are several large array declarations in llvm-libc. They usually
look similar to this:
```c++
alignas(16) inline constexpr LogRR LOG_TABLE = {
{
{Sign::POS, 0, 0_u128},
{Sign::POS, -134, 0x8080abac'46f38946'662d417c'ed007a46_u128},
{Sign::POS, -133, 0x8102b2c4'9ac23a4f'91d082dc'e3ddcd38_u128},
{Sign::POS, -133, 0xc2492946'4655f45c'da5f3cc0'b3251dbd_u128},
{Sign::POS, -132, 0x820aec4f'3a222380'b9e3aea6'c444ef07_u128},
// ...
```
the `_u128` is a user-defined literal, so the hex constant to the left
of it is actually a `StringLiteral` and the UDL converts that to a
different type by iterating over all chars. It calls one function per
char, and that function contains the usual switch statement over all
ASCII characters.
[15 lines not shown]
Revert "[BOLT][AArch64] Transform cmpbr ~> cmp + br when inversion not possible (#185731)" (#202309)
This reverts commit 6b13656fd8386f979e061cc97e32b607ee3fcdf4.
We have identified various bugs hence reverting:
* relaxLocalBranches() should account for BB growth and adjust subsequent BB offsets in fragment
* multiple parallel workers are sharing the same allocator in DataflowInfoManager
* liveness is run lazily, potentially after the CFG has been modified
config: add functional 26.7 / 15.1
* Rebase for 15.1-RC3, volatile/26.7 for now
* OpenSSL 3.5 with FIPS, ports-only for now
* plugins and core as -devel only for now
* SMP configs adjusted for stale options
* Removed ndproxy
* PHP 8.5
To review:
# diff -ur config/26.1 config/26.7
[analyzer] Trigger checkLifetimeEnd callback from CFGLifetimeEnds element
This patch adds handling of the `CFGLifetimeEnd` element to the CSA, and
produces a newly created callback `checkLifetimeEnd` for each occurrence
of it.
It is useful to implement detection of dangling pointers as in:
```
void su_use_after_block () { int* p=0; { int x=1; p=&x; } *p = 2; }
// ^ p dangles
```
This patch does not implement the check itself. it is motivated by the
discussion in
https://discourse.llvm.org/t/what-is-the-status-of-scopeend-and-scopebegin/90861
--
[4 lines not shown]
[flang][flang-rt] Treat REAL(2)/COMPLEX(2) as C-interoperable types (#201888)
IEEE-754 binary16 ("half") maps cleanly to the C `_Float16` type
(ISO/IEC TS 18661-3), but flang previously rejected `REAL(KIND=2)` and
`COMPLEX(KIND=2)` in C-interoperable contexts. Make `REAL(KIND=2)` and
`COMPLEX(KIND=2)` into actual interoperable types.
`ISO_C_BINDING` now exports the gfortran-compatible named constants
`c_float16` and `c_float16_complex` (both value 2), the kind parameter
for the half-precision C interoperable types.
Assisted-by: AI
py-aiohttp: updated to 3.14.1
3.14.1 (2026-06-07)
Bug fixes
- Fixed a race condition in :py:class:`~aiohttp.TCPConnector` where closing the connector while a DNS resolution was in-flight could raise :py:exc:`AttributeError` instead of :py:exc:`~aiohttp.ClientConnectionError` -- by :user:`goingforstudying-ctrl`.
- Fixed ``CancelledError`` not closing a connection -- by :user:`aiolibsbot`.
- Tightened up some websocket parser checks -- by :user:`Dreamsorcerer`.
- Fixed :class:`~aiohttp.CookieJar` dropping the host-only flag of cookies when persisted with :meth:`~aiohttp.CookieJar.save` and reloaded with :meth:`~aiohttp.CookieJar.load`, so a cookie set without a ``Domain`` attribute is again scoped to the exact host that set it after a reload; the absolute expiration deadline is now persisted as well, so a reloaded cookie keeps its original lifetime instead of being rescheduled from the load time. :meth:`~aiohttp.CookieJar.load` now replaces the jar contents rather than merging onto prior state, and loaded cookies pass through the same acceptance rules as :meth:`~aiohttp.CookieJar.update_cookies`, so a cookie for an IP-address host is dropped when loaded into a jar created without ``unsafe=True`` -- by :user:`bdraco`.
- Scoped :class:`~aiohttp.DigestAuthMiddleware` credentials to the origin of the first request it handles, so a redirect to a different origin no longer triggers a digest response computed from the configured credentials; a challenge from another origin is only answered when that origin falls within a protection space advertised by the anchor origin through the RFC 7616 ``domain`` directive -- by :user:`bdraco`.
- Fixed the C HTTP parser not enforcing ``max_line_size`` on a request target or response reason phrase that is split across multiple reads; each fragment was checked on its own, so an accumulated line could exceed the limit without raising ``LineTooLong``. The accumulated length is now checked, matching the pure-Python parser -- by :user:`bdraco`.
- Changed :class:`~aiohttp.TCPConnector` to reject legacy non-canonical numeric IPv4 host forms such as ``2130706433``, ``017700000001`` and ``127.1`` with :exc:`~aiohttp.InvalidUrlClientError`; only canonical dotted-quad IPv4 literals are now treated as IP address literals, while every other host is sent through the configured resolver -- by :user:`bdraco`.
[10 lines not shown]
