Home - Waterfall Grid T-Grid Console Builders Recent Builds Buildslaves Changesources - JSON API - About

Console View


Categories: connectors experimental galera main
Legend:   Passed Failed Warnings Failed Again Running Exception Offline No data

connectors experimental galera main
fd8c51e5a31c...
fd8c51e5a31c15c31f312bcbefcce14b12d23d97
Mohamed
MDEV-40423 use-of-uninitialized-value in Gis_point::get_data_as_wkt(String*, char const**) const

read_point_from_json() returned success for a GeoJSON position with
fewer than two numbers, leaving x and/or y uninitialized. They were
then stored in the WKB and read by ST_AsText().

Reject such positions as incorrect GeoJSON, since RFC 7946 requires
at least two numbers.
ef4c7459b843...
ef4c7459b8433603b306dc46618eccae9d2b6957
Dave Gosselin
MDEV-42078:  Map macOS errno 63 in main.create_notembedded

Maps errno 63 to 36 in the output of the first CREATE TABLE in
main.create_notembedded, as main.symlink does.  That statement creates
a table whose file name is 255 bytes and expects ENAMETOOLONG in the
error, which is 36 on Linux and 63 on macOS.  The test has failed on
macOS since d0b279f1852 added it.

Assisted-By: Claude Opus 5.5 <[email protected]>
da4147a61108...
da4147a6110842c9f657dfd4e2080858465fac50
Pekka Lampio
MDEV-38999: Galera - stale reads in explicit transactions

wsrep_must_sync_wait() skipped a statement's causal wait unconditionally
once a multi-statement transaction was open, regardless of which
wsrep_sync_wait bit was configured - so later statements could run
against a view no fresher than whatever BEGIN itself happened to check.
A timed-out wait's error also stayed sticky until commit/rollback,
breaking ROLLBACK itself.

Fix: only skip the wait once the transaction has made its first write or
locking read (SELECT ... FOR UPDATE/LOCK IN SHARE MODE, including via a
stored procedure CALL, autocommit statements, and UNION) - after that,
re-waiting risks a self-deadlock against the local applier. Clear a
timed-out wait's error immediately instead of leaving it sticky.

Tests: galera_MDEV-38999*.test cover the bitmask gap, the self-deadlock
risk, stored-procedure/UNION/autocommit locking reads, and the query
cache's independent wait path.

Assisted-by: Claude:claude-sonnet-5
d6a605bcff6b...
d6a605bcff6b7a5bd94cec759f9da3fe59105117
Oleksandr Byelkin
Merge branch '13.1' into bb-13.1-release
cda5e2a45b3f...
cda5e2a45b3f075373db25e69b4f3cfcdff20090
drrtuy
feat: MDEV-40672 implement basic support for the pluggable aggregate functions
c8e6ab229f03...
c8e6ab229f030119c19f3208d40f415decb41dae
bsrikanth-mariadb
MDEV-42186: Info leak with optimizer_replay_context

When @@optimizer_replay_context is set, the replay reports mismatches
between the context and the optimizer's statistics as warnings that name
tables, indexes and ranges. For a view, stored routine or trigger those
names can belong to objects the invoker has no privilege to see, for
example the base tables of a DEFINER view, or a key number and the
view's hidden predicate through a records_in_range() call.

Apply the same privilege checks the optimizer trace and the optimizer
context recorder already use:

* Optimizer_context_replay gets a missing_priv flag, set through
  missing_privilege(). Optimizer_context_replay::has_records() returns
  false once it is set, and every infuse_*()/store_*() entry point
  already bails out on !has_records(), so no warning is produced and no
  replayed data is used.
* opt_trace.cc: report_missing_privilege() also notifies the replay, and
  the checks for tables, views, stored routines and the security context
  no longer return early when only a replay is active.

Table-level SELECT is required, so column-level grants do not enable the
replay, even when they cover all columns. The flag is never cleared
within a statement. For a stored function or trigger the check runs when
it is called, so output for tables already optimized stays.

Add test opt_context_replay_view_leak.
bd4d5680ca4e...
bd4d5680ca4e7d8fd3b953e9f9d342599ac5c07c
Sergei Golubchik
MDEV-40406 hide #mysql50# prefix support behind the old mode

Disallow usage of #mysql50# prefix in db and table names,
only allow it under the old_mode=MYSQL50_TABLE_NAMES.

Even in the default old_mode the #mysql50# support isn't completely off,
such names are not rejected everywhere throughout the server, but only
in the parser. Rejecting them everywhere would need a lot of code to
cover various corner cases when a name is accepted under
MYSQL50_TABLE_NAMES and then the old_mode is cleared - see test cases.

