March 2025 - ruby-core - ml.ruby-lang.org

[ruby-core:121261] [Ruby master Feature#18784] `FileUtils.rm_f` and `FileUtils.rm_rf` should not mask exceptions
by byroot (Jean Boussier) 07 Mar '25

07 Mar '25

Issue #18784 has been updated by byroot (Jean Boussier). The `!` for a version that raises is a Rails convention, and AFAIK always rejected for Ruby itself. So a keyword argument is more likely to be accepted. ---------------------------------------- Feature #18784: `FileUtils.rm_f` and `FileUtils.rm_rf` should not mask exceptions https://bugs.ruby-lang.org/issues/18784#change-112216 * Author: deivid (David Rodríguez) * Status: Open ---------------------------------------- In recent times, I've been having issues with these methods because they don't let you know when some issue happened while trying to remove the given folders/files. IMO most users expect all pre-existing folders/files that are passed to these methods to be actually removed by the methods. Instead, when this happens, errors are silently swallowed and normally the result is that you will get some other issue further down the road, making the problem hard to debug. The current workaround I'm using is to double check whether the files still exist after the method, and raise a custom error if they do, but I still can't see the original problem, so issues are similarly hard to debug. This is also a deviation from how `rm -rf` and `rm -f` work, since these tools finish with a failure exit code when they fail to remove the given files. Given that `fileutils` is intended to mimic shell functionality, I think this is just a bug. I think the intention of the `force` flag here is to: * Don't prompt for confirmation. * Ignore given arguments that are not files that already exist. But any issue other than that should not be swallowed, and in general I think the method should succeed if and only if the given list of file names does not exist after the methods are done. I think this is in line with the following note I get when I run `man rm`, but also suggests that this is not the standard behavior of "historical implementations" > COMPATIBILITY > > The rm utility differs from historical implementations in that the -f option only masks attempts to remove non-existent files instead of masking a large variety of errors. I implemented this at https://github.com/ruby/fileutils/pull/58, but treating this as a bug. I can also implement a more conservative for approach for users that might be using `FileUtils.rm_rf` or `FileUtils.rm_f` but don't really care if the files are removed or not. Alternative proposals would be `FileUtils.rm_rf(force: strict)`, or `FileUtils.strict_rm_rf`, but to be honest, if this is considered a breaking change, I would ship it as a new major version, and let users update their code to swallow errors themselves if they need to. Happy to hear any feedback! -- https://bugs.ruby-lang.org/

1 0

[ruby-core:121260] [Ruby master Feature#18784] `FileUtils.rm_f` and `FileUtils.rm_rf` should not mask exceptions
by Dan0042 (Daniel DeLorme) 07 Mar '25

07 Mar '25

Issue #18784 has been updated by Dan0042 (Daniel DeLorme). It could also be an option like `FileUtils.rm(ignore_missing: true)`, that way it can apply to both `rm` and `rm_r`. ---------------------------------------- Feature #18784: `FileUtils.rm_f` and `FileUtils.rm_rf` should not mask exceptions https://bugs.ruby-lang.org/issues/18784#change-112215 * Author: deivid (David Rodríguez) * Status: Open ---------------------------------------- In recent times, I've been having issues with these methods because they don't let you know when some issue happened while trying to remove the given folders/files. IMO most users expect all pre-existing folders/files that are passed to these methods to be actually removed by the methods. Instead, when this happens, errors are silently swallowed and normally the result is that you will get some other issue further down the road, making the problem hard to debug. The current workaround I'm using is to double check whether the files still exist after the method, and raise a custom error if they do, but I still can't see the original problem, so issues are similarly hard to debug. This is also a deviation from how `rm -rf` and `rm -f` work, since these tools finish with a failure exit code when they fail to remove the given files. Given that `fileutils` is intended to mimic shell functionality, I think this is just a bug. I think the intention of the `force` flag here is to: * Don't prompt for confirmation. * Ignore given arguments that are not files that already exist. But any issue other than that should not be swallowed, and in general I think the method should succeed if and only if the given list of file names does not exist after the methods are done. I think this is in line with the following note I get when I run `man rm`, but also suggests that this is not the standard behavior of "historical implementations" > COMPATIBILITY > > The rm utility differs from historical implementations in that the -f option only masks attempts to remove non-existent files instead of masking a large variety of errors. I implemented this at https://github.com/ruby/fileutils/pull/58, but treating this as a bug. I can also implement a more conservative for approach for users that might be using `FileUtils.rm_rf` or `FileUtils.rm_f` but don't really care if the files are removed or not. Alternative proposals would be `FileUtils.rm_rf(force: strict)`, or `FileUtils.strict_rm_rf`, but to be honest, if this is considered a breaking change, I would ship it as a new major version, and let users update their code to swallow errors themselves if they need to. Happy to hear any feedback! -- https://bugs.ruby-lang.org/

1 0

[ruby-core:121259] [Ruby master Feature#18784] `FileUtils.rm_f` and `FileUtils.rm_rf` should not mask exceptions
by deivid 07 Mar '25

07 Mar '25

Issue #18784 has been updated by deivid (David Rodríguez). Today I again spent a lot of time debugging an issue, and it ended up being an exception swallowed by `FileUtils.rm_rf`. Would you be ok with adding `FileUtils.rm_rf!` that mimics standard `rm -rf` shell behaviour, similar to what @Dan0042 suggested above? A new method does not pose backwards compatibility concerns, and I think the name conveys well that it's the same as `FileUtils.rm_rf` but potentially raising exceptions if deletion fails. Then it would be easy enough to add a RuboCop cop for those who prefer the more strict version to enforce `FileUtils.rm_rf!` over `FileUtils.rm_rf`. I'm happy to implement this if accepted! ---------------------------------------- Feature #18784: `FileUtils.rm_f` and `FileUtils.rm_rf` should not mask exceptions https://bugs.ruby-lang.org/issues/18784#change-112214 * Author: deivid (David Rodríguez) * Status: Open ---------------------------------------- In recent times, I've been having issues with these methods because they don't let you know when some issue happened while trying to remove the given folders/files. IMO most users expect all pre-existing folders/files that are passed to these methods to be actually removed by the methods. Instead, when this happens, errors are silently swallowed and normally the result is that you will get some other issue further down the road, making the problem hard to debug. The current workaround I'm using is to double check whether the files still exist after the method, and raise a custom error if they do, but I still can't see the original problem, so issues are similarly hard to debug. This is also a deviation from how `rm -rf` and `rm -f` work, since these tools finish with a failure exit code when they fail to remove the given files. Given that `fileutils` is intended to mimic shell functionality, I think this is just a bug. I think the intention of the `force` flag here is to: * Don't prompt for confirmation. * Ignore given arguments that are not files that already exist. But any issue other than that should not be swallowed, and in general I think the method should succeed if and only if the given list of file names does not exist after the methods are done. I think this is in line with the following note I get when I run `man rm`, but also suggests that this is not the standard behavior of "historical implementations" > COMPATIBILITY > > The rm utility differs from historical implementations in that the -f option only masks attempts to remove non-existent files instead of masking a large variety of errors. I implemented this at https://github.com/ruby/fileutils/pull/58, but treating this as a bug. I can also implement a more conservative for approach for users that might be using `FileUtils.rm_rf` or `FileUtils.rm_f` but don't really care if the files are removed or not. Alternative proposals would be `FileUtils.rm_rf(force: strict)`, or `FileUtils.strict_rm_rf`, but to be honest, if this is considered a breaking change, I would ship it as a new major version, and let users update their code to swallow errors themselves if they need to. Happy to hear any feedback! -- https://bugs.ruby-lang.org/

1 0

[ruby-core:121253] [Ruby master Bug#21175] Range#max called on a beginles Integer Range with excluded end raises TypeError
by andrykonchin (Andrew Konchin) 07 Mar '25

07 Mar '25

Issue #21175 has been reported by andrykonchin (Andrew Konchin). ---------------------------------------- Bug #21175: Range#max called on a beginles Integer Range with excluded end raises TypeError https://bugs.ruby-lang.org/issues/21175 * Author: andrykonchin (Andrew Konchin) * Status: Open * ruby -v: 3.4.2 * Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN ---------------------------------------- I would expect that for a Range with Integer right boundary `end - 1` is returned: ```ruby (nil...10).max # => (irb):1:in 'Range#max': cannot exclude end value with non Integer begin value (TypeError) ``` -- https://bugs.ruby-lang.org/

2 1

[ruby-core:121201] [Ruby master Bug#21162] Regexp casefold mismatch for latin1 supplemental chars
by headius (Charles Nutter) 07 Mar '25

07 Mar '25

Issue #21162 has been reported by headius (Charles Nutter). ---------------------------------------- Bug #21162: Regexp casefold mismatch for latin1 supplemental chars https://bugs.ruby-lang.org/issues/21162 * Author: headius (Charles Nutter) * Status: Open * Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN ---------------------------------------- Originally reported to joni repo with a possible fix here: https://github.com/jruby/joni/pull/20 From that PR: > When a character is less than or equal to single byte size (0xff), > yet it takes more than 1 byte in the current encoding, the > case folding code incorrectly put it in bitset instead of code > range. As a result, for utf8 encoding, casefold works incorrectly > on characters in range \u0080 to \u00ff (latin1 supplement). > > Before fix: > > "\u00c2" [\u00e0-\u00e5] returns false > "\u00c2" [\u00e2] returns false > "\u00c2" \u00e2 returns true As a Ruby example: ``` $ ruby -v -e 'p(/[\u00e0-\u00e5]/i =~ "\u00c2")' ruby 3.4.1 (2024-12-25 revision 48d4efcb85) +PRISM [arm64-darwin24] nil ``` The PR above was rebased in https://github.com/jruby/joni/pull/85. When that patch is incorporated into JRuby, it behaves as expected: ``` $ ruby -v -e 'p(/[\u00e0-\u00e5]/i =~ "\u00c2")' jruby 10.0.0.0-SNAPSHOT (3.4.0) 2025-02-27 c0e5008419 OpenJDK 64-Bit Server VM 21.0.5+11-LTS on 21.0.5+11-LTS +indy +jit [arm64-darwin] 0 ``` This bug may affect other casefold situations. As I am not very familiar with this code in CRuby (other than from maintaining the port in joni) I would like others to evaluate this fix and help find other places it is needed. -- https://bugs.ruby-lang.org/

2 3

[ruby-core:121236] [Ruby master Bug#21169] "try to mark T_NONE object" with 3.3.7
by stanhu (Stan Hu) 06 Mar '25

06 Mar '25

Issue #21169 has been reported by stanhu (Stan Hu). ---------------------------------------- Bug #21169: "try to mark T_NONE object" with 3.3.7 https://bugs.ruby-lang.org/issues/21169 * Author: stanhu (Stan Hu) * Status: Open * ruby -v: ruby 3.3.7 (2025-01-15 revision be31f993d7) [x86_64-linux] * Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN ---------------------------------------- We have been intermittent `try to mark T_NONE object` erorrs in CI using Ruby 3.3.7. For example: ``` /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/journey/visitors.rb:139: [BUG] try to mark T_NONE object ruby 3.3.7 (2025-01-15 revision be31f993d7) +YJIT [x86_64-linux] -- Control frame information ----------------------------------------------- c:0150 p:---- s:0851 e:000850 CFUNC :+ c:0149 p:0016 s:0846 e:000845 METHOD /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/journey/visitors.rb:139 c:0148 p:0005 s:0841 e:000840 METHOD /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/journey/visitors.rb:70 c:0147 p:0013 s:0836 e:000835 METHOD /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/journey/visitors.rb:63 c:0146 p:0014 s:0831 e:000829 METHOD /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/journey/visitors.rb:139 c:0145 p:0005 s:0825 e:000824 METHOD /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/journey/visitors.rb:70 c:0144 p:0013 s:0820 e:000819 METHOD /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/journey/visitors.rb:63 c:0143 p:0014 s:0815 e:000813 METHOD /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/journey/visitors.rb:139 c:0142 p:0005 s:0809 e:000808 METHOD /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/journey/visitors.rb:70 c:0141 p:0013 s:0804 e:000803 METHOD /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/journey/visitors.rb:63 c:0140 p:0014 s:0799 e:000797 METHOD /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/journey/visitors.rb:139 c:0139 p:0005 s:0793 e:000792 METHOD /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/journey/visitors.rb:70 c:0138 p:0013 s:0788 e:000787 METHOD /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/journey/visitors.rb:63 c:0137 p:0005 s:0783 e:000782 METHOD /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/journey/visitors.rb:58 c:0136 p:0008 s:0778 e:000776 METHOD /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/journey/visitors.rb:135 c:0135 p:0009 s:0772 e:000771 METHOD /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/journey/path/pattern.rb:24 c:0134 p:0093 s:0768 e:000767 METHOD /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/journey/route.rb:69 [FINISH] c:0133 p:---- s:0753 e:000752 CFUNC :new c:0132 p:0032 s:0739 e:000738 METHOD /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/routing/mapper.rb:170 c:0131 p:0011 s:0733 e:000732 METHOD /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/journey/routes.rb:66 c:0130 p:0074 s:0726 e:000725 METHOD /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/routing/route_set.rb:595 c:0129 p:0177 s:0719 e:000718 METHOD /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/routing/mapper.rb:1985 [FINISH] c:0128 p:0065 s:0701 e:000700 METHOD /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/routing/mapper.rb:1956 [FINISH] c:0127 p:0027 s:0687 e:000686 BLOCK /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/routing/mapper.rb:1925 [FINISH] c:0126 p:---- s:0682 e:000681 CFUNC :each c:0125 p:0262 s:0678 e:000677 METHOD /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/routing/mapper.rb:1923 [FINISH] c:0124 p:0182 s:0663 e:000662 METHOD /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/routing/mapper.rb:1662 [FINISH] c:0123 p:0031 s:0653 e:000652 METHOD /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/routing/mapper.rb:735 [FINISH] c:0122 p:0011 s:0645 e:000644 METHOD /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/routing/mapper.rb:696 c:0121 p:0005 s:0639 e:000638 BLOCK /builds/gitlab-org/gitlab/config/routes/project.rb:452 [FINISH] c:0120 p:0022 s:0636 e:000635 METHOD /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/routing/mapper.rb:1885 [FINISH] c:0119 p:0023 s:0631 e:000630 BLOCK /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/routing/mapper.rb:1532 c:0118 p:0012 s:0628 e:000627 METHOD /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/routing/mapper.rb:1765 [FINISH] c:0117 p:0019 s:0623 e:000622 METHOD /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/routing/mapper.rb:1526 c:0116 p:0004 s:0618 e:000617 BLOCK /builds/gitlab-org/gitlab/config/routes/project.rb:451 [FINISH] c:0115 p:0008 s:0615 e:000614 BLOCK /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/routing/mapper.rb:1468 c:0114 p:0012 s:0612 e:000611 METHOD /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/routing/mapper.rb:886 [FINISH] c:0113 p:0021 s:0607 e:000606 METHOD /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/routing/mapper.rb:1773 [FINISH] c:0112 p:0031 s:0601 e:000600 BLOCK /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/routing/mapper.rb:1467 [FINISH] c:0111 p:0012 s:0598 e:000597 METHOD /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/routing/mapper.rb:1765 [FINISH] c:0110 p:0031 s:0593 e:000592 METHOD /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/routing/mapper.rb:1465 [FINISH] c:0109 p:---- s:0586 e:000585 CFUNC :public_send c:0108 p:0015 s:0579 e:000578 BLOCK /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/routing/mapper.rb:1730 c:0107 p:0278 s:0576 e:000575 METHOD /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/routing/mapper.rb:871 [FINISH] c:0106 p:0084 s:0567 e:000566 METHOD /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/routing/mapper.rb:1729 [FINISH] c:0105 p:0021 s:0558 e:000557 METHOD /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/routing/mapper.rb:1461 c:0104 p:0584 s:0551 E:0026b0 BLOCK /builds/gitlab-org/gitlab/config/routes/project.rb:450 [FINISH] c:0103 p:0278 s:0548 e:000547 METHOD /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/routing/mapper.rb:871 c:0102 p:0006 s:0539 E:002690 BLOCK /builds/gitlab-org/gitlab/config/routes/project.rb:30 [FINISH] c:0101 p:0278 s:0536 e:000535 METHOD /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/routing/mapper.rb:871 c:0100 p:0018 s:0527 E:002670 BLOCK /builds/gitlab-org/gitlab/config/routes/project.rb:22 [FINISH] c:0099 p:0278 s:0524 e:000523 METHOD /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/routing/mapper.rb:871 c:0098 p:0012 s:0515 E:002650 BLOCK /builds/gitlab-org/gitlab/config/routes/project.rb:17 [FINISH] c:0097 p:0278 s:0512 e:000511 METHOD /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/routing/mapper.rb:871 c:0096 p:0013 s:0503 e:000502 METHOD /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/routing/mapper.rb:1000 c:0095 p:0008 s:0497 E:002630 EVAL /builds/gitlab-org/gitlab/config/routes/project.rb:3 [FINISH] c:0094 p:---- s:0494 e:000493 CFUNC :instance_eval c:0093 p:0021 s:0488 E:000888 METHOD /builds/gitlab-org/gitlab/lib/gitlab/patch/draw_route.rb:30 c:0092 p:0018 s:0483 e:000482 METHOD /builds/gitlab-org/gitlab/lib/gitlab/patch/draw_route.rb:17 c:0091 p:0010 s:0478 e:000476 METHOD /builds/gitlab-org/gitlab/lib/gitlab/patch/draw_route.rb:11 c:0090 p:0347 s:0471 E:000798 BLOCK /builds/gitlab-org/gitlab/config/routes.rb:304 [FINISH] c:0089 p:---- s:0467 e:000466 CFUNC :instance_exec c:0088 p:0030 s:0463 e:000462 METHOD /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/routing/route_set.rb:428 c:0087 p:0015 s:0457 e:000456 METHOD /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/routing/route_set.rb:410 c:0086 p:0009 s:0452 E:000040 BLOCK /builds/gitlab-org/gitlab/config/routes.rb:7 c:0085 p:0032 s:0449 e:000448 METHOD /builds/gitlab-org/gitlab/lib/initializer_connections.rb:19 c:0084 p:0017 s:0443 E:000020 TOP /builds/gitlab-org/gitlab/config/routes.rb:6 [FINISH] c:0083 p:---- s:0440 e:000439 CFUNC :load c:0082 p:0005 s:0435 e:000434 BLOCK /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/railties-7.0.8.7/lib/rails/application/routes_reloader.rb:50 [FINISH] c:0081 p:---- s:0431 e:000430 CFUNC :each c:0080 p:0006 s:0427 e:000426 METHOD /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/railties-7.0.8.7/lib/rails/application/routes_reloader.rb:50 c:0079 p:0007 s:0423 e:000422 METHOD /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/railties-7.0.8.7/lib/rails/application/routes_reloader.rb:24 c:0078 p:0003 s:0419 e:000418 BLOCK /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/railties-7.0.8.7/lib/rails/application/routes_reloader.rb:38 c:0077 p:0020 s:0416 e:000415 METHOD /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/activesupport-7.0.8.7/lib/active_support/file_update_checker.rb:83 c:0076 p:0017 s:0412 e:000411 METHOD /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/railties-7.0.8.7/lib/rails/application/routes_reloader.rb:13 c:0075 p:0020 s:0403 e:000402 BLOCK /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/railties-7.0.8.7/lib/rails/application/finisher.rb:158 [FINISH] c:0074 p:---- s:0398 e:000397 CFUNC :instance_exec c:0073 p:0013 s:0393 e:000392 METHOD /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/railties-7.0.8.7/lib/rails/initializable.rb:32 c:0072 p:0017 s:0388 e:000387 BLOCK /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/railties-7.0.8.7/lib/rails/initializable.rb:61 [FINISH] c:0071 p:0016 s:0384 e:000383 BLOCK /usr/local/lib/ruby/3.3.0/tsort.rb:231 [FINISH] c:0070 p:0004 s:0380 e:000379 BLOCK /usr/local/lib/ruby/3.3.0/tsort.rb:353 [FINISH] c:0069 p:0004 s:0376 e:000375 BLOCK /usr/local/lib/ruby/3.3.0/tsort.rb:425 [FINISH] c:0068 p:0098 s:0372 E:002610 METHOD /usr/local/lib/ruby/3.3.0/tsort.rb:434 c:0067 p:0049 s:0360 E:0009c8 BLOCK /usr/local/lib/ruby/3.3.0/tsort.rb:424 [FINISH] c:0066 p:---- s:0354 e:000353 CFUNC :each c:0065 p:0010 s:0350 e:000349 METHOD /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/railties-7.0.8.7/lib/rails/initializable.rb:50 [FINISH] c:0064 p:---- s:0344 e:000343 CFUNC :call c:0063 p:0067 s:0339 E:0025b0 METHOD /usr/local/lib/ruby/3.3.0/tsort.rb:418 c:0062 p:0023 s:0327 E:0015e8 BLOCK /usr/local/lib/ruby/3.3.0/tsort.rb:352 [FINISH] c:0061 p:---- s:0323 e:000322 CFUNC :each c:0060 p:---- s:0320 e:000319 CFUNC :call c:0059 p:0029 s:0316 E:000100 METHOD /usr/local/lib/ruby/3.3.0/tsort.rb:350 c:0058 p:0024 s:0308 E:000cb0 METHOD /usr/local/lib/ruby/3.3.0/tsort.rb:229 c:0057 p:0026 s:0302 e:000301 METHOD /usr/local/lib/ruby/3.3.0/tsort.rb:208 c:0056 p:0019 s:0295 E:000680 METHOD /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/railties-7.0.8.7/lib/rails/initializable.rb:60 c:0055 p:0021 s:0289 e:000288 METHOD /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/railties-7.0.8.7/lib/rails/application.rb:372 c:0054 p:0012 s:0284 e:000283 TOP /builds/gitlab-org/gitlab/config/environment.rb:7 [FINISH] c:0053 p:---- s:0281 e:000280 CFUNC :require c:0052 p:0052 s:0276 e:000275 BLOCK /usr/local/lib/ruby/3.3.0/bundled_gems.rb:69 [FINISH] c:0051 p:0131 s:0270 e:000269 METHOD /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/bootsnap-1.18.4/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:30 [FINISH] c:0050 p:0055 s:0261 e:000260 METHOD /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/zeitwerk-2.6.7/lib/zeitwerk/kernel.rb:38 c:0049 p:0022 s:0253 e:000252 METHOD /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/railties-7.0.8.7/lib/rails/application.rb:348 c:0048 p:0011 s:0248 E:0026f0 BLOCK /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/railties-7.0.8.7/lib/rails/application.rb:506 c:0047 p:0007 s:0245 e:000244 BLOCK /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/rake-13.0.6/lib/rake/task.rb:281 [FINISH] c:0046 p:---- s:0241 e:000240 CFUNC :each c:0045 p:0113 s:0237 e:000236 METHOD /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/rake-13.0.6/lib/rake/task.rb:281 c:0044 p:0117 s:0231 e:000230 BLOCK /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/rake-13.0.6/lib/rake/task.rb:219 [FINISH] c:0043 p:---- s:0227 e:000226 CFUNC :synchronize c:0042 p:0015 s:0223 e:000222 METHOD /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/rake-13.0.6/lib/rake/task.rb:199 c:0041 p:0018 s:0216 e:000215 BLOCK /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/rake-13.0.6/lib/rake/task.rb:243 [FINISH] c:0040 p:---- s:0211 e:000210 CFUNC :each c:0039 p:0023 s:0207 e:000206 METHOD /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/rake-13.0.6/lib/rake/task.rb:241 c:0038 p:0106 s:0201 e:000200 BLOCK /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/rake-13.0.6/lib/rake/task.rb:218 [FINISH] c:0037 p:---- s:0197 e:000196 CFUNC :synchronize c:0036 p:0015 s:0193 e:000192 METHOD /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/rake-13.0.6/lib/rake/task.rb:199 c:0035 p:0018 s:0186 e:000185 BLOCK /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/rake-13.0.6/lib/rake/task.rb:243 [FINISH] c:0034 p:---- s:0181 e:000180 CFUNC :each c:0033 p:0023 s:0177 e:000176 METHOD /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/rake-13.0.6/lib/rake/task.rb:241 c:0032 p:0106 s:0171 e:000170 BLOCK /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/rake-13.0.6/lib/rake/task.rb:218 [FINISH] c:0031 p:---- s:0167 e:000166 CFUNC :synchronize c:0030 p:0015 s:0163 e:000162 METHOD /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/rake-13.0.6/lib/rake/task.rb:199 c:0029 p:0018 s:0156 e:000155 METHOD /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/rake-13.0.6/lib/rake/task.rb:188 c:0028 p:0027 s:0150 e:000149 METHOD /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/rake-13.0.6/lib/rake/application.rb:160 c:0027 p:0005 s:0142 e:000141 BLOCK /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/rake-13.0.6/lib/rake/application.rb:116 [FINISH] c:0026 p:---- s:0138 e:000137 CFUNC :each c:0025 p:0029 s:0134 e:000133 BLOCK /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/rake-13.0.6/lib/rake/application.rb:116 c:0024 p:0019 s:0131 e:000130 METHOD /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/rake-13.0.6/lib/rake/application.rb:125 c:0023 p:0004 s:0126 e:000125 METHOD /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/rake-13.0.6/lib/rake/application.rb:110 c:0022 p:0015 s:0122 e:000121 BLOCK /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/rake-13.0.6/lib/rake/application.rb:83 c:0021 p:0002 s:0119 e:000118 METHOD /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/rake-13.0.6/lib/rake/application.rb:186 c:0020 p:0008 s:0114 e:000113 METHOD /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/rake-13.0.6/lib/rake/application.rb:80 c:0019 p:0012 s:0109 e:000108 TOP /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/rake-13.0.6/exe/rake:27 [FINISH] c:0018 p:---- s:0106 e:000105 CFUNC :load c:0017 p:0078 s:0101 e:000100 TOP /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/bin/rake:25 [FINISH] c:0016 p:---- s:0096 e:000095 CFUNC :load c:0015 p:0064 s:0091 e:000090 METHOD /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/bundler-2.5.11/lib/bundler/cli/exec.rb:58 c:0014 p:0050 s:0085 e:000084 METHOD /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/bundler-2.5.11/lib/bundler/cli/exec.rb:23 c:0013 p:0044 s:0080 e:000079 METHOD /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/bundler-2.5.11/lib/bundler/cli.rb:455 c:0012 p:0054 s:0073 e:000072 METHOD /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/bundler-2.5.11/lib/bundler/vendor/thor/lib/thor/command.rb:28 c:0011 p:0040 s:0065 e:000064 METHOD /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/bundler-2.5.11/lib/bundler/vendor/thor/lib/thor/invocation.rb:127 c:0010 p:0213 s:0058 e:000057 METHOD /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/bundler-2.5.11/lib/bundler/vendor/thor/lib/thor.rb:527 c:0009 p:0008 s:0045 e:000044 METHOD /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/bundler-2.5.11/lib/bundler/cli.rb:35 c:0008 p:0044 s:0040 e:000039 METHOD /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/bundler-2.5.11/lib/bundler/vendor/thor/lib/thor/base.rb:584 c:0007 p:0022 s:0033 e:000032 METHOD /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/bundler-2.5.11/lib/bundler/cli.rb:29 c:0006 p:0042 s:0028 e:000027 BLOCK /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/bundler-2.5.11/exe/bundle:28 c:0005 p:0007 s:0022 e:000021 METHOD /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/bundler-2.5.11/lib/bundler/friendly_errors.rb:117 c:0004 p:0051 s:0017 E:000ed8 TOP /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/bundler-2.5.11/exe/bundle:20 [FINISH] c:0003 p:---- s:0013 e:000012 CFUNC :load c:0002 p:0081 s:0008 E:001260 EVAL /usr/local/bin/bundle:25 [FINISH] c:0001 p:0000 s:0003 E:0016b0 DUMMY [FINISH] -- Ruby level backtrace information ---------------------------------------- /usr/local/bin/bundle:25:in `<main>' /usr/local/bin/bundle:25:in `load' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/bundler-2.5.11/exe/bundle:20:in `<top (required)>' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/bundler-2.5.11/lib/bundler/friendly_errors.rb:117:in `with_friendly_errors' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/bundler-2.5.11/exe/bundle:28:in `block in <top (required)>' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/bundler-2.5.11/lib/bundler/cli.rb:29:in `start' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/bundler-2.5.11/lib/bundler/vendor/thor/lib/thor/base.rb:584:in `start' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/bundler-2.5.11/lib/bundler/cli.rb:35:in `dispatch' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/bundler-2.5.11/lib/bundler/vendor/thor/lib/thor.rb:527:in `dispatch' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/bundler-2.5.11/lib/bundler/vendor/thor/lib/thor/invocation.rb:127:in `invoke_command' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/bundler-2.5.11/lib/bundler/vendor/thor/lib/thor/command.rb:28:in `run' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/bundler-2.5.11/lib/bundler/cli.rb:455:in `exec' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/bundler-2.5.11/lib/bundler/cli/exec.rb:23:in `run' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/bundler-2.5.11/lib/bundler/cli/exec.rb:58:in `kernel_load' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/bundler-2.5.11/lib/bundler/cli/exec.rb:58:in `load' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/bin/rake:25:in `<top (required)>' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/bin/rake:25:in `load' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/rake-13.0.6/exe/rake:27:in `<top (required)>' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/rake-13.0.6/lib/rake/application.rb:80:in `run' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/rake-13.0.6/lib/rake/application.rb:186:in `standard_exception_handling' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/rake-13.0.6/lib/rake/application.rb:83:in `block in run' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/rake-13.0.6/lib/rake/application.rb:110:in `top_level' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/rake-13.0.6/lib/rake/application.rb:125:in `run_with_threads' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/rake-13.0.6/lib/rake/application.rb:116:in `block in top_level' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/rake-13.0.6/lib/rake/application.rb:116:in `each' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/rake-13.0.6/lib/rake/application.rb:116:in `block (2 levels) in top_level' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/rake-13.0.6/lib/rake/application.rb:160:in `invoke_task' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/rake-13.0.6/lib/rake/task.rb:188:in `invoke' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/rake-13.0.6/lib/rake/task.rb:199:in `invoke_with_call_chain' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/rake-13.0.6/lib/rake/task.rb:199:in `synchronize' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/rake-13.0.6/lib/rake/task.rb:218:in `block in invoke_with_call_chain' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/rake-13.0.6/lib/rake/task.rb:241:in `invoke_prerequisites' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/rake-13.0.6/lib/rake/task.rb:241:in `each' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/rake-13.0.6/lib/rake/task.rb:243:in `block in invoke_prerequisites' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/rake-13.0.6/lib/rake/task.rb:199:in `invoke_with_call_chain' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/rake-13.0.6/lib/rake/task.rb:199:in `synchronize' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/rake-13.0.6/lib/rake/task.rb:218:in `block in invoke_with_call_chain' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/rake-13.0.6/lib/rake/task.rb:241:in `invoke_prerequisites' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/rake-13.0.6/lib/rake/task.rb:241:in `each' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/rake-13.0.6/lib/rake/task.rb:243:in `block in invoke_prerequisites' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/rake-13.0.6/lib/rake/task.rb:199:in `invoke_with_call_chain' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/rake-13.0.6/lib/rake/task.rb:199:in `synchronize' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/rake-13.0.6/lib/rake/task.rb:219:in `block in invoke_with_call_chain' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/rake-13.0.6/lib/rake/task.rb:281:in `execute' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/rake-13.0.6/lib/rake/task.rb:281:in `each' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/rake-13.0.6/lib/rake/task.rb:281:in `block in execute' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/railties-7.0.8.7/lib/rails/application.rb:506:in `block in run_tasks_blocks' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/railties-7.0.8.7/lib/rails/application.rb:348:in `require_environment!' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/zeitwerk-2.6.7/lib/zeitwerk/kernel.rb:38:in `require' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/bootsnap-1.18.4/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:30:in `require' /usr/local/lib/ruby/3.3.0/bundled_gems.rb:69:in `block (2 levels) in replace_require' /usr/local/lib/ruby/3.3.0/bundled_gems.rb:69:in `require' /builds/gitlab-org/gitlab/config/environment.rb:7:in `<main>' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/railties-7.0.8.7/lib/rails/application.rb:372:in `initialize!' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/railties-7.0.8.7/lib/rails/initializable.rb:60:in `run_initializers' /usr/local/lib/ruby/3.3.0/tsort.rb:208:in `tsort_each' /usr/local/lib/ruby/3.3.0/tsort.rb:229:in `tsort_each' /usr/local/lib/ruby/3.3.0/tsort.rb:350:in `each_strongly_connected_component' /usr/local/lib/ruby/3.3.0/tsort.rb:350:in `call' /usr/local/lib/ruby/3.3.0/tsort.rb:350:in `each' /usr/local/lib/ruby/3.3.0/tsort.rb:352:in `block in each_strongly_connected_component' /usr/local/lib/ruby/3.3.0/tsort.rb:418:in `each_strongly_connected_component_from' /usr/local/lib/ruby/3.3.0/tsort.rb:418:in `call' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/railties-7.0.8.7/lib/rails/initializable.rb:50:in `tsort_each_child' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/railties-7.0.8.7/lib/rails/initializable.rb:50:in `each' /usr/local/lib/ruby/3.3.0/tsort.rb:424:in `block in each_strongly_connected_component_from' /usr/local/lib/ruby/3.3.0/tsort.rb:434:in `each_strongly_connected_component_from' /usr/local/lib/ruby/3.3.0/tsort.rb:425:in `block (2 levels) in each_strongly_connected_component_from' /usr/local/lib/ruby/3.3.0/tsort.rb:353:in `block (2 levels) in each_strongly_connected_component' /usr/local/lib/ruby/3.3.0/tsort.rb:231:in `block in tsort_each' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/railties-7.0.8.7/lib/rails/initializable.rb:61:in `block in run_initializers' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/railties-7.0.8.7/lib/rails/initializable.rb:32:in `run' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/railties-7.0.8.7/lib/rails/initializable.rb:32:in `instance_exec' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/railties-7.0.8.7/lib/rails/application/finisher.rb:158:in `block in <module:Finisher>' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/railties-7.0.8.7/lib/rails/application/routes_reloader.rb:13:in `execute' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/activesupport-7.0.8.7/lib/active_support/file_update_checker.rb:83:in `execute' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/railties-7.0.8.7/lib/rails/application/routes_reloader.rb:38:in `block in updater' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/railties-7.0.8.7/lib/rails/application/routes_reloader.rb:24:in `reload!' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/railties-7.0.8.7/lib/rails/application/routes_reloader.rb:50:in `load_paths' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/railties-7.0.8.7/lib/rails/application/routes_reloader.rb:50:in `each' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/railties-7.0.8.7/lib/rails/application/routes_reloader.rb:50:in `block in load_paths' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/railties-7.0.8.7/lib/rails/application/routes_reloader.rb:50:in `load' /builds/gitlab-org/gitlab/config/routes.rb:6:in `<main>' /builds/gitlab-org/gitlab/lib/initializer_connections.rb:19:in `raise_if_new_database_connection' /builds/gitlab-org/gitlab/config/routes.rb:7:in `block in <main>' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/routing/route_set.rb:410:in `draw' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/routing/route_set.rb:428:in `eval_block' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/routing/route_set.rb:428:in `instance_exec' /builds/gitlab-org/gitlab/config/routes.rb:304:in `block (2 levels) in <main>' /builds/gitlab-org/gitlab/lib/gitlab/patch/draw_route.rb:11:in `draw' /builds/gitlab-org/gitlab/lib/gitlab/patch/draw_route.rb:17:in `draw_ce' /builds/gitlab-org/gitlab/lib/gitlab/patch/draw_route.rb:30:in `draw_route' /builds/gitlab-org/gitlab/lib/gitlab/patch/draw_route.rb:30:in `instance_eval' /builds/gitlab-org/gitlab/config/routes/project.rb:3:in `draw_route' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/routing/mapper.rb:1000:in `constraints' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/routing/mapper.rb:871:in `scope' /builds/gitlab-org/gitlab/config/routes/project.rb:17:in `block in draw_route' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/routing/mapper.rb:871:in `scope' /builds/gitlab-org/gitlab/config/routes/project.rb:22:in `block (2 levels) in draw_route' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/routing/mapper.rb:871:in `scope' /builds/gitlab-org/gitlab/config/routes/project.rb:30:in `block (3 levels) in draw_route' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/routing/mapper.rb:871:in `scope' /builds/gitlab-org/gitlab/config/routes/project.rb:450:in `block (4 levels) in draw_route' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/routing/mapper.rb:1461:in `resources' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/routing/mapper.rb:1729:in `apply_common_behavior_for' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/routing/mapper.rb:871:in `scope' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/routing/mapper.rb:1730:in `block in apply_common_behavior_for' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/routing/mapper.rb:1730:in `public_send' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/routing/mapper.rb:1465:in `resources' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/routing/mapper.rb:1765:in `with_scope_level' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/routing/mapper.rb:1467:in `block in resources' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/routing/mapper.rb:1773:in `resource_scope' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/routing/mapper.rb:886:in `controller' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/routing/mapper.rb:1468:in `block (2 levels) in resources' /builds/gitlab-org/gitlab/config/routes/project.rb:451:in `block (5 levels) in draw_route' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/routing/mapper.rb:1526:in `member' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/routing/mapper.rb:1765:in `with_scope_level' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/routing/mapper.rb:1532:in `block in member' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/routing/mapper.rb:1885:in `path_scope' /builds/gitlab-org/gitlab/config/routes/project.rb:452:in `block (6 levels) in draw_route' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/routing/mapper.rb:696:in `post' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/routing/mapper.rb:735:in `map_method' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/routing/mapper.rb:1662:in `match' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/routing/mapper.rb:1923:in `map_match' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/routing/mapper.rb:1923:in `each' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/routing/mapper.rb:1925:in `block in map_match' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/routing/mapper.rb:1956:in `decomposed_match' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/routing/mapper.rb:1985:in `add_route' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/routing/route_set.rb:595:in `add_route' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/journey/routes.rb:66:in `add_route' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/routing/mapper.rb:170:in `make_route' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/routing/mapper.rb:170:in `new' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/journey/route.rb:69:in `initialize' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/journey/path/pattern.rb:24:in `build_formatter' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/journey/visitors.rb:135:in `accept' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/journey/visitors.rb:58:in `accept' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/journey/visitors.rb:63:in `visit' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/journey/visitors.rb:70:in `visit_CAT' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/journey/visitors.rb:139:in `binary' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/journey/visitors.rb:63:in `visit' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/journey/visitors.rb:70:in `visit_CAT' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/journey/visitors.rb:139:in `binary' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/journey/visitors.rb:63:in `visit' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/journey/visitors.rb:70:in `visit_CAT' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/journey/visitors.rb:139:in `binary' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/journey/visitors.rb:63:in `visit' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/journey/visitors.rb:70:in `visit_CAT' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/journey/visitors.rb:139:in `binary' /builds/gitlab-org/gitlab/vendor/ruby/3.3.0/gems/actionpack-7.0.8.7/lib/action_dispatch/journey/visitors.rb:139:in `+' -- Threading information --------------------------------------------------- Total ractor count: 1 Ruby thread count for this ractor: 1 -- C level backtrace information ------------------------------------------- /usr/local/lib/libruby.so.3.3(rb_print_backtrace+0x14) [0x7c7d2cc6417d] /usr/src/ruby/vm_dump.c:820 /usr/local/lib/libruby.so.3.3(rb_vm_bugreport) /usr/src/ruby/vm_dump.c:1151 /usr/local/lib/libruby.so.3.3(bug_report_end+0x0) [0x7c7d2ca52aee] /usr/src/ruby/error.c:1042 /usr/local/lib/libruby.so.3.3(rb_bug_without_die) /usr/src/ruby/error.c:1042 /usr/local/lib/libruby.so.3.3(die+0x0) [0x7c7d2c98f3d6] /usr/src/ruby/error.c:1050 /usr/local/lib/libruby.so.3.3(rb_bug) /usr/src/ruby/error.c:1052 /usr/local/lib/libruby.so.3.3(gc_mark_ptr+0x1a9) [0x7c7d2ca7b1b9] /usr/src/ruby/gc.c:7080 /usr/local/lib/libruby.so.3.3(gc_mark+0x13) [0x7c7d2ca7d187] /usr/src/ruby/gc.c:7117 /usr/local/lib/libruby.so.3.3(gc_mark_children) /usr/src/ruby/gc.c:7480 /usr/local/lib/libruby.so.3.3(gc_mark_stacked_objects+0x78) [0x7c7d2ca7e6c8] /usr/src/ruby/gc.c:7572 /usr/local/lib/libruby.so.3.3(gc_mark_stacked_objects_all) /usr/src/ruby/gc.c:7610 /usr/local/lib/libruby.so.3.3(gc_marks_rest) /usr/src/ruby/gc.c:8805 /usr/local/lib/libruby.so.3.3(gc_marking_exit+0x0) [0x7c7d2ca7fd04] /usr/src/ruby/gc.c:8863 /usr/local/lib/libruby.so.3.3(gc_marks) /usr/src/ruby/gc.c:8874 /usr/local/lib/libruby.so.3.3(gc_start) /usr/src/ruby/gc.c:9616 /usr/local/lib/libruby.so.3.3(heap_prepare+0x2e) [0x7c7d2ca80475] /usr/src/ruby/gc.c:2517 /usr/local/lib/libruby.so.3.3(heap_next_free_page) /usr/src/ruby/gc.c:2732 /usr/local/lib/libruby.so.3.3(newobj_alloc) /usr/src/ruby/gc.c:2834 /usr/local/lib/libruby.so.3.3(newobj_init+0x0) [0x7c7d2ca83fe9] /usr/src/ruby/gc.c:2937 /usr/local/lib/libruby.so.3.3(newobj_of0) /usr/src/ruby/gc.c:2938 /usr/local/lib/libruby.so.3.3(newobj_of) /usr/src/ruby/gc.c:2954 /usr/local/lib/libruby.so.3.3(rb_wb_protected_newobj_of) /usr/src/ruby/gc.c:2969 /usr/local/lib/libruby.so.3.3(rb_array_const_ptr+0x0) [0x7c7d2c9a31b1] /usr/src/ruby/array.c:4888 /usr/local/lib/libruby.so.3.3(rb_ary_plus) /usr/src/ruby/array.c:4890 [0x7c7d2d67c3ad] ``` I don't have a consistent repro yet, but still working on it. I see https://bugs.ruby-lang.org/issues/21021, but https://github.com/ruby/ruby/pull/12660 doesn't appear to apply to Ruby 3.3.7. Is it possible this was already fixed in 3.4.1? -- https://bugs.ruby-lang.org/

3 3

[ruby-core:121172] [Ruby master Feature#21157] Comparison operator <>
by lpogic 05 Mar '25

05 Mar '25

Issue #21157 has been reported by lpogic (Łukasz Pomietło). ---------------------------------------- Feature #21157: Comparison operator <> https://bugs.ruby-lang.org/issues/21157 * Author: lpogic (Łukasz Pomietło) * Status: Open ---------------------------------------- I propose introducing a comparison operator *<>* which would give the following results: ```ruby 1 <> 2 # => -1 2 <> 1 # => 1 1 <> 1 # => false 1 <> "a" # => true ``` With the help of the new operator, complex ordering expressions could be written explicitly. For example: ```ruby Point = Struct.new(:x, :y) array = [Point.new(1, 2), Point.new(6, 4), Point.new(2, 2), Point.new(5, 2)] array.sort{|a, b| a.y <> b.y || b.x <> a.x || 0 } # => [#<struct Point x=5, y=2>, #<struct Point x=2, y=2>, #<struct Point x=1, y=2>, #<struct Point x=6, y=4>] ``` The *<>* notation may look familiar to sql users, where it means 'not equal'. Defined in the form given it will retain this meaning to some extent: ```ruby a = b = 1 a_not_equal_b if a <> b a_equal_b unless a <> b ``` -- https://bugs.ruby-lang.org/

5 10

[ruby-core:121238] [Ruby master Misc#19122] Use MADV_DONTNEED instead of MADV_FREE when freeing a Fiber's stack
by ioquatix (Samuel Williams) 04 Mar '25

04 Mar '25

Issue #19122 has been updated by ioquatix (Samuel Williams). On the latest Linux kernel, the constants have changed: ``` MADV_DONTNEED = 4 MADV_FREE = 8 ``` I did a quick comparison, creating 10,000 fibers x10 times in a loop: ``` samuel@aiko ~/D/s/memory-leak (main)> time RUBY_SHARED_FIBER_POOL_FREE_STACKS=8 bundle exec test.rb >/dev/null <main>: warning: Setting RUBY_SHARED_FIBER_POOL_FREE_STACKS to a value greater than 1 is operating system specific, and may cause crashes. ________________________________________________________ Executed in 841.07 millis fish external usr time 373.88 millis 441.00 micros 373.44 millis sys time 463.22 millis 168.00 micros 463.05 millis samuel@aiko ~/D/s/memory-leak (main)> time RUBY_SHARED_FIBER_POOL_FREE_STACKS=16 bundle exec test.rb >/dev/null <main>: warning: Setting RUBY_SHARED_FIBER_POOL_FREE_STACKS to a value greater than 1 is operating system specific, and may cause crashes. ________________________________________________________ Executed in 582.77 millis fish external usr time 357.66 millis 420.00 micros 357.24 millis sys time 220.90 millis 164.00 micros 220.74 millis samuel@aiko ~/D/s/memory-leak (main)> time RUBY_SHARED_FIBER_POOL_FREE_STACKS=0 bundle exec test.rb >/dev/null ________________________________________________________ Executed in 444.61 millis fish external usr time 312.92 millis 503.00 micros 312.41 millis sys time 128.99 millis 0.00 micros 128.99 millis ``` Also memory usage as we expected: ``` samuel@aiko ~/D/s/memory-leak (main)> RUBY_SHARED_FIBER_POOL_FREE_STACKS=16 bundle exec test.rb <main>: warning: Setting RUBY_SHARED_FIBER_POOL_FREE_STACKS to a value greater than 1 is operating system specific, and may cause crashes. PID: 70235 Memory usage: 150.82 MB Clearing fibers and garbage collecting... Memory usage: 150.82 MB samuel@aiko ~/D/s/memory-leak (main)> RUBY_SHARED_FIBER_POOL_FREE_STACKS=8 bundle exec test.rb <main>: warning: Setting RUBY_SHARED_FIBER_POOL_FREE_STACKS to a value greater than 1 is operating system specific, and may cause crashes. PID: 70279 Memory usage: 151.63 MB Clearing fibers and garbage collecting... Memory usage: 73.63 MB ``` Using the following test script: ``` #!/usr/bin/env ruby require "memory/leak/system" def print_memory_usage size = Memory::Leak::System.memory_usage(Process.pid) units = %w(B KB MB GB TB) unit = 0 while size > 1024 && unit < units.size size /= 1024.0 unit += 1 end puts "Memory usage: %.2f %s" % [size, units[unit]] end puts "PID: #{Process.pid}" 10.times do |i| puts "Iteration: #{i}" # Create 10,000 fibers: fibers = 10_000.times.map do Fiber.new do Fiber.yield Fiber.current end.resume end # Print memory usage: print_memory_usage puts "Clearing fibers and garbage collecting..." # Clear fibers: fibers.clear GC.start # Print memory usage: print_memory_usage end ``` ---------------------------------------- Misc #19122: Use MADV_DONTNEED instead of MADV_FREE when freeing a Fiber's stack https://bugs.ruby-lang.org/issues/19122#change-112186 * Author: smcgivern (Sean McGivern) * Status: Assigned * Assignee: ioquatix (Samuel Williams) ---------------------------------------- I'd like to propose that Ruby stops using MADV_FREE when freeing a Fiber's stack, and switches to using MADV_DONTNEED even when MADV_FREE is supported. MADV_FREE is used in one place in the Ruby codebase, when freeing the stack of a freed Fiber: https://git.ruby-lang.org/ruby.git/tree/cont.c#n683 The comment for `fiber_pool_stack_free` says: ```c // We advise the operating system that the stack memory pages are no longer being used. // This introduce some performance overhead but allows system to relaim memory when there is pressure. ``` Where possible (i.e. on Linux 4.5 and later), `fiber_pool_stack_free` uses `MADV_FREE` over `MADV_DONTNEED`. This has the side effect that memory statistics such as RSS will not reduce until and unless the OS actually reclaims that memory. If that doesn't happen, then the reported memory usage via RSS will be much higher than the 'real' memory usage. If this was pervasive throughtout the Ruby codebase then that would be one thing, but currently this is just for Fiber. This means that: 1. A program that doesn't use Fiber will have somewhat reliable RSS statistics on recent Linux. 2. A program that heavily uses Fiber (such as something using Async::HTTP) will see an inflated RSS statistic. Go made a similar change to the one I'm proposing here for similar reasons: https://github.com/golang/go/issues/42330 > While `MADV_FREE` is somewhat faster than `MADV_DONTNEED`, it doesn't affect many of the statistics that `MADV_DONTNEED` does until the memory is actually reclaimed. This generally leads to poor user experience, like confusing stats in `top` and other monitoring tools; and bad integration with management systems that respond to memory usage. > [...] > I propose we change the default to prefer `MADV_DONTNEED` over `MADV_FREE`, to favor user-friendliness and minimal surprise over performance. I think it's become clear that Linux's implementation of `MADV_FREE` ultimately doesn't meet our needs. As an aside, MADV_FREE was not used in Ruby 3.1 (https://bugs.ruby-lang.org/issues/19101) and I haven't found any bugs filed about this behaviour other than that one. -- https://bugs.ruby-lang.org/

1 0

[ruby-core:121193] [Ruby master Bug#21161] Crash when locale is set to Turkish tr_TR.UTF-8
by srbaker (Steven Baker) 04 Mar '25

04 Mar '25

Issue #21161 has been reported by srbaker (Steven Baker). ---------------------------------------- Bug #21161: Crash when locale is set to Turkish tr_TR.UTF-8 https://bugs.ruby-lang.org/issues/21161 * Author: srbaker (Steven Baker) * Status: Open * ruby -v: ruby 3.4.2 (2025-02-15 revision d2930f8e7a) +PRISM [x86_64-linux] * Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN ---------------------------------------- TL;DR this bug was reported in our tracker, and I'm pushing it upstream: https://bugzilla.opensuse.org/show_bug.cgi?id=1237861 When the locale is set to `tr_TR.UTF-8`, there is an encoding error. It has been narrowed down specifically to setting `LC_CTYPE`. To reproduce simply run `LC_CTYPE=tr_TR.UTF-8 ruby -e "puts 42"` Example from a fresh 3.4.2 install: ``` shell srbaker@geekopad:~> LC_CTYPE=tr_TR.UTF-8 ruby -e "puts 42" /home/srbaker/.local/share/mise/installs/ruby/3.4.2/lib64/ruby/3.4.0/rubygems.rb:9:in 'Kernel#require': /home/srbaker/.local/share/mise/installs/ruby/3.4.2/lib64/ruby/3.4.0/x86_64-linux/rbconfig.rb:1: unknown or invalid encoding in the magic comment (ArgumentError) > 1 | # encoding: ascii-8bit | ^~~~~~~~~~ 2 | # frozen-string-literal: false 3 | # from /home/srbaker/.local/share/mise/installs/ruby/3.4.2/lib64/ruby/3.4.0/rubygems.rb:9:in '<top (required)>' from <internal:gem_prelude>:2:in 'Kernel#require' from <internal:gem_prelude>:2:in '<internal:gem_prelude>' ``` This reproduces across multiple installs of ruby: from our packages, locally built on both GNU/Linux and macOS. It looks like it's related to some normalisation on lowercase i, which in Turkish appears to produce a lowercase i without a dot, and the string. Details in our bug linked above. -- https://bugs.ruby-lang.org/

3 5

[ruby-core:121141] [Ruby master Bug#21153] ::Foo ||= p 1 should parse
by qnighy (Masaki Hara) 03 Mar '25

03 Mar '25

Issue #21153 has been reported by qnighy (Masaki Hara). ---------------------------------------- Bug #21153: ::Foo ||= p 1 should parse https://bugs.ruby-lang.org/issues/21153 * Author: qnighy (Masaki Hara) * Status: Open * ruby -v: ruby 3.5.0dev (2025-02-22T15:11:40Z master fd882fb681) +PRISM [x86_64-linux] * Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN ---------------------------------------- There is an inconsistency between how `Foo` and `::Foo` are handled: ```console % ./miniruby --parser=parse.y -e "Foo ||= p 1" 1 % ./miniruby --parser=parse.y -e "::Foo ||= p 1" -e:1: syntax error, unexpected integer literal, expecting 'do' or '{' or '(' ::Foo ||= p 1 ./miniruby: compile error (SyntaxError) ``` Note that `Object::Foo` also parses. Prism successfully parses both, which is what I expect. ```console % ./miniruby --parser=prism -e "Foo ||= p 1" 1 % ./miniruby --parser=prism -e "::Foo ||= p 1" 1 ``` To fix this, you should probably handle all tOP_ASGNs in the op_asgn rule. -- https://bugs.ruby-lang.org/

3 2