{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":160895450,"defaultBranch":"fb-mysql-5.6.35","name":"mysql-5.6","ownerLogin":"hermanlee","currentUserCanPush":false,"isFork":true,"isEmpty":false,"createdAt":"2018-12-08T02:15:05.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/6656176?v=4","public":true,"private":false,"isOrgOwned":false},"refInfo":{"name":"","listCacheKey":"v0:1708536463.0","currentOid":""},"activityList":{"items":[{"before":null,"after":"4cd86f32dad116821d6999a30c8909a86f366e23","ref":"refs/heads/fb-mysql-8.0.23-rangelock","pushedAt":"2024-02-21T17:27:43.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"hermanlee","name":"Herman Lee","path":"/hermanlee","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6656176?s=80&v=4"},"commit":{"message":"[mysql-5.6][PR] Range Locking support, MyRocks part\n\nSummary:\n(Range Locking pull request,filed against fb-mysql-8.0.23)\n\nThis adds a my.cnf parameter, rocksdb_use_range_locking.\n\nWhen it is ON, MyRocks will:\n- initialize RocksDB to use range-locking lock manager\n- for all DML operations (including SELECT .. FOR UPDATE) will lock\n   the scanned range before reading/modifying rows.\n- In range locking mode, there is no snapshot checking (cannot do that\n  for ranges). Instead, MyRocks will read and modify latest committed\n  data, just like InnoDB does (in the code, grep for (start|end)_ignore_\n  snapshot)\n- Queries that do not have a finite range to scan, like\n    UPDATE t1 .... ORDER BY t1.key LIMIT n\n  will use a  \"Locking iterator\" which will read rows, lock the range,\n  and re-read the rows. See class LockingIterator.\n\nPull Request resolved: https://github.com/facebook/mysql-5.6/pull/1185\nGitHub Author: Sergei Petrunia <sergey@mariadb.com>","shortMessageHtmlLink":"[mysql-5.6][PR] Range Locking support, MyRocks part"}},{"before":"70b2ec9680137f4a4580fae47caf3581ad18c7dd","after":null,"ref":"refs/heads/fb-mysql-8.0.32-wip","pushedAt":"2023-11-20T17:10:53.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"hermanlee","name":"Herman Lee","path":"/hermanlee","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6656176?s=80&v=4"}},{"before":"1f7d103569caf59dbbefca045208794e51639440","after":"70b2ec9680137f4a4580fae47caf3581ad18c7dd","ref":"refs/heads/fb-mysql-8.0.32-wip","pushedAt":"2023-10-18T17:25:43.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"hermanlee","name":"Herman Lee","path":"/hermanlee","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6656176?s=80&v=4"},"commit":{"message":"write throttling: Add tracing to get_current_replication_lag\n\nSummary:\nAdd some more tracing to aforementioned function to be able to better\nanswer questions around why certain replica lag values were computed.\n\nDifferential Revision: D50097790","shortMessageHtmlLink":"write throttling: Add tracing to get_current_replication_lag"}},{"before":"db83478bcee3275b7f6be01ced2a7742e64440c2","after":"1f7d103569caf59dbbefca045208794e51639440","ref":"refs/heads/fb-mysql-8.0.32-wip","pushedAt":"2023-10-03T18:26:03.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"hermanlee","name":"Herman Lee","path":"/hermanlee","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6656176?s=80&v=4"},"commit":{"message":"Add drop database to the set of DDL statements tracked by slow log\n\nSummary: Adding tracking for DROP DATABASE so that it shows up in the mysql_slow_log scuba. This should help us narrow down the cases when someone issues this to drop the shard db without dropping the shard, and that triggers tasks like T163949917.\n\nDifferential Revision: D49337859","shortMessageHtmlLink":"Add drop database to the set of DDL statements tracked by slow log"}},{"before":null,"after":"db83478bcee3275b7f6be01ced2a7742e64440c2","ref":"refs/heads/fb-mysql-8.0.32-wip","pushedAt":"2023-09-12T18:16:35.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"hermanlee","name":"Herman Lee","path":"/hermanlee","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6656176?s=80&v=4"},"commit":{"message":"Linux num_vcpus_using_config should use conf instead of onln\n\nSummary:\n\nUse the number of cpus configured instead of the cpus online. The test\nmain.resource_group_bugs_debug runs only when the number of configured\ncpus is greater than 4, but the linux call during the test checks the\nnumber of online cpus, which is dynamic.\n\nChange num_vcpus_using_config() to prefer returning\n_SC_NPROCESSORS_CONF vs. _SC_NPROCESSORS_ONLN.","shortMessageHtmlLink":"Linux num_vcpus_using_config should use conf instead of onln"}}],"hasNextPage":false,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"djE6ks8AAAAEAR3XaAA","startCursor":null,"endCursor":null}},"title":"Activity · hermanlee/mysql-5.6"}