So, the goal is only to make the prefix practically unusable,
preparing for its eventual demise.

This mode is always enabled on the slave side, otherwise any
unprivileged user on the master would be able to break replication.

Assisted-by: Claude:claude-opus-5-5
b6d1660317f7...
b6d1660317f7248ff14eabd17420a1e24874458e
Vladislav Vaintroub
MDEV-38741 mtr: do not suppress the reason of a client disconnect

The global suppressions of "Aborted connection", in mariadb-test-run.pl
and mtr_warnings.sql, hid the line that the client disconnect watcher
writes when it aborts a command: "Aborted connection N to db: 'x' user:
'u' host: 'h' (Client disconnected)". Nothing showed when the watcher
aborted a connection that it should have left alone. main.locale found
one, because its server log is in German and the English entry did not
match.

Make the two entries skip a line that ends in "(Client disconnected)".
Other aborted connections are suppressed as before. The tests that drop
a client on purpose accept the reason with mtr.add_suppression(),
details in PR#6035.

Assisted-by: Claude:claude-sonnet-5-5
b1f892f67fa0...
b1f892f67fa097dff82f276589790222388dd958
Vladislav Vaintroub
MDEV-38741 Abort the running statement when its client disconnects

A watcher thread subscribes to the OS notification that a client has
gone (e.g. TCP FIN or RST for a TCP socket, a gone client process for a
named pipe) and aborts the running statement like KILL CONNECTION does.
Controlled by the global variable disconnect_watcher. Details in
PR#6035.

Assisted-by: Claude:claude-sonnet-5-5
aab8cd7c0962...
aab8cd7c09620f1da45bc4ed9e641db00fd025ac
Vladislav Vaintroub
MDEV-42258: Windows ignores --back-log, simultaneous connects are refused

On Windows, listen() with a positive backlog is limited to a small value,
so a burst of simultaneous connections (e.g. 256 clients) overflows the
accept queue and some are refused with WSAECONNREFUSED (10061).

For TCP listening sockets, including the extra port, pass
SOMAXCONN_HINT(back_log) when back_log >= 200, the range it supports
(200-65535). Smaller values are passed as before.

Assisted-by: Claude:claude-sonnet-5-5
a40034db4cc4...
a40034db4cc4e50ee4f2102778bbe16365d4d563
Hemant Dangi
MDEV-42231: galera_sst_check_port_ancestry fails on noexec vardir

Issue:
The test generates a driver script under $MYSQLTEST_VARDIR/tmp and
executes it directly. On a host where that directory is on a
noexec-mounted tmpfs, execution fails with "Permission denied"
regardless of the script's mode bits, since noexec is enforced by the
kernel against the mount itself, not against the file's own
permissions.

Solution:
Invoke the generated driver script through bash explicitly instead of
relying on the kernel executing it directly via its shebang; running
it through an interpreter only requires the interpreter itself to be
executable, not the script file.
95d1d27bfa1e...
95d1d27bfa1e0a83df66ea87cc9ee5015d1ee9ab
Oleksandr Byelkin
Merge branch 'main' into bb-13.2-release
7c0d77ef0d62...
7c0d77ef0d62de35fef7e6a0d622884e384c092c
ParadoxV5
forgot to update this test
7115ec71bd45...
7115ec71bd45c03f29cb496bbe445d71a08153a4
ParadoxV5
missed this spot
5ecc55e9b027...
5ecc55e9b027cdb086e77d30d2bfec70ea606575
bsrikanth-mariadb
MDEV-42044: I_S.OPTIMIZER_CONTEXT exposes rows, DDL and statistics ...

Optimizer Context has DDLs of used tables and VIEWs, table statistics,
and even captured table rows which include all, even the columns that
the query doesn't read.

The user running the query might not have access to some of this
information. Making it available in the optimizer context would create
an opportunity to bypass the security controls.

There is a similar issue in the Optimizer Trace. It is solved by NOT
producing optimizer trace if it would expose data that's not available
otherwise. We have to extend that logic for context recorder as well.

Optimizer Trace relied on opt_trace_disable_if_no_tables_access(), to
check if the query object had privilege to execute.

