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
fa2875bc6e03...
fa2875bc6e034b748f110a702f5be9ae5dd0426c
Oleksandr Byelkin
Merge branch 'bb-10.11-release' into bb-11.4-release
e3b0ca29389e...
e3b0ca29389e5b68ebd7a48df10afeb996ce2976
Sergei Petrunia
Cherry-pick lost commit: Improve comments and readability.
dd6c47268c80...
dd6c47268c80e5a5cb5477633099720fdedb873a
Rucha Deodhar
MDEV-39213: json range syntax crash

Analysis:
When json is being parsed, the step decreases without a out-of-bound check
resulting in failure.
Fix:
Before decreasing the step, check if it will result into out of bound.
d0501281ecb0...
d0501281ecb025b0d3ccf72b2d7e3e9473705f35
Sergei Golubchik
MDEV-39481 ASAN error on malformed WKB polygon

let's make is difficult for wkb and len to desync
bf90ff4a5415...
bf90ff4a5415fc5a2b4480284811dd0824e22ccb
Sergei Petrunia
Cherry-pick lost commit: JSON parsing: rename classes to cleaner names

Read_container_value -> Read_array.
Read_list_of_context -> Read_array_into_list
b66db0f23bd2...
b66db0f23bd253bfdcd8f475b017d49f36d05d9f
Marko Mäkelä
MDEV-32115: Log checkpoint race with wsrep_sst_method=rsync

Galera snapshot transfer (SST) using the default wsrep_sst_method=rsync
is prone to creating corrupted snapshots. The probability for this is
rather low and might only affect installations that include
ENGINE=InnoDB tables that contain FULLTEXT INDEX.

The function sst_disable_innodb_writes() aims to disable all InnoDB writes
during the time a snapshot transfer (SST) is in progress using the
default wsrep_sst_method=rsync.

The logic based on invoking log_make_checkpoint() almost works, except
for two things: We failed to ensure that fts_optimize_callback() has
stopped executing, and we did not block updates of the log checkpoint
header.

log_checkpoint_low(): Assert that writes to the log are allowed.

buf_flush_page_cleaner(): Do not try to advance the checkpoint while
wsrep_sst_method=rsync is in progress. This prevents the assertion
in log_checkpoint_low() from failing.

fts_optimize_pause(), fts_optimize_resume(): Pause and resume the
fts_optimize_callback().

sst_disable_innodb_writes(): Disable all background writers
before initiating the log checkpoint.

fts_optimize_callback(): Assert that wsrep_sst_method=rsync is not
active, and remove the previous incorrect attempt at fixing this race.
b100fbf49a12...
b100fbf49a129437434bf3b8457a4bf17f4eaf69
bsrikanth-mariadb
MDEV-39412: parse error reading tabs in ranges

Note:
while reading from information_schema.optimizer_context one level of unescaping
is already done i.e. (\\t becomes \t or \\\\t becomes \\t)

w.r.t the MDEV, there are 2 problems: -

1.
When reading from the sql script file, json parser is not able to parse
the range value in json_read_value() from json_lib.c
"ranges": [
            "(b\t\t\t\t\t\t) <= (b) <= (b???????)"
          ],
mainly the \t\t stuff, and hence a warning.
It also stops loading the context into memory.
Since, a new table is created with empty data, and without context,
we get Impossible WHERE noticed after reading const tables

2.
There is unescaping call being made in read_string() from sql_json_lib.cc
while parsing of the context. With this \\t was becoming \t.
However, print_range() from opt_range.cc already does escaping of the values.
The value "b\t\t\t" was in fact produced as "\b\\t\\t\\t".
Later, we try to compare range values from the query and the context.

Here a mismatch a found because, in one case there was escaping,
and in the other case escaping got removed.

Solutions
=========
For Problem 1. have escaping for ranges.
This should be done while dumping range values into the context.

For Problem 2. Remove unscaping call in read_string().
aa86e932a5c8...
aa86e932a5c878cf3e228405adc03ed2267e6537
ParadoxV5
MDEV-39418: Revert most of MDEV-39240 for MDEV-32188

MDEV-39240 fixed how servers before 11.5/11.4-enterprise
accepted timestamps beyond Year 2038 from row-based replication,
which were invalid until 11.5/11.4-enterprise’s MDEV-32188.
MDEV-39240 does not apply after MDEV-32188 extended the valid range,
so those versions should exclude this fix,
as if MDEV-32188 already covers it.

This commit reverts commits 3234045953 and most of f9c34a1442, keeping
only the tweak to the MTR script `include/check_type` for consistency.
8978a52132e4...
8978a52132e4c9bfc8886a9a0c8b3db41802b1ff
Oleksandr Byelkin
Merge branch '10.6' into bb-10.11-release
846bb70dc23d...
846bb70dc23d1877073acdbe6ccba22a6231bc80
Daniel Black
MDEV-39523 UBSAN on ST_COLLECT (has_cached_value)

UBSAN errored with UBSAN: load of value 165, which is not a valid value for
type 'bool' on SELECT ST_COLLECT.

This was Item_func_collect::val_str reading the has_cached_value. The
member variable has_cached_value was set to true later in this function
when it had a cached value. There was no initialization of
has_cached_value to false in the constructor.

We copy the cached value if the Item_func_collect is copied.
835df429bd43...
835df429bd4389968714f99dba735c26dc8deb4f
Oleksandr Byelkin
Merge branch '10.11' into bb-10.11-release
6e1c732fa162...
6e1c732fa162837c79dbb3dde20c28ede9a0d91b
Sergei Petrunia
Cherry-pick lost commit: Fixup to previous commit
676bfa7d14c7...
676bfa7d14c7bf42a22485edd137b5b915e100bf
Sergei Petrunia
Cherry-pick lost commit: Add unit test for json_read_object.
5f9a4a812df6...
5f9a4a812df67702ef9da3165f07abe49e027b28
Sergei Petrunia
Cherry-pick lost commit: Rename dump_XXXX() functions and make them more readable.
560d95f9d89f...
560d95f9d89fffc538c5e01da8f53ca2618d3e9e
Sergei Petrunia
Cherry-pick lost commit: Make JSON parsing helpers accept MEM_ROOT* argument, not THD.
4799aad65d74...
4799aad65d746a487f06c5399cc8f9f9dd9af943
Rucha Deodhar
MDEV-39449: Memory corruption (heap-buffer-overflow) in uint4korr and
Gcalc_function::count_internal, apparent partial stack looping in
Gcalc_function::count_internal and Assertion `(0)' failed in
Item_func_spatial_precise_rel::val_bool

Analysis:
ST_COVEREDBY() was linked with Item_func_spatial_precise_rel with
SP_COVEREDBY_FUNC, but the case was missing in val_bool() method.
This resulted in fall through switch leading to an assert/ASAN failure during

Fix:
Added the missing case and implemented it similar to WITHIN
(with MBR precheck + buffer). This fixes the crash and makes
ST_COVEREDBY() behave correctly.
467b06c9c03a...
467b06c9c03ae9f9d1e2a8a0c124e8d3c2c596f0
Sergei Petrunia
Cherry-pick lost commit: Rename: Read_list_of_ranges to Read_array_of_strings and move it to sql_json_lib.
422aa545a6ce...
422aa545a6ce10a2dc16d2976568a39a231065e0
Rucha Deodhar
MDEV-39213: json range syntax crash

Analysis:
When json is being parsed, the step decreases without a out-of-bound check
resulting in failure.
Fix:
Before decreasing the step, check if it will result into out of bound.
3e86ab4d00f4...
3e86ab4d00f4b20904f378bcaa66132a77a5093f
ParadoxV5
MDEV-39418: Revert most of MDEV-39240 for MDEV-32188

MDEV-39240 fixed how servers before 11.5/11.4-enterprise
accepted timestamps beyond Year 2038 from row-based replication,
which were invalid until 11.5/11.4-enterprise’s MDEV-32188.
MDEV-39240 does not apply after MDEV-32188 extended the valid range,
so those versions should exclude this fix,
as if MDEV-32188 already covers it.

This commit reverts commits 3234045953 and most of f9c34a1442, keeping
only the tweak to the MTR script `include/check_type` for consistency.
3d2ae78f843e...
3d2ae78f843ed1b5ba715439014aa7bbd1eceaa3
Dave Gosselin
MDEV-39494: UBSAN error on division by zero.

An incorrectly backported test from 11.x revealed an UBSAN error in 10.11, so
fix that problem by preventing a division-by-zero from happening.

Remove the other incorrectly backported tests and relabel the retained test
in terms of the current ticket.
32327e572bbd...
32327e572bbdfee6a2c2c60b4d37d3d1a0d61e3b
Sergei Golubchik
MDEV-39540 crash due to narrowing cast in update_ref_and_keys()
2393bb54d305...
2393bb54d3054c9400cc76ae6fcdd9d8da206599
PranavKTiwari
MDEV-38839: Fix assertion in close_thread_tables on CREATE TABLE...SELECT FOR UPDATE with MyISAM temp table in MIXED binlog mode

Cause: FOR UPDATE on MyISAM temp tables uses a write lock (no row-level locking), incorrectly marking a read as a write. This blocks binlog_truncate_trx_cache() and triggers an assertion.

Fix: In decide_logging_format(), check tbl->updating to detect real writes. For read-only access, mark as STMT_READS_TEMP_NON_TRANS_TABLE instead of write, preventing incorrect behavior.
20d7b6ef36e0...
20d7b6ef36e0a9fe4476e25517a3933562226df0
Sergei Golubchik
MDEV-39516 s3 curl_easy_setopt requires long values otherwise compile failure

update submodule to compile on fc44
200eb5365a4d...
200eb5365a4ded078cfbdb51e755d74885cfbc41
Sergei Golubchik
MDEV-39516 s3 curl_easy_setopt requires long values otherwise compile failure

update submodule to compile on fc44
11aa4deb1a57...
11aa4deb1a57e901b9aed14203e64baf95e7b7ff
sjaakola
MDEV-34784 unhandled FK dependency with DML vs DDL

Certain DDL statements (e.g. ALTER TABLE) require innodb table lock
on tables having foreign key constraint reference to the table
under DDL execution. This dependency is not added in write set
key information. However, tables being referenced to will be added
in the key information, so the table locking domain of DDL is only
partially recorded.

One harmful consequence of this missing dependency information happens
when a DML modifies a FK child table's row, which has NULL in the FK
referencing column. In such situation, the FK reference cannot be followed
during DDL execution, and there will be no FK parent table keys recorded
in the write set. Parallel applying (or multi-master access) of such DML
and DDL on the FK parent table will cause applying conflicts.

This  scenario is presented in a new mtr test added in this commit.
The commit has a fix for the DDL FK dependency handling by adding all FK
child table names in the write set key information.
The commit has also fixes for innodb lock0lock.cc error logging to report
lock connflicts of table and record locks correctly.
1053630fcad2...
1053630fcad2a3b4613312adaf96d1c3cc456786
Jan Lindström
MDEV-39413 wsrep unsafe handling of parameters

When server is started with unsafe parameter --exec could
return also error 134. Furthermore, --exed pkill could
return error 15. Added these error codes as accepted.
0af4790be6bd...
0af4790be6bd5be8ce68c272b35c5c13baf0c786
Sergei Petrunia
Cherry-pick lost commit: Fixup (2)
03c1512dfec2...
03c1512dfec2aabbda12cddbafb666d10d2f7997
Rucha Deodhar
MDEV-39213: json range syntax crash

Analysis:
When json is being parsed, the step decreases without a out-of-bound check
resulting in failure.
Fix:
Before decreasing the step, check if it will result into out of bound.
037174e70d80...
037174e70d803fd77bb6d7cd397d2e121472b1bb
Sergei Petrunia
Cherry-pick lost commit: Coding style renames: Saved_index_stats, Saved_table_stats
BuildBot (0.8.9) working for the MariaDB project.
Page built: Thu 07 May 2026 01:11:41 (UTC)