PHP digest — 16 October 2026
Seven developments. The vote on exceptions for invalid number-base input opened, Laravel 13.37 shipped, PHPUnit
13.4.3 and 12.5.40 fixed test-dependency, hook-method and Open Test Reporting bugs, and Symfony published details of
the 8.2 #[Lock] controller attribute. Later in the day, the PDO binary parameters RFC opened for discussion, a
case-insensitive ini_get_all() RFC was announced, and the Uri\QueryParams author replied to the 9 October review.
Vote opens on exceptions for invalid number-base input
On 16 October the author opened the vote on the
number base functions RFC
(voting thread). This is the date announced on 9 October. If accepted,
bindec(), octdec(), hexdec() and base_convert() would throw a plain Exception in PHP 8.7 for characters
that are invalid in the given base. Today they ignore those characters with an E_DEPRECATED notice, which they
have done since PHP 7.4. The single primary vote needs a 2/3 majority and closes on 2026-11-01 at 15:30 UTC. At about
10:05 UTC the interim count was 3–0–0. That is not a result. See the RFC page.
Laravel 13.37
Laravel v13.37.0 was tagged on 16 October at 05:00 UTC. It is mostly fixes. Several concern queue and scheduler locks:
- a race condition with jobs that use both
onOneServer()andwithoutOverlapping()(#62007); - unique locks are now released when pushing a job (#62010) or a queued listener (#62045) to the queue fails,
and unique queued listener locks are released under
Queue::fake()(#62025).
Other changes:
queue:failed --queue(#61971), andqueue:forgetaccepts several IDs (#61901);migrate:statusno longer reports skipped migrations as pending (#61989);- a
strictoption forRule::numeric()(#62031); - JPEG XL support in the Image API (#62019);
encrypted:objectandencrypted:collectioncasts no longer always count as dirty (#62032);- fixes for N+1 queries with nested JSON:API relationships (#62000) and for several Eloquent relation queries.
PHPUnit 13.4.3 and 12.5.40
PHPUnit 13.4.3 and 12.5.40 were released on 16 October and contain only fixes. Both releases fix the following:
- Some dependencies were never checked: those listed after a dependency on a test that returns no value, or after a dependency on a larger test. Tests then ran instead of being skipped when such a dependency had not passed.
- Process isolation failed when the test class namespace began with a name that the child process imports, such as
CodeCoverageorFacade. - An unserializable data set or dependency value, such as a closure, aborted the whole run.
- When a before-first-test, after-last-test or hook method errored, failed or skipped the test, the remaining methods of the same kind were still called. As a result, tests were reported with the wrong outcome.
- The progress output and counts were wrong when a before-first-test method errored or failed.
- The Open Test Reporting XML logfile had missing or duplicate start/end events, and it was not well-formed when names,
messages or exception strings contained
]]>, invalid UTF-8 or characters not allowed in XML, such as ANSI escapes.
The two release notes differ in detail. In 13.4.3, a test with several outcomes is now reported with its most severe outcome, and the fixes for invalid XML also cover test output.
Symfony 8.2: #[Lock] controller details
The 11 October digest noted the merged #[Lock] attribute.
A 16 October post describes how it behaves:
- By default, a competing request gets
409 Conflict.blocking: truewaits instead, with no timeout of its own.read: truetakes a shared lock, andmethods:limits the lock to some HTTP methods. - Keys can be expressions or
{name}placeholders taken from route parameters (#66784). Placeholders now also work in#[RateLimit]keys. A controller can receive the acquiredLockInterface/SharedLockInterface(#66697). - The default TTL is 30 seconds and is not refreshed automatically. If the lock expires before the controller
finishes, another request can acquire it. For a
StreamedResponse, the lock is held until the content has been sent. - Unless the key depends on controller arguments, the lock is acquired before the arguments are resolved and before
#[IsGranted]is checked, whatever order the attributes are in. A user without access can therefore get409instead of403.
This is the 8.2 development branch, not a released version.
PDO binary parameters RFC opens for discussion
The PDO binary parameter support RFC moved from draft to Under Discussion
(version 0.4), and the author opened the thread at 19:34 UTC. It
proposes either a new PDO::PARAM_BINARY data type or a binary flag for PDO::PARAM_STR/PDO::PARAM_LOB, so that
drivers handle binary data consistently. The author asked for MySQL and PostgreSQL feedback before a vote.
A six-point review from Ilia Alshanetsky followed at 20:43 UTC. It argues
that PARAM_LOB is already binary in some drivers, that a fallback to strings corrupts data in pdo_pgsql and pdo_mysql,
that neither representation degrades safely in drivers that do not know it, and that the ODBC hex case is a driver bug.
The RFC targets "Next PHP 8.x" and has no vote date. See the RFC page.
RFC: case-insensitive extension names in ini_get_all()
A new RFC, announced
at 16:51 UTC, would make ini_get_all() match extension names case-insensitively (ASCII, independent of the locale), like
extension_loaded(), get_extension_funcs() and phpversion() already do. Today ini_get_all('Pcre') warns and returns
false. It is proposed for PHP 8.7 and needs a 2/3 majority. The author plans to open the vote two weeks after the
announcement if no further discussion comes up. See the RFC page.
Uri\QueryParams: author answers the review
The author of the query parameters RFC
replied to the 14-point review from 9 October. They would drop
$maxQueryStringLength, rename list() to toList() and parseWhatWg() to parseWhatWgUrlSearchParams(), make the RFC 1866
and RFC 3986 parsers reject invalid query syntax, narrow the value type of append()/set(), and add byte-based and
WHATWG-compatible UTF-16 sorting. They keep parseRfc3986(), hasValue(), deleteValue() and withArray(). These are stated
plans: the RFC page has not been edited since 15 October. See the RFC page.
Coverage
At 10:01 UTC the 32 due feed, release and index sources were collected successfully. The 25 daily package,
adoption, support-window and advisory sources were not due and keep their 16:01 UTC data from 15 October. health
reports all 57 sources ok and none stale. The official RFC index has 951 entries. throw_error_for_invalid_characters_for_number_base
is now listed as voting, next to end_pear_endorsement (vote ends 19 October) and reldateformatter (vote ends
22 October). The 04:01 UTC run found nothing new, so this edition starts at 10:01 UTC. The facts above come from the
RFC page, the internals voting thread, the GitHub release pages and the Symfony post.
At 22:01 UTC all 57 sources, including the daily ones, were collected successfully, and health reports none stale.
The RFC index now has 952 entries. It adds case_insensitive_ini_get_all as under discussion, and pdo_binary changed from
draft to under discussion. The last three sections come from the RFC pages and internals messages. A SymfonyCon
speaker announcement and a Laravel News post about the rule builders already covered in the
14 October digest were skipped.