{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":8555900,"defaultBranch":"main","name":"rails","ownerLogin":"maximerety","currentUserCanPush":false,"isFork":true,"isEmpty":false,"createdAt":"2013-03-04T13:17:58.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/58582?v=4","public":true,"private":false,"isOrgOwned":false},"refInfo":{"name":"","listCacheKey":"v0:1709498697.0","currentOid":""},"activityList":{"items":[{"before":"75120346d28bb8259307acd84d50e42d361fe968","after":"ee9414fcf05d80d2254a6ae259d24269df3d2f1c","ref":"refs/heads/optim-in-batches-using-offset","pushedAt":"2024-05-21T14:38:11.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"maximerety","name":"Maxime Réty","path":"/maximerety","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/58582?s=80&v=4"},"commit":{"message":"[Fix #51242] Rework in_batches(use_ranges: true) to be more efficient\n\nWhen `use_ranges: true` option is used, we do not need to return the\nwhole list of primary keys for each range. This wastes network resources\nand takes longer than necessary, as only the last primary key from the\nrange would be needed.\n\nWe can instead use OFFSET to peek at the last primary key of the next\nbatch, instead of returning the whole list of pks from the range.\n\nThere is a trade-off, however, as we need an additional query to confirm\nthe size of the very last batch, and the value of the last last primary\nkey. Unless we only have a handful of small batches, this strategy is a\nwinner overall, as it reduces the time and network resources spent\ngenerating batches.\n\nFor example, `[10, 11, 12, ..., 20]` was previously loaded to generate a\nrelation in the form of `WHERE id > 10 AND id <= 20` for a batch. Since\n`10` would already be known from the previous iteration, we only need to\nretrieve the last key in the range (`20`) using a `LIMIT 1 OFFSET ω`\nconstruct (ω = batch size - 1), thus avoiding the unnecessary loading\nand discarding of all other primary keys in the range.","shortMessageHtmlLink":"[Fix rails#51242] Rework in_batches(use_ranges: true) to be more effi…"}},{"before":"0a9346c3b0c98338fbc354e1540364397e46c4f9","after":"75120346d28bb8259307acd84d50e42d361fe968","ref":"refs/heads/optim-in-batches-using-offset","pushedAt":"2024-05-17T12:59:06.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"maximerety","name":"Maxime Réty","path":"/maximerety","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/58582?s=80&v=4"},"commit":{"message":"[Fix #51242] Rework in_batches(use_ranges: true) to be more efficient\n\nWhen `use_ranges: true` option is used, we do not need to return the\nwhole list of primary keys for each range. This wastes network resources\nand takes longer than necessary, as only the last primary key from the\nrange would be needed.\n\nWe can instead use OFFSET to peek at the last primary key of the next\nbatch, instead of returning the whole list of pks from the range.\n\nThere is a trade-off, however, as we need an additional query to confirm\nthe size of the very last batch, and the value of the last last primary\nkey. Unless we only have a handful of small batches, this strategy is a\nwinner overall, as it reduces the time and network resources spent\ngenerating batches.","shortMessageHtmlLink":"[Fix rails#51242] Rework in_batches(use_ranges: true) to be more effi…"}},{"before":"e34a0eec38767920e04f56a7aa7978b7c5fb685a","after":"161d98dec2706521cb5d1f58acd87c3c1f391c8a","ref":"refs/heads/main","pushedAt":"2024-05-17T12:24:58.000Z","pushType":"push","commitsCount":692,"pusher":{"login":"maximerety","name":"Maxime Réty","path":"/maximerety","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/58582?s=80&v=4"},"commit":{"message":"Merge branch 'rm-trix'","shortMessageHtmlLink":"Merge branch 'rm-trix'"}},{"before":"58a0796d8500c789c1d33dd2b8e4f9ac9dce2825","after":"0a9346c3b0c98338fbc354e1540364397e46c4f9","ref":"refs/heads/optim-in-batches-using-offset","pushedAt":"2024-04-08T13:57:22.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"maximerety","name":"Maxime Réty","path":"/maximerety","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/58582?s=80&v=4"},"commit":{"message":"[Fix #51242] Rework in_batches(use_ranges: true) to be more efficient\n\nWhen `use_ranges: true` option is used, we do not need to return the\nwhole list of primary keys for each range. This wastes network resources\nand takes longer than necessary, as only the last primary key from the\nrange would be needed.\n\nWe can instead use OFFSET to peek at the last primary key of the next\nbatch, instead of returning the whole list of pks from the range.\n\nThere is a trade-off, however, as we need an additional query to confirm\nthe size of the very last batch, and the value of the last last primary\nkey. Unless we only have a handful of small batches, this strategy is a\nwinner overall, as it reduces the time and network resources spent\ngenerating batches.","shortMessageHtmlLink":"[Fix rails#51242] Rework in_batches(use_ranges: true) to be more effi…"}},{"before":"d6a5a586b0a029f9a364a04e32455e2e67c61131","after":"58a0796d8500c789c1d33dd2b8e4f9ac9dce2825","ref":"refs/heads/optim-in-batches-using-offset","pushedAt":"2024-04-02T09:12:31.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"maximerety","name":"Maxime Réty","path":"/maximerety","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/58582?s=80&v=4"},"commit":{"message":"[Fix #51242] Rework in_batches(use_ranges: true) to be more efficient\n\nWhen `use_ranges: true` option is used, we do not need to return the\nwhole list of primary keys for each range. This wastes network resources\nand takes longer than necessary, as only the last primary key from the\nrange would be needed.\n\nWe can instead use OFFSET to peek at the last primary key of the next\nbatch, instead of returning the whole list of pks from the range.\n\nThere is a trade-off, however, as we need an additional query to confirm\nthe size of the very last batch, and the value of the last last primary\nkey. Unless we only have a handful of small batches, this strategy is a\nwinner overall, as it reduces the time and network resources spent\ngenerating batches.","shortMessageHtmlLink":"[Fix rails#51242] Rework in_batches(use_ranges: true) to be more effi…"}},{"before":"485f96feaae05b2ce76099fdb8b59422adfaa507","after":"d6a5a586b0a029f9a364a04e32455e2e67c61131","ref":"refs/heads/optim-in-batches-using-offset","pushedAt":"2024-03-26T21:43:19.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"maximerety","name":"Maxime Réty","path":"/maximerety","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/58582?s=80&v=4"},"commit":{"message":"[Fix #51242] Rework in_batches(use_ranges: true) to be more efficient\n\nWhen `use_ranges: true` option is used, we do not need to return the\nwhole list of primary keys for each range. This wastes network resources\nand takes longer than necessary, as only the last primary key from the\nrange would be needed.\n\nWe can instead use OFFSET to peek at the last primary key of the next\nbatch, instead of returning the whole list of pks from the range.\n\nThere is a trade-off, however, as we need an additional query to confirm\nthe size of the very last batch, and the value of the last last primary\nkey. Unless we only have a handful of small batches, this strategy is a\nwinner overall, as it reduces the time and network resources spent\ngenerating batches.","shortMessageHtmlLink":"[Fix rails#51242] Rework in_batches(use_ranges: true) to be more effi…"}},{"before":"4f75a1ce1046af559dc35a54a81e8180e1a52685","after":"485f96feaae05b2ce76099fdb8b59422adfaa507","ref":"refs/heads/optim-in-batches-using-offset","pushedAt":"2024-03-06T00:06:19.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"maximerety","name":"Maxime Réty","path":"/maximerety","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/58582?s=80&v=4"},"commit":{"message":"[Fix #51242] Rework in_batches(use_ranges: true) to be more efficient\n\nWhen `use_ranges: true` option is used, we do not need to return the\nwhole list of primary keys for each range. This wastes network resources\nand takes longer than necessary, as only the last primary key from the\nrange would be needed.\n\nWe can instead use OFFSET to peek at the last primary key of the next\nbatch, instead of returning the whole list of pks from the range.\n\nThere is a trade-off, however, as we need an additional query to confirm\nthe size of the very last batch, and the value of the last last primary\nkey. Unless we only have a handful of small batches, this strategy is a\nwinner overall, as it reduces the time and network resources spent\ngenerating batches.","shortMessageHtmlLink":"[Fix rails#51242] Rework in_batches(use_ranges: true) to be more effi…"}},{"before":"cb7ed678ce1e00385444554995536c73f7a3c882","after":"4f75a1ce1046af559dc35a54a81e8180e1a52685","ref":"refs/heads/optim-in-batches-using-offset","pushedAt":"2024-03-05T23:26:23.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"maximerety","name":"Maxime Réty","path":"/maximerety","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/58582?s=80&v=4"},"commit":{"message":"[Fix #51242] Rework in_batches(use_ranges: true) to be more efficient\n\nWhen `use_ranges: true` option is used, there is no need to return the\nwhole list of ids for every range. This wastes network resources and\ntakes longer than necessary, as only the last id is needed.\n\nWe can instead use OFFSET to peek at the last id of the next batch, and\nreturn this single id in place of the whole list of ids from the range.\n\nThere is a trade-off, however, as we need an additional query to confirm\nthe size and last id of the very last batch. Unless we only have a\nhandful of small batches, this strategy is a winner overall, as it\nreduces the time and network resources spent generating batches.","shortMessageHtmlLink":"[Fix rails#51242] Rework in_batches(use_ranges: true) to be more effi…"}},{"before":"1aacf38f908c76e37978ad31d5c313e61fa170e8","after":"cb7ed678ce1e00385444554995536c73f7a3c882","ref":"refs/heads/optim-in-batches-using-offset","pushedAt":"2024-03-03T23:00:22.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"maximerety","name":"Maxime Réty","path":"/maximerety","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/58582?s=80&v=4"},"commit":{"message":"[Fix #51242] Rework in_batches(use_ranges: true) to be more efficient\n\nWhen `use_ranges: true` option is used, there is no need to return the\nwhole list of ids for every range. This wastes network resources and\ntakes longer than necessary, as only the last id is needed.\n\nWe can instead use OFFSET to peek at the last id of the next batch, and\nreturn this single id in place of the whole list of ids from the range.\n\nThere is a trade-off, however, as we need an additional query to confirm\nthe size and last id of the very last batch. Unless we only have a\nhandful of small batches, this strategy is a winner overall, as it\nreduces the time and network resources spent generating batches.","shortMessageHtmlLink":"[Fix rails#51242] Rework in_batches(use_ranges: true) to be more effi…"}},{"before":"56ba3555171c1d80d4b9347bc7f37f0d1faaabd7","after":"1aacf38f908c76e37978ad31d5c313e61fa170e8","ref":"refs/heads/optim-in-batches-using-offset","pushedAt":"2024-03-03T20:49:20.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"maximerety","name":"Maxime Réty","path":"/maximerety","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/58582?s=80&v=4"},"commit":{"message":"Rework in_batches to be more network efficient\n\nWhen `use_ranges: true` option is used, there is no need to return the\nwhole list of ids for every range. This wastes network resources and\ntakes longer than necessary, as only the last id is needed.\n\nWe can instead use OFFSET to peek at the last id of the next batch, and\nreturn this single id in place of the whole list of ids from the range.\n\nThere is a trade-off, however, as we need an additional query to confirm\nthe size and last id of the very last batch. Unless we only have a\nhandful of small batches, this strategy is a winner overall, as it\nreduces the time and network resources spent generating batches.","shortMessageHtmlLink":"Rework in_batches to be more network efficient"}},{"before":null,"after":"56ba3555171c1d80d4b9347bc7f37f0d1faaabd7","ref":"refs/heads/optim-in-batches-using-offset","pushedAt":"2024-03-03T20:44:57.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"maximerety","name":"Maxime Réty","path":"/maximerety","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/58582?s=80&v=4"},"commit":{"message":"Rework in_batches to be more network efficient\n\nWhen `use_ranges: true` option is used, there is no need to return the\nwhole list of ids for every range. This would waste to many network and\ntime resources, as only the last id is needed.\n\nInstead we can use OFFSET to peek at the last id of the next batch, and\nreturn only this one.\n\nThere's a trade-off though, since we need one additional query to\nconfirm the size and last id for the very last batch. Unless you have\nonly a handful of small batches, this is overall a winning strategy with\nless time and network resources spent to generate batches.\n\nThere is a trade-off, however, as we need an additional query to confirm\nthe size and last id of the very last batch. Unless you only have a\nhandful of small batches, this strategy is a winner overall, as it\nreduces the time and network resources spent generating batches.","shortMessageHtmlLink":"Rework in_batches to be more network efficient"}},{"before":"9b343c28799abd5555207de3a43231c50cbf8109","after":"e34a0eec38767920e04f56a7aa7978b7c5fb685a","ref":"refs/heads/main","pushedAt":"2024-02-25T20:38:08.000Z","pushType":"push","commitsCount":182,"pusher":{"login":"maximerety","name":"Maxime Réty","path":"/maximerety","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/58582?s=80&v=4"},"commit":{"message":"Merge pull request #51186 from Earlopain/encourage-html-safe-methods-for-safe-join\n\nDocs: Encourage html safe methods for safe join [ci skip]","shortMessageHtmlLink":"Merge pull request rails#51186 from Earlopain/encourage-html-safe-met…"}},{"before":"8fda5f8b299aab7578727235f60ff29c6e37e532","after":"0ae4ca3a15ab975fd3f24d327f0654831bb5684f","ref":"refs/heads/7-1-stable","pushedAt":"2024-02-14T09:21:56.000Z","pushType":"push","commitsCount":8,"pusher":{"login":"maximerety","name":"Maxime Réty","path":"/maximerety","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/58582?s=80&v=4"},"commit":{"message":"Merge pull request #51061 from maximerety/backport-active-record-encryption-eager-load-7-1\n\nBackport #50606 to 7-1-stable","shortMessageHtmlLink":"Merge pull request rails#51061 from maximerety/backport-active-record…"}},{"before":"0656787be644d7d5550e82450153403853c73014","after":"9b343c28799abd5555207de3a43231c50cbf8109","ref":"refs/heads/main","pushedAt":"2024-02-14T09:21:40.000Z","pushType":"push","commitsCount":285,"pusher":{"login":"maximerety","name":"Maxime Réty","path":"/maximerety","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/58582?s=80&v=4"},"commit":{"message":"Merge pull request #51076 from yahonda/enum_action_mailbox\n\nAddress `Defining enums with keyword arguments` warning in Action Mai…","shortMessageHtmlLink":"Merge pull request rails#51076 from yahonda/enum_action_mailbox"}},{"before":"cee5d5bf210ed5cab63266552bf75e6d1e34cce3","after":null,"ref":"refs/heads/backport-active-record-encryption-eager-load-7-1","pushedAt":"2024-02-14T08:44:50.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"maximerety","name":"Maxime Réty","path":"/maximerety","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/58582?s=80&v=4"}},{"before":null,"after":"cee5d5bf210ed5cab63266552bf75e6d1e34cce3","ref":"refs/heads/backport-active-record-encryption-eager-load-7-1","pushedAt":"2024-02-13T12:26:49.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"maximerety","name":"Maxime Réty","path":"/maximerety","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/58582?s=80&v=4"},"commit":{"message":"Merge pull request #50606 from maximerety/active-record-encryption-eager-load\n\n[Fix #50604] Restore compatibility of Active Record Encryption configs with eager loading mode","shortMessageHtmlLink":"Merge pull request rails#50606 from maximerety/active-record-encrypti…"}},{"before":"4626b71413612e2c58d88d0d89da649c969fdb50","after":"8fda5f8b299aab7578727235f60ff29c6e37e532","ref":"refs/heads/7-1-stable","pushedAt":"2024-02-13T08:35:56.000Z","pushType":"push","commitsCount":133,"pusher":{"login":"maximerety","name":"Maxime Réty","path":"/maximerety","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/58582?s=80&v=4"},"commit":{"message":"Merge pull request #51017 from p8/activesupport/document-time-zone-create (#51058)\n\nImprove documentation of ActiveSupport::TimeZone.create [ci-skip]\r\n\r\nCo-authored-by: Rafael Mendonça França ","shortMessageHtmlLink":"Merge pull request rails#51017 from p8/activesupport/document-time-zo…"}},{"before":"d997c554b3dfc87a2896cf7f0d7f87c39a32ab1c","after":null,"ref":"refs/heads/active-record-encryption-eager-load","pushedAt":"2024-02-13T08:35:03.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"maximerety","name":"Maxime Réty","path":"/maximerety","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/58582?s=80&v=4"}},{"before":"94cec125926a99cd9877a002c39560af556c52bc","after":"d997c554b3dfc87a2896cf7f0d7f87c39a32ab1c","ref":"refs/heads/active-record-encryption-eager-load","pushedAt":"2024-02-12T16:57:59.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"maximerety","name":"Maxime Réty","path":"/maximerety","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/58582?s=80&v=4"},"commit":{"message":"[Fix #50604] Restore compatibility of ARE configs with eager loading mode\n\nConfigure ActiveRecord::Encryption (ARE) on ActiveRecord::Base (AR)\nloading, so that ARE configs are ready before AR models start using\n`encrypts` to declare encrypted attributes.\n\nThis means that you can add ARE configurations in initializers, as long\nas you don't trigger the loading of ActiveRecord::Base or your AR models\nin prior initializers.","shortMessageHtmlLink":"[Fix rails#50604] Restore compatibility of ARE configs with eager loa…"}},{"before":"7105a53b72b6f55a1b8da8be914b556487e497f7","after":"94cec125926a99cd9877a002c39560af556c52bc","ref":"refs/heads/active-record-encryption-eager-load","pushedAt":"2024-02-12T13:04:51.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"maximerety","name":"Maxime Réty","path":"/maximerety","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/58582?s=80&v=4"},"commit":{"message":"[Fix #50604] Restore compatibility of ARE configs with eager loading mode\n\nConfigure ActiveRecord::Encryption (ARE) on ActiveRecord::Base (AR)\nloading, so that ARE configs are ready before AR models start using\n`encrypts` to declare encrypted attributes.\n\nThis means that you can add ARE configurations in initializers, as long\nas you don't trigger the loading of ActiveRecord::Base or your AR models\nin prior initializers.","shortMessageHtmlLink":"[Fix rails#50604] Restore compatibility of ARE configs with eager loa…"}},{"before":"3ffb25c1191e30ec58487ee322cebe130d9993ba","after":"7105a53b72b6f55a1b8da8be914b556487e497f7","ref":"refs/heads/active-record-encryption-eager-load","pushedAt":"2024-01-31T12:08:11.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"maximerety","name":"Maxime Réty","path":"/maximerety","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/58582?s=80&v=4"},"commit":{"message":"[Fix #50604] Restore compatibility of ARE configs with eager loading mode\n\nConfigure ActiveRecord::Encryption (ARE) on ActiveRecord::Base (AR)\nloading, so that ARE configs are ready before AR models start using\n`encrypts` to declare encrypted attributes.\n\nThis means that you can add ARE configurations in initializers, as long\nas you don't trigger the loading of ActiveRecord::Base or your AR models\nin prior initializers.","shortMessageHtmlLink":"[Fix rails#50604] Restore compatibility of ARE configs with eager loa…"}},{"before":"099493ae9827b66270ca13f9fd8a1c4fc206a57f","after":"3ffb25c1191e30ec58487ee322cebe130d9993ba","ref":"refs/heads/active-record-encryption-eager-load","pushedAt":"2024-01-31T12:06:50.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"maximerety","name":"Maxime Réty","path":"/maximerety","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/58582?s=80&v=4"},"commit":{"message":"[Fix #50604] Restore compatibility of ARE configs with eager loading mode\n\nConfigure ActiveRecord::Encryption (ARE) on ActiveRecord::Base (AR)\nloading, so that ARE configs are ready before AR models start using\n`encrypts` to declare encrypted attributes.\n\nThis means that you can add ARE configurations in initializers, as long\nas you don't trigger the loading of ActiveRecord::Base or your AR models\nin prior initializers.","shortMessageHtmlLink":"[Fix rails#50604] Restore compatibility of ARE configs with eager loa…"}},{"before":"88374f3fd121607032ddf97ef888af8ff6bac7d4","after":"099493ae9827b66270ca13f9fd8a1c4fc206a57f","ref":"refs/heads/active-record-encryption-eager-load","pushedAt":"2024-01-25T12:07:23.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"maximerety","name":"Maxime Réty","path":"/maximerety","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/58582?s=80&v=4"},"commit":{"message":"[Fix #50604] Restore compatibility of ARE configs with eager loading mode\n\nConfigure ActiveRecord::Encryption (ARE) on ActiveRecord::Base (AR)\nloading, so that ARE configs are ready before AR models start using\n`encrypts` to declare encrypted attributes.\n\nThis means that you can add ARE configurations in initializers, as long\nas you don't trigger the loading of ActiveRecord::Base or your AR models\nin prior initializers.","shortMessageHtmlLink":"[Fix rails#50604] Restore compatibility of ARE configs with eager loa…"}},{"before":"2464c52f371eca79e2180bdc5bd442fec1624c4c","after":"88374f3fd121607032ddf97ef888af8ff6bac7d4","ref":"refs/heads/active-record-encryption-eager-load","pushedAt":"2024-01-22T13:09:31.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"maximerety","name":"Maxime Réty","path":"/maximerety","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/58582?s=80&v=4"},"commit":{"message":"[Fix #50604] Restore compatibility of ARE configs with eager loading mode\n\nConfigure ActiveRecord::Encryption (ARE) on ActiveRecord::Base (AR)\nloading, so that ARE configs are ready before AR models start using\n`encrypts` to declare encrypted attributes.\n\nThis means that you can add ARE configurations in initializers, as long\nas you don't trigger the loading of ActiveRecord::Base or your AR models\nin prior initializers.","shortMessageHtmlLink":"[Fix rails#50604] Restore compatibility of ARE configs with eager loa…"}},{"before":"057f771bd3a65565f7962e460d4366dcdbc3a8a8","after":"2464c52f371eca79e2180bdc5bd442fec1624c4c","ref":"refs/heads/active-record-encryption-eager-load","pushedAt":"2024-01-17T12:51:09.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"maximerety","name":"Maxime Réty","path":"/maximerety","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/58582?s=80&v=4"},"commit":{"message":"[Fix #50604] Restore compatibility of ARE configs with eager loading mode\n\nConfigure ActiveRecord::Encryption (ARE) on ActiveRecord::Base (AR)\nloading, so that ARE configs are ready before AR models start using\n`encrypts` to declare encrypted attributes.\n\nThis means that you can add ARE configurations in initializers, as long\nas you don't trigger the loading of ActiveRecord::Base or your AR models\nin prior initializers.","shortMessageHtmlLink":"[Fix rails#50604] Restore compatibility of ARE configs with eager loa…"}},{"before":"4026afdba780ca631149a97e2469c9783e5f2933","after":"057f771bd3a65565f7962e460d4366dcdbc3a8a8","ref":"refs/heads/active-record-encryption-eager-load","pushedAt":"2024-01-16T15:32:26.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"maximerety","name":"Maxime Réty","path":"/maximerety","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/58582?s=80&v=4"},"commit":{"message":"[Fix #50604] Restore compatibility of ARE configs with eager loading mode\n\nConfigure ActiveRecord::Encryption (ARE) on ActiveRecord::Base (AR)\nloading, so that ARE configs are ready before AR models start using\n`encrypts` to declare encrypted attributes.\n\nThis means that you can add ARE configurations in initializers, as long\nas you don't trigger the loading of ActiveRecord::Base or your AR models\nin prior initializers.","shortMessageHtmlLink":"[Fix rails#50604] Restore compatibility of ARE configs with eager loa…"}},{"before":"a255742b2eb711baa8fd7a8937852851ddc8a679","after":"0656787be644d7d5550e82450153403853c73014","ref":"refs/heads/main","pushedAt":"2024-01-16T15:30:47.000Z","pushType":"push","commitsCount":41,"pusher":{"login":"maximerety","name":"Maxime Réty","path":"/maximerety","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/58582?s=80&v=4"},"commit":{"message":"Merge pull request #50764 from eugeneius/syntax_error_proxy_nil_backtrace_locations\n\nHandle nil backtrace_locations in SyntaxErrorProxy","shortMessageHtmlLink":"Merge pull request rails#50764 from eugeneius/syntax_error_proxy_nil_…"}},{"before":"dc7236db694530383bc4f4a08b1c7459152da50c","after":"4026afdba780ca631149a97e2469c9783e5f2933","ref":"refs/heads/active-record-encryption-eager-load","pushedAt":"2024-01-12T20:47:18.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"maximerety","name":"Maxime Réty","path":"/maximerety","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/58582?s=80&v=4"},"commit":{"message":"[Fix #50604] Restore compatibility of ARE configs with eager loading mode\n\nConfigure ActiveRecord::Encryption (ARE) on ActiveRecord::Base (AR)\nloading, so that ARE configs are ready before AR models start using\n`encrypts` to declare encrypted attributes.\n\nThis means that you can add ARE configurations in initializers, as long\nas you don't trigger the loading of ActiveRecord::Base or your AR models\nin prior initializers.","shortMessageHtmlLink":"[Fix rails#50604] Restore compatibility of ARE configs with eager loa…"}},{"before":"90d0dc596133dc60839de121c5435712d84e21bf","after":"a255742b2eb711baa8fd7a8937852851ddc8a679","ref":"refs/heads/main","pushedAt":"2024-01-12T16:25:29.000Z","pushType":"push","commitsCount":3,"pusher":{"login":"maximerety","name":"Maxime Réty","path":"/maximerety","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/58582?s=80&v=4"},"commit":{"message":"Merge pull request #50261 from joshuay03/activerecord-transactions-set-callback\n\nFix [#50260] Support `:on` option in `#set_callback`","shortMessageHtmlLink":"Merge pull request rails#50261 from joshuay03/activerecord-transactio…"}},{"before":"c5f3a8143004c92e39dbe57ab3f6d3b0a890dc20","after":"90d0dc596133dc60839de121c5435712d84e21bf","ref":"refs/heads/main","pushedAt":"2024-01-12T10:48:19.000Z","pushType":"push","commitsCount":12,"pusher":{"login":"maximerety","name":"Maxime Réty","path":"/maximerety","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/58582?s=80&v=4"},"commit":{"message":"Merge pull request #50719 from ghiculescu/patch-12\n\nFix indenting in SQLite database.yml","shortMessageHtmlLink":"Merge pull request rails#50719 from ghiculescu/patch-12"}}],"hasNextPage":true,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"djE6ks8AAAAET_cQtwA","startCursor":null,"endCursor":null}},"title":"Activity · maximerety/rails"}