Fix PXB-3170 - Test failure in keyring_pxb_2275.sh

8.0 Fix PXB-3181 - Duplicate timestamp printed when using innodb-use-nati…

Fix PXB-3003 - Race Condition in log_files_find_and_analyze

Fix PXB-3141 - fix folder permission on fifo get

CMake Error at cmake/mysql_version.cmake:65 (MYSQL_GET_CONFIG_VALUE):
  MYSQL_GET_CONFIG_VALUE Macro invoked with incorrect arguments for macro
  named: MYSQL_GET_CONFIG_VALUE
Call Stack (most recent call first):
  cmake/mysql_version.cmake:218 (GET_MYSQL_VERSION)
  CMakeLists.txt:577 (INCLUDE)

1159ccb - Added a new entry into MYSQL_VERSION file. PXB has a custom
MYSQL_GET_CONFIG_VALUE macro which accepts a 3rd parameter to instruct
which file we are parsing from. Adjuster MYSQL_VERSION_STABILITY
to be read from MYSQL_VERSION.

Bumped smart memory required server.

Fix PXB-3173 - Partial download functionality regression

PXB-3186 - Merge 8.0.35

Fixed PXB-3168 - Under high write load, backup fails with "log block …

Release 8.0.35-30

8.0 Fix PXB-3210: PXB fails to build on macOS since 8.0.33-28 due to FIND_PRO…

8.0 Fix PXB-2797: Schema mismatch when importing table with full-text index f…

… 8.0.33

fix:https://perconadev.atlassian.net/browse/PXB-3130

    Backup using xtrabackup 8.0.30, and then prepare using xtrabackup 8.0.33. Th                                              e error is as follows:

    InnoDB: Assertion failure: log0recv.cc:4353:log.m_files.find(recovered_lsn)                                               != log.m_files.end()
    I0825 22:33:01.738934 05155 ???:1] xtrabackup80 - InnoDB: thread 13998887390                                              6432InnoDB: We intentionally generate a memory trap.
    I0825 22:33:01.738951 05155 ???:1] xtrabackup80 - InnoDB: Submit a detailed                                               bug report to https://jira.percona.com/projects/PXB.
    I0825 22:33:01.738968 05155 ???:1] xtrabackup80 - InnoDB: If you get repeate                                              d assertion failures or crashes, even
    I0825 22:33:01.738985 05155 ???:1] xtrabackup80 - InnoDB: immediately after                                               the mysqld startup, there may be
    I0825 22:33:01.739001 05155 ???:1] xtrabackup80 - InnoDB: corruption in the                                               InnoDB tablespace. Please refer to
    I0825 22:33:01.739018 05155 ???:1] xtrabackup80 - InnoDB: http://dev.mysql.c                                              om/doc/refman/8.0/en/forcing-innodb-recovery.html
    I0825 22:33:01.739035 05155 ???:1] xtrabackup80 - InnoDB: about forcing reco                                              very.

    Through analysis, it was found that it was caused by the type being out of b                                              ounds.
    Multiple uint32_ The value obtained by multiplying the values of type t is s                                              till uint32_ Type t, when the result value is greater than uint32_ After the ran                                              ge that t can represent, an incorrect return value will be obtained

    So, type improvement is needed, which has been validated and passed

PXB-3283: Column %s precise type mismatch error while importing a tablespace (8.0)

PKG-56 Binary Tarballs of PXC and PXB without openssl libs included

fix:Backup using xtrabackup 8.0.30, and then prepare using xtrabackup…

Bump up version to 8.0.35-31

Add ubuntu noble pxb

Release-8.0.35-31

PKG-82 update changelog for rpm packages for PXB and PXC

Release-8.0.35-31

PXB-3302: GTID of the last change output truncated in Xtrabackup back…

…dated

PXB-3319 Tarballs have dependency on libgcrypt.so.11

Fix centos 7 repos

deleted: storage/innobase/xtrabackup/doc/
modified:   CMakeLists.txt

PXB-3316 Remove doc folder to fix Snyk issues (8.0)