Solution
========
Run opt_trace_disable_if_no_tables_access() once in
mysql_execute_command(), after the trace, and recorder are created.
Along with it set missing_priv flag in the recorder object if needed.
This flag is used to skip recording the stats, and not dump the
context at the end of query execution.
5e89a686697d...
5e89a686697df8f228fe1ac62da2f2b6917fd7ea
Alexey Yurchenko
MGL-301 Add MTR tests and fix error reporting
5aa4d0f75b46...
5aa4d0f75b4671032849c7c81f14e28dfaba7a9a
forkfun
MDEV-42222 String copy must not share a heap buffer

A copy of a String pointed to the buffer of the original and kept its
capacity without owning the buffer. Condition pushdown copies items
with shallow_copy(): all String members of the copy, and
Arg_comparator::value1/value2 of a copied comparison, shared the
buffers of the original item. When the original item reallocated
a buffer for a longer value, the copy kept using the freed one,
e.g. UPPER, CAST(.. AS CHAR), STR_TO_DATE and JSON_EXTRACT
comparison on 2nd execution of a prepared statement.

The copy constructor of a String that owns its buffer copies the data
now. A copy of a String that doesn't own its buffer points to the same
data and has no capacity.

Assignment still makes the String point to the data of the other one,
but without capacity. No code that writes through an assigned String
was found.

SFORMAT copied every String argument twice per row. It passes them by
reference now, to avoid copying the data.

Tests: main.in_subq_cond_pushdown and main.ctype_ucs.

Assisted-By: Claude:claude-sonnet-5-5
5596dcbfd813...
5596dcbfd81368f8e5fef64ddd955e7d5e1cfdcd
Vladislav Vaintroub
MDEV-42258: Windows ignores --back-log, simultaneous connects are refused

On Windows, listen() with a positive backlog is limited to a small value,
so a burst of simultaneous connections (e.g. 256 clients) overflows the
accept queue and some are refused with WSAECONNREFUSED (10061).

For TCP listening sockets, including the extra port, pass
SOMAXCONN_HINT(back_log) when back_log >= 200, the range it supports
(200-65535). Smaller values are passed as before.

Assisted-by: Claude:claude-sonnet-5-5
52efdeefd0a9...
52efdeefd0a9c9c0b5d0995a84c1d70fb5d64898
Oleksandr Byelkin
Merge branch 'bb-13.1-release' into bb-13.2-release
52391ebe4feb...
52391ebe4feb56c8ccbbf33a29ea3acbb7b7cea7
drrtuy
Item_sum_test_plugin_first shallow copy changed b/c its implementation leaked memory.
4c41cfb34a75...
4c41cfb34a75a01eb6431f5a0f05ee62a3a11efd
Vladislav Vaintroub
MDEV-38741 mtr: do not suppress the reason of a client disconnect

The global suppressions of "Aborted connection", in mariadb-test-run.pl
and mtr_warnings.sql, hid the line that the client disconnect watcher
writes when it aborts a command: "Aborted connection N to db: 'x' user:
'u' host: 'h' (Client disconnected)". Nothing showed when the watcher
aborted a connection that it should have left alone. main.locale found
one, because its server log is in German and the English entry did not
match.

Make the two entries skip a line that ends in "(Client disconnected)".
Other aborted connections are suppressed as before. The tests that drop
a client on purpose accept the reason with mtr.add_suppression(),
details in PR#6035.

Assisted-by: Claude:claude-sonnet-5-5
4c1920a46764...
4c1920a46764488d1449f65eb18a128bc8336c67
Vladislav Vaintroub
MDEV-38741 Abort the running statement when its client disconnects

A watcher thread subscribes to the OS notification that a client has
gone (e.g. TCP FIN or RST for a TCP socket, a gone client process for a
named pipe) and aborts the running statement like KILL CONNECTION does.
Controlled by the global variable disconnect_watcher. Details in
PR#6035.

Assisted-by: Claude:claude-sonnet-5-5
44fa4f72d5d7...
44fa4f72d5d7168c1b4abf6d2ddf18473ad30ccf
Pekka Lampio
MDEV-38999 followup: fix galera_sr.mysql-wsrep#215 regression

wsrep_must_sync_wait() now performs the causal wait on the first
real statement of an explicit transaction instead of skipping it as
soon as the transaction was merely BEGIN'd. mysql-wsrep#215
deliberately freezes node_1's local applier via a debug sync point
and then expects node_1's own first statement in the transaction to
proceed without waiting for that frozen apply - which the old,
buggy skip-on-BEGIN behaviour happened to allow, but the fix
correctly no longer does.

Disable wsrep_sync_wait for node_1's session before entering the
transaction, mirroring the same workaround node_1a's connection
already uses for the identical reason.

Co-Authored-By: Claude Sonnet 5 <[email protected]>
36e358d1a88a...
36e358d1a88a216a962ace89f4f91da89b74371b
drrtuy
MDEV-41352 Pluggable Aggregate Functions now supports FILTER syntax.
29596176415e...
29596176415e7c2455f3049d2b41e29c2d4fd969
ParadoxV5
MDEV-21322 Report Slave Progress to the Master

(Draft: Commit message is staged on the PR.)
2676164b5300...
2676164b5300b8dfb9dd6ff39a99c38de0cfdb59
drrtuy
MDEV-41270: every PAF implementation decides whether it supports DISTINCT argument or not.
1ba6beea9d86...
1ba6beea9d86ab367b2969c107e28f6a6fd79d2d
Oleksandr Byelkin
Fix crossbreed of MDEV-41491 and MDEV-35254 (plugins.parsec crash).

Check length first.
19c90297d6fe...
19c90297d6feee0a50fde600b7e65eb07f8f777c
Sergei Golubchik
stabilize I_S.VECTOR_INDEXES.INDEX_SIZE after an INSERT

innodb needs time for the value to stop changing. wait for it.
110fa80d1de0...
110fa80d1de019140e8c2c27d619a8c211bd51a3
drrtuy
MDEV-41269 PAF fix for DISTINCT + literal argument.
0ec19ff0b417...
0ec19ff0b417da1dc69ad1e0fda5c70fccccf86d
ParadoxV5
MDEV-21322 Report Slave Progress to the Master

(Draft: Commit message is staged on the PR.)
0e489b743823...
0e489b743823b455a94cee502e081f5eb98e99f1
Jan Lindström
MDEV-42234 : Galera test failure on galera.galera_ws_datatypes

Re-record after fk name change. Test change only.
0d2e564a68bb...
0d2e564a68bb023e929f70a0578170a8ada7760a
sjaakola
MDEV-41597: Do privilege checks of triggers and views before TOI

CREATE TRIGGER, CREATE VIEW and ALTER VIEW did some of their privilege
checks only after TOI had replicated the statement. The applier runs
with all privileges, so a statement refused on the originating node
was still applied by the other nodes:
- the DEFINER clause (sp_process_definer(), which requires SET USER
  for a DEFINER other than the current user), for all three
  statements, creating the trigger or view with a DEFINER the user
  was not allowed to use
- the column privileges of a view (ER_COLUMNACCESS_DENIED_ERROR),
  creating a view that gives more privileges than the user has on
  the underlying tables

ALTER VIEW without a DEFINER clause also replicated the wrong
definition. fill_defined_view_parts(), which takes DEFINER, ALGORITHM
and SQL SECURITY from the existing view, ran after the replicated
statement had been built, so the other nodes got the current user as
DEFINER and the default SQL SECURITY.

Do the checks before TOI begins, as is already done for stored
routines and events:
- mysql_create_or_drop_trigger() calls sp_process_definer() for
  CREATE TRIGGER before WSREP_TO_ISOLATION_BEGIN, and
  Table_triggers_list::create_trigger() no longer calls it.
- mysql_create_view() calls fill_defined_view_parts() (ALTER VIEW)
  and sp_process_definer() early, and begins TOI only after all
  checks, just before mysql_register_view().

The order of checks changes for all builds: the DEFINER error is now
reported before some errors that were found later in the statement.

The test galera.galera_toi_definer_check checks that:
- CREATE TRIGGER, CREATE VIEW and ALTER VIEW refused for a foreign
  DEFINER on node_1 are not applied on node_2
- CREATE VIEW refused for missing column privileges on node_1 is not
  applied on node_2
- ALTER VIEW without a DEFINER clause keeps the same DEFINER and
  SQL SECURITY on both nodes

Assisted By: Claude Opus 5.5
011c00af5658...
011c00af5658268e92d019e32a4b85c7dbaeab2c
ParadoxV5
MDEV-21322: Delete extra `remove_slave()` call

The `Ack_receiver::remove_slave()` call in
`kill_zombie_dump_threads()`’s loop callback is not necessary,
because binlog dump threads that have called `Ack_receiver::add_slave()`
will call `remove_slave()` during cleanup anyway.
This commit erases this extraneous call, for it wastes the dump thread’s
normal `remove_slave()` step, which locks `Ack_receiver`’s global mutex.
MDEV-21322 (report ACKs on SHOW SLAVE HOSTS) also has trouble
matching its synchronization needs with this global lock acquisition.
BuildBot (0.8.9) working for the MariaDB project.
Page built: Sat 14 Nov 2026 01:00:19 (UTC)