{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":123367186,"defaultBranch":"10.4","name":"mariadb-server","ownerLogin":"codership","currentUserCanPush":false,"isFork":true,"isEmpty":false,"createdAt":"2018-03-01T01:52:50.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/1644626?v=4","public":true,"private":false,"isOrgOwned":true},"refInfo":{"name":"","listCacheKey":"v0:1717710988.0","currentOid":""},"activityList":{"items":[{"before":"1bf0950b191aaaa181068551fa241c9d09e6c7c3","after":"5b39ded713d021e7ec76f8f550b43678821eae22","ref":"refs/heads/10.11","pushedAt":"2024-06-12T00:23:10.000Z","pushType":"push","commitsCount":47,"pusher":{"login":"codership-jenkins","name":null,"path":"/codership-jenkins","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/8788800?s=80&v=4"},"commit":{"message":"MDEV-34156 InnoDB fails to apply the redo log for compressed tablespace\n\nProblem:\n=======\nDuring recovery, InnoDB fails to apply the redo log for\ncompressed tablespace. The reason is that InnoDB assumes\nthat pages has been freed while applying the redo log for it.\nDuring multiple scan of redo logs, InnoDB stores the freed\npage information when it have sufficient buffer pool pages.\nOnce it ran out of memory, InnoDB doesn't store freed page\ninformation. But InnoDB assigns the freed page ranges to tablespace\nin recv_init_crash_recovery_spaces() even though\nInnoDB doesn't have complete freed range information.\nWhile applying the redo log, InnoDB wrongly assumes that page\nhas been freed and it could lead to corruption of tablespace.\nThis issue is caused by commit 941af1fa581a799e59ddc3afcae965852aeceb00 (MDEV-31803)\nand commit 2f9e264781f702b8da1ed418ac9f4f5e8f8aa843 (MDEV-29911).\n\nSolution:\n========\nDuring recovery, set recovery size and freed page information\nfor all tablespace irrespective of memory.","shortMessageHtmlLink":"MDEV-34156 InnoDB fails to apply the redo log for compressed tablespace"}},{"before":"a02773f7c000273dd823df6bb386c4d735c3dcc7","after":"f2eda615798d6d879a913a44c22d5dd0fc7ed8c9","ref":"refs/heads/10.5","pushedAt":"2024-06-12T00:23:10.000Z","pushType":"push","commitsCount":21,"pusher":{"login":"codership-jenkins","name":null,"path":"/codership-jenkins","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/8788800?s=80&v=4"},"commit":{"message":"MDEV-33616 workaround libmariadb bug : mysql_errno = 0 on failed connection\n\nThe bug can happens on macOS, if server closes the socket without sending\nerror packet to client. Closing the socket on server side is legitimate,\nand happen e.g when write timeout occurs, perhaps also other situations.\n\nHowever mysqltest is not prepared to handle mysql_errno 0, and erroneously\nthinks connection was successfully established.\n\nThe fix/workaround in mysqltest is to treat client failure with\nmysql_errno 0 the same as CR_SERVER_LOST (generic client-side\ncommunication error)\n\nThe real fix in client library would ensure that mysql_errno is set\non errors.","shortMessageHtmlLink":"MDEV-33616 workaround libmariadb bug : mysql_errno = 0 on failed conn…"}},{"before":"699d38d9512218531b9fe7569600ec0619cc6f71","after":"fcd21d3e40a8739ca6813ac3a098ebf8d5fd5475","ref":"refs/heads/10.6","pushedAt":"2024-06-12T00:23:10.000Z","pushType":"push","commitsCount":39,"pusher":{"login":"codership-jenkins","name":null,"path":"/codership-jenkins","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/8788800?s=80&v=4"},"commit":{"message":"MDEV-34355: rpl.rpl_semi_sync_no_missed_ack_after_add_slave ‘server_3 should have sent…’\n\nThe problem is that the test could query the status variable\nRpl_semi_sync_slave_send_ack before the slave actually updated it.\nThis would result in an immediate --die assertion killing the rest\nof the test. The bottom of this commit message has a small patch\nthat can be applied to reproduce the test failure.\n\nThis patch fixes the test failure by waiting for the variable to be\nupdated before querying its value.\n\ndiff --git a/sql/semisync_slave.cc b/sql/semisync_slave.cc\nindex 9ddd4c5c8d7..60538079fce 100644\n--- a/sql/semisync_slave.cc\n+++ b/sql/semisync_slave.cc\n@@ -303,7 +303,10 @@ int Repl_semi_sync_slave::slave_reply(Master_info *mi)\n reply_res= DBUG_EVALUATE_IF(\"semislave_failed_net_flush\", 1,\n net_flush(net));\n if (!reply_res)\n+ {\n+ sleep(1);\n rpl_semi_sync_slave_send_ack++;\n+ }\n }\n DBUG_RETURN(reply_res);\n }","shortMessageHtmlLink":"MDEV-34355: rpl.rpl_semi_sync_no_missed_ack_after_add_slave ‘server_3…"}},{"before":"db5030c31caa55fdbecf2634718b73dcccb8f7b0","after":"3b4ab9379dd10331935535dbd2dfe27da67310ac","ref":"refs/heads/10.6-MDEV-33064-fix","pushedAt":"2024-06-10T15:15:41.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"denis-protivensky","name":"Denis Protivensky","path":"/denis-protivensky","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/9651639?s=80&v=4"},"commit":{"message":"Ignore wsrep_streaming_log table changes on SR trx fragment removal","shortMessageHtmlLink":"Ignore wsrep_streaming_log table changes on SR trx fragment removal"}},{"before":"4e785bd2048237fda256b5f7d13323a3b305c0f8","after":"827d90d75756126b61209818957d0bdf7de16b64","ref":"refs/heads/10.6-MDEV-28452","pushedAt":"2024-06-10T08:43:28.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"plampio","name":"Pekka Lampio","path":"/plampio","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/51317842?s=80&v=4"},"commit":{"message":"Improved MTR test MDEV-28452 by removing a sleep.","shortMessageHtmlLink":"Improved MTR test MDEV-28452 by removing a sleep."}},{"before":"a8a1dc2abe8d87f681f07f2c434bab525a4be41c","after":"9327ab46864a17b8bc66bd324a025c3d6b5292c2","ref":"refs/heads/10.6-MDEV-31658","pushedAt":"2024-06-10T07:35:29.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"janlindstrom","name":"Jan Lindström","path":"/janlindstrom","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6338705?s=80&v=4"},"commit":{"message":"MDEV-31658 : Deadlock found when trying to get lock during applying\n\nProblem was that there was two non-conflicting local idle\ntransactions in node_1 that both inserted a key to primary key.\nThen two transactions from other nodes inserted also\na key to primary key so that insert from node_2 conflicted\none of the local transactions in node_1 so that there would\nbe duplicate key if both are committed. For this insert\nfrom other node tries to acquire S-lock for this record\nand because this insert is high priority brute force (BF)\ntransaction it will kill idle local transaction.\n\nConcurrently, second insert from node_3 conflicts the second\nidle insert transaction in node_1. Again, it tries to acquire\nS-lock for this record and kills idle local transaction.\n\nAt this point we have two non-conflicting high priority\ntransactions holding S-lock on different records in node_1.\nFor example like this: rec s-lock-node2-rec s-lock-node3-rec rec.\n\nBecause these high priority BF-transactions do not wait\neach other insert from node3 that has later seqno compared\nto insert from node2 can continue. It will try to acquire\ninsert intention for record it tries to insert (to avoid\nduplicate key to be inserted by local transaction). Hower,\nit will note that there is conflicting S-lock in same gap\nbetween records. This will lead deadlock error as we have\ndefined that BF-transactions may not wait for record lock\nbut we can't kill conflicting BF-transaction because\nit has lower seqno and it should commit first.\n\nBF-transactions are executed concurrently because their\nvalues to primary key are different i.e. they do not\nconflict.\n\nGalera certification will make sure that inserts from\nother nodes i.e these high priority BF-transactions\ncan't insert duplicate keys. Local transactions naturally\ncan but they will be killed when BF-transaction\nacquires required record locks.\n\nTherefore, we can allow situation where there is conflicting\nS-lock and insert intention lock regardless of their seqno\norder and let both continue with no wait. This will lead\nto situation where we need to allow BF-transaction\nto wait when lock_rec_has_to_wait_in_queue is called\nbecause this function is also called from\nlock_rec_queue_validate and because lock is waiting\nthere would be assertion in ut_a(lock->is_gap()\n|| lock_rec_has_to_wait_in_queue(cell, lock));\n\nlock_wait_wsrep_kill\n Add debug sync points for BF-transactions killing\n local transaction.\n\nwsrep_assert_no_bf_bf_wait\n Print also requested lock information\n\nlock_rec_has_to_wait\n Add function to handle wsrep transaction lock wait\n cases.\n\nlock_rec_has_to_wait_wsrep\n New function to handle wsrep transaction lock wait\n exceptions.\n\nlock_rec_has_to_wait_in_queue\n Remove wsrep exception, in this function all\n conflicting locks need to wait in queue.\n Conflicts between BF and local transactions\n are handled in lock_wait.","shortMessageHtmlLink":"MDEV-31658 : Deadlock found when trying to get lock during applying"}},{"before":"c776101c7cbd351691d9286709774caf45b3bf50","after":"254a24e977a328b38fc83b2e9323e976b544f3d6","ref":"refs/heads/10.5-MDEV-12008","pushedAt":"2024-06-07T09:26:39.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"janlindstrom","name":"Jan Lindström","path":"/janlindstrom","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6338705?s=80&v=4"},"commit":{"message":"MDEV-12008 : Change error code for Galera unkillable threads\n\nChanged error code for Galera unkillable threads to\nbe ER_KILL_DENIED_HIGH_PRIORITY giving message\n\nThis is an high priority thread/query and cannot be killed\nwithout compromising consistency of the cluster\n\nalso a warning is produced\n Thread %lld is [wsrep applier|high priority] and cannot be killed","shortMessageHtmlLink":"MDEV-12008 : Change error code for Galera unkillable threads"}},{"before":"b12c14e3b42c44ff3a48e82679c2fab8148b372f","after":"699d38d9512218531b9fe7569600ec0619cc6f71","ref":"refs/heads/10.6","pushedAt":"2024-06-07T00:23:08.000Z","pushType":"push","commitsCount":3,"pusher":{"login":"codership-jenkins","name":null,"path":"/codership-jenkins","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/8788800?s=80&v=4"},"commit":{"message":"MDEV-34296 extern thread_local is a CPU waste\n\nIn commit 99bd22605938c42d876194f2ec75b32e658f00f5 (MDEV-31558)\nwe wrongly thought that there would be minimal overhead for accessing\na thread-local variable mariadb_stats.\n\nIt turns out that in C++11, each access to an extern thread_local\nvariable requires conditionally invoking an initialization function.\nIn fact, the initializer expression of mariadb_stats is dynamic, and\nthose calls were actually unavoidable.\n\nIn C++20, one could declare constinit thread_local variables, but\nthe address of a thread_local variable (&mariadb_dummy_stats) is not\na compile-time constant. We did not want to declare mariadb_dummy_stats\nwithout thread_local, because then the dummy accesses could lead to\ncache line contention between threads.\n\nmariadb_stats: Declare as __thread or __declspec(thread) so that\nthere will be no dynamic initialization, but zero-initialization.\n\nmariadb_dummy_stats: Remove. It is a lesser evil to let\nthe environment perform zero-initialization and check if\n!mariadb_stats.\n\nReviewed by: Sergei Petrunia","shortMessageHtmlLink":"MDEV-34296 extern thread_local is a CPU waste"}},{"before":"ce9efb4e0223c978dcf4511ed33f5118e3b3c3ce","after":"a02773f7c000273dd823df6bb386c4d735c3dcc7","ref":"refs/heads/10.5","pushedAt":"2024-06-07T00:23:08.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"codership-jenkins","name":null,"path":"/codership-jenkins","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/8788800?s=80&v=4"},"commit":{"message":"MDEV-34057 Inconsistent FTS state in concurrent scenarios\n\nProblem:\n=======\n- This commit is a merge of mysql commit 129ee47ef994652081a11ee9040c0488e5275b14.\nInnoDB FTS can be in inconsistent state when sync operation\nterminates the server before committing the operation. This\ncould lead to incorrect synced doc id and incorrect query results.\n\nSolution:\n========\n- During sync commit operation, InnoDB should pass\nthe sync transaction to update the max doc id\nin the config table.\n\nfts_read_synced_doc_id() : This function is used\nto read only synced doc id from the config table.","shortMessageHtmlLink":"MDEV-34057 Inconsistent FTS state in concurrent scenarios"}},{"before":null,"after":"d3dd7fc747e6284413fc97900daf6f842a711c8b","ref":"refs/heads/joiner-voting-mtr-10.5","pushedAt":"2024-06-06T21:56:28.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"ayurchen","name":"Alexey Yurchenko","path":"/ayurchen","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1644111?s=80&v=4"},"commit":{"message":"3 MTR tests to test fixes for MENT-2081.\nRequires Galera commit 91f0090a05e96c3cc353b80d961ede45cefb9279","shortMessageHtmlLink":"3 MTR tests to test fixes for MENT-2081."}},{"before":null,"after":"a2cbe2e2599eef4197d43015ac81d7a4b1dca332","ref":"refs/heads/10.5-MDEV-34269","pushedAt":"2024-06-06T07:59:46.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"janlindstrom","name":"Jan Lindström","path":"/janlindstrom","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6338705?s=80&v=4"},"commit":{"message":"MDEV-34269 : 10.11.8 cluster becomes inconsistent when using composite primary key and partitioning\n\nThis is regression from commit 3228c08fa8. Problem is that\nwhen table storage engine is determined there should be\ncheck is table partitioned and if it is then determine\npartition implementing storage engine.\n\nReported bug is reproducible only with --log-bin so make\nsure tests changed by 3228c08fa8 and new test are run\nwith --log-bin and binlog disabled.","shortMessageHtmlLink":"MDEV-34269 : 10.11.8 cluster becomes inconsistent when using composit…"}},{"before":"58a0e1e3dd96628cb119a36361bdddb049873a73","after":"b12c14e3b42c44ff3a48e82679c2fab8148b372f","ref":"refs/heads/10.6","pushedAt":"2024-06-06T00:23:08.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"codership-jenkins","name":null,"path":"/codership-jenkins","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/8788800?s=80&v=4"},"commit":{"message":"MDEV-34265 Possible hang during IO burst with innodb_flush_sync enabled\n\nWhen checkpoint age goes beyond the sync flush threshold and\nbuf_flush_sync_lsn is set, page cleaner enters into \"furious flush\"\nstage to aggressively flush dirty pages from flush list and pull\ncheckpoint LSN above safe margin. In this stage, page cleaner skips\ndoing LRU flush and eviction.\n\nIn 10.6, all other threads entirely rely on page cleaner to generate\nfree pages. If free pages get over while page cleaner is busy in\n\"furious flush\" stage, a session thread could wait for free page in the\nmiddle of a min-transaction(mtr) while holding latches on other pages.\n\nIt, in turn, can prevent page cleaner to flush such pages preventing\ncheckpoint LSN to move forward creating a deadlock situation. Even\notherwise, it could create a stall and hang like situation for large BP\nwith plenty of dirty pages to flush before the stage could finish.\n\nFix: During furious flush, check and evict LRU pages after each flush\niteration.","shortMessageHtmlLink":"MDEV-34265 Possible hang during IO burst with innodb_flush_sync enabled"}},{"before":"e9f4b87e530bc3806062c2b91a25052edd2c4325","after":"ce9efb4e0223c978dcf4511ed33f5118e3b3c3ce","ref":"refs/heads/10.5","pushedAt":"2024-06-06T00:23:08.000Z","pushType":"push","commitsCount":11,"pusher":{"login":"codership-jenkins","name":null,"path":"/codership-jenkins","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/8788800?s=80&v=4"},"commit":{"message":"MDEV-34296 tpool - declare thread_local_waiter \"static thread_local\"","shortMessageHtmlLink":"MDEV-34296 tpool - declare thread_local_waiter \"static thread_local\""}},{"before":"d61947550a38de96de44b4a526e6da90b910ff2b","after":"1bf0950b191aaaa181068551fa241c9d09e6c7c3","ref":"refs/heads/10.11","pushedAt":"2024-06-05T00:23:06.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"codership-jenkins","name":null,"path":"/codership-jenkins","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/8788800?s=80&v=4"},"commit":{"message":"MDEV-34146: Remove duplicate #DEBHELPER# from MariaDB server postrm\n\nMoving to use Debian systemd install and uninstall scripts\ncaused duplicated DEBHELP to server postrm script. Commit\nremoves unneeded and makes postrm work better and pass lintian\ntests","shortMessageHtmlLink":"MDEV-34146: Remove duplicate #DEBHELPER# from MariaDB server postrm"}},{"before":"25476ba1ae18728bec2956f6ff274f38a925d56d","after":"e9f4b87e530bc3806062c2b91a25052edd2c4325","ref":"refs/heads/10.5","pushedAt":"2024-06-05T00:23:06.000Z","pushType":"push","commitsCount":7,"pusher":{"login":"codership-jenkins","name":null,"path":"/codership-jenkins","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/8788800?s=80&v=4"},"commit":{"message":"MDEV-33919: Remove less standard format directive an-trap\n\nFew man pages have less standard format directive:\n.it 1 an-trap which specifying a formatting instruction\nrelated to indentation (adds tab in man page in this)\n\nThere is no traces what an-trap should do and removing\nit does not affect rendering of man page","shortMessageHtmlLink":"MDEV-33919: Remove less standard format directive an-trap"}},{"before":"f2302a62e33a1c83ccc0968149f9543bc315e82b","after":"58a0e1e3dd96628cb119a36361bdddb049873a73","ref":"refs/heads/10.6","pushedAt":"2024-06-04T00:23:09.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"codership-jenkins","name":null,"path":"/codership-jenkins","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/8788800?s=80&v=4"},"commit":{"message":"MDEV-34223 Innodb - add status variable for number of bulk inserts\n\n- Added a counter innodb_num_bulk_insert_operation in\nINFORMATION_SCHEMA.GLOBAL_STATUS. This counter is incremented\nwhenever a InnoDB undergoes bulk insert operation.\n\n- Change the innodb_instant_alter_column to atomic variable.","shortMessageHtmlLink":"MDEV-34223 Innodb - add status variable for number of bulk inserts"}},{"before":"d456e1382d7b9305ec4f4c3cd298827bf15d3cae","after":"4e785bd2048237fda256b5f7d13323a3b305c0f8","ref":"refs/heads/10.6-MDEV-28452","pushedAt":"2024-06-03T07:40:41.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"plampio","name":"Pekka Lampio","path":"/plampio","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/51317842?s=80&v=4"},"commit":{"message":"Fixes for issues raised by the reviewers.","shortMessageHtmlLink":"Fixes for issues raised by the reviewers."}},{"before":"94999c16cc5cf126227c7084dcd9e06ed4d5689e","after":"2d3e2c58b6d8e74cbec36a806e5ca9f3cbca3fb5","ref":"refs/heads/11.1","pushedAt":"2024-06-01T00:23:07.000Z","pushType":"push","commitsCount":47,"pusher":{"login":"codership-jenkins","name":null,"path":"/codership-jenkins","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/8788800?s=80&v=4"},"commit":{"message":"Merge branch '10.11' into 11.1","shortMessageHtmlLink":"Merge branch '10.11' into 11.1"}},{"before":"22774ddb53eb605b40ec680e416b2e6fc482935d","after":"d61947550a38de96de44b4a526e6da90b910ff2b","ref":"refs/heads/10.11","pushedAt":"2024-06-01T00:23:07.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"codership-jenkins","name":null,"path":"/codership-jenkins","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/8788800?s=80&v=4"},"commit":{"message":"fix a typo","shortMessageHtmlLink":"fix a typo"}},{"before":"457948707df1e24578a7d7d070e54b74345e46e5","after":"1849dfef64d5f191c1fda3457ad97c6775f9a9f3","ref":"refs/heads/11.4","pushedAt":"2024-05-31T00:23:06.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"codership-jenkins","name":null,"path":"/codership-jenkins","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/8788800?s=80&v=4"},"commit":{"message":"MDEV-34256 InnoDB throws out of bound write due to temporary\n\t\ttablespace truncation\n\n- InnoDB fails with out of bound write error after temporary\ntablespace truncation. This issue caused by\ncommit c507678b207a1a8ce6d99ea28fb947bed1d95795 (MDEV-28699).\nInnoDB fail to clear freed ranges if shrinking size\nis the last offset of the freed range.","shortMessageHtmlLink":"MDEV-34256 InnoDB throws out of bound write due to temporary"}},{"before":"a960e95febd10b8558e9e626869babd0573bbf69","after":"22774ddb53eb605b40ec680e416b2e6fc482935d","ref":"refs/heads/10.11","pushedAt":"2024-05-31T00:23:06.000Z","pushType":"push","commitsCount":44,"pusher":{"login":"codership-jenkins","name":null,"path":"/codership-jenkins","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/8788800?s=80&v=4"},"commit":{"message":"Merge branch '10.6' into 10.11","shortMessageHtmlLink":"Merge branch '10.6' into 10.11"}},{"before":"b0b463a894bab4e6cd7786924b1a0afa62d0cd42","after":"25476ba1ae18728bec2956f6ff274f38a925d56d","ref":"refs/heads/10.5","pushedAt":"2024-05-31T00:23:06.000Z","pushType":"push","commitsCount":5,"pusher":{"login":"codership-jenkins","name":null,"path":"/codership-jenkins","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/8788800?s=80&v=4"},"commit":{"message":"MDEV-29027 ASAN errors in spider_db_free_result after partition DDL\n\nSpider calls ha_spider::close() at least twice on ALTER TABLE ... ADD\nPARTITION. The first call frees wide_handler and the second call\naccesses wide_handler->trx->thd (heap-use-after-free).\n\nIn general, there seems to be no problem with using THD obtained by\nthe macro current_thd() except in background threads. Thus, we simply\nreplace wide_handler->trx->thd with current_thd().\n\nOriginal author: Nayuta Yanagasawa","shortMessageHtmlLink":"MDEV-29027 ASAN errors in spider_db_free_result after partition DDL"}},{"before":"99f6684ba0f85ae12582770c8cacfa6aa950f166","after":"c96b23f99409cad9c0dac5040561136211486995","ref":"refs/heads/11.5","pushedAt":"2024-05-31T00:23:06.000Z","pushType":"push","commitsCount":9,"pusher":{"login":"codership-jenkins","name":null,"path":"/codership-jenkins","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/8788800?s=80&v=4"},"commit":{"message":"Merge branch '11.4' into 11.5","shortMessageHtmlLink":"Merge branch '11.4' into 11.5"}},{"before":"36ab6cc80cc8d8bf332852ecdf5fac3adf8e8888","after":"f2302a62e33a1c83ccc0968149f9543bc315e82b","ref":"refs/heads/10.6","pushedAt":"2024-05-31T00:23:06.000Z","pushType":"push","commitsCount":36,"pusher":{"login":"codership-jenkins","name":null,"path":"/codership-jenkins","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/8788800?s=80&v=4"},"commit":{"message":"Merge branch '10.5' into 10.6","shortMessageHtmlLink":"Merge branch '10.5' into 10.6"}},{"before":"f5e7034da2b2daa61482b75d41dedaec52bd04d4","after":"9cf732eaafd9dd15e1f3af1c2a1b816d44117753","ref":"refs/heads/11.5-blackbox-and-buffered-error-logging-for-Galera","pushedAt":"2024-05-30T08:28:55.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"janlindstrom","name":"Jan Lindström","path":"/janlindstrom","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6338705?s=80&v=4"},"commit":{"message":"Fix wsrep_buffered_error_log_filename output so that it is not full path","shortMessageHtmlLink":"Fix wsrep_buffered_error_log_filename output so that it is not full path"}},{"before":"aa04bba47b702f9653261109f41555264f834ef8","after":"457948707df1e24578a7d7d070e54b74345e46e5","ref":"refs/heads/11.4","pushedAt":"2024-05-30T00:23:08.000Z","pushType":"push","commitsCount":4,"pusher":{"login":"codership-jenkins","name":null,"path":"/codership-jenkins","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/8788800?s=80&v=4"},"commit":{"message":"Merge branch 'bb-11.4-bumpversion' of github.com:MariaDB/server into bb-11.4-bumpversion","shortMessageHtmlLink":"Merge branch 'bb-11.4-bumpversion' of github.com:MariaDB/server into …"}},{"before":"82ba486e5484a9dfb5608956453574542a89930d","after":"a960e95febd10b8558e9e626869babd0573bbf69","ref":"refs/heads/10.11","pushedAt":"2024-05-30T00:23:08.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"codership-jenkins","name":null,"path":"/codership-jenkins","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/8788800?s=80&v=4"},"commit":{"message":"don't require resolveip if it won't be used","shortMessageHtmlLink":"don't require resolveip if it won't be used"}},{"before":"83a04be84aa5ed95f24371d2eb125216e4a89eab","after":"b0b463a894bab4e6cd7786924b1a0afa62d0cd42","ref":"refs/heads/10.5","pushedAt":"2024-05-30T00:23:08.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"codership-jenkins","name":null,"path":"/codership-jenkins","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/8788800?s=80&v=4"},"commit":{"message":"MDEV-33616 Fix memleak in pfs_noop\n\nInvoke cleanup routine at the end of pfs_noop.","shortMessageHtmlLink":"MDEV-33616 Fix memleak in pfs_noop"}},{"before":null,"after":"f5e7034da2b2daa61482b75d41dedaec52bd04d4","ref":"refs/heads/11.5-blackbox-and-buffered-error-logging-for-Galera","pushedAt":"2024-05-29T10:42:44.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"janlindstrom","name":"Jan Lindström","path":"/janlindstrom","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6338705?s=80&v=4"},"commit":{"message":"MDEV-34229 : Port blackbox feature from ES\n\nThis is the first version of the Black Box (BB) feature that extends\nthe logging mechanism of MariaDB database servers. It saves\nall log messages regardless of the log level setting for a short\ntime. These log messages are stored in the BB until it becomes\nfull. After that new log messages overwrite the oldest ones in BB.\n\nIncludes a tool bbtool to inspect messages stored in the BB.\nTool can be used also to inspect messages after server crash\nfor troubleshooting.\n\nNew parameters\nwsrep_blackbox_name string default null readonly\nwsrep_blackbox_size ulong default 0 dynamic\n\nFeature originally developed by Pekka Lampio (pekka.lampio@galeracluster.com)\nModified for MariaDB by Jan Lindström (jan.lindstrom@galeracluster.com)","shortMessageHtmlLink":"MDEV-34229 : Port blackbox feature from ES"}},{"before":"72aca84cfaa34eb77250e5a30c0ceddbd054bb68","after":"f5e7034da2b2daa61482b75d41dedaec52bd04d4","ref":"refs/heads/11.5-buffered-error-logging","pushedAt":"2024-05-29T10:38:42.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"janlindstrom","name":"Jan Lindström","path":"/janlindstrom","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6338705?s=80&v=4"},"commit":{"message":"MDEV-34229 : Port blackbox feature from ES\n\nThis is the first version of the Black Box (BB) feature that extends\nthe logging mechanism of MariaDB database servers. It saves\nall log messages regardless of the log level setting for a short\ntime. These log messages are stored in the BB until it becomes\nfull. After that new log messages overwrite the oldest ones in BB.\n\nIncludes a tool bbtool to inspect messages stored in the BB.\nTool can be used also to inspect messages after server crash\nfor troubleshooting.\n\nNew parameters\nwsrep_blackbox_name string default null readonly\nwsrep_blackbox_size ulong default 0 dynamic\n\nFeature originally developed by Pekka Lampio (pekka.lampio@galeracluster.com)\nModified for MariaDB by Jan Lindström (jan.lindstrom@galeracluster.com)","shortMessageHtmlLink":"MDEV-34229 : Port blackbox feature from ES"}}],"hasNextPage":true,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"djE6ks8AAAAEYsNWkgA","startCursor":null,"endCursor":null}},"title":"Activity · codership/mariadb-server"}