[Bug 284699] www/gitlab migration fails on gitlab-ce-17.8.1_2 due to concurrent-ruby change in v1.3.5

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=284699

            Bug ID: 284699
           Summary: www/gitlab migration fails on gitlab-ce-17.8.1_2 due
                    to concurrent-ruby change in v1.3.5
           Product: Ports & Packages
           Version: Latest
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: mfechner@FreeBSD.org
          Reporter: freebsd@gbtechlab.com
             Flags: maintainer-feedback?(mfechner@FreeBSD.org)
          Assignee: mfechner@FreeBSD.org

I am getting this error after removing Gemfile.lock and running migrations:

rake aborted!
NameError: uninitialized constant ActiveSupport::LoggerThreadSafeLevel::Logger
(NameError)

    Logger::Severity.constants.each do |severity|
          ^^^^^^^^^^
<internal:/s/usr/local/lib/ruby/site_ruby/3.2/rubygems/core_ext/kernel_require.rb>:37:in
`require'
<internal:/s/usr/local/lib/ruby/site_ruby/3.2/rubygems/core_ext/kernel_require.rb>:37:in
`require'
<internal:/s/usr/local/lib/ruby/site_ruby/3.2/rubygems/core_ext/kernel_require.rb>:37:in
`require'
<internal:/s/usr/local/lib/ruby/site_ruby/3.2/rubygems/core_ext/kernel_require.rb>:37:in
`require'
<internal:/s/usr/local/lib/ruby/site_ruby/3.2/rubygems/core_ext/kernel_require.rb>:37:in
`require'
<internal:/s/usr/local/lib/ruby/site_ruby/3.2/rubygems/core_ext/kernel_require.rb>:37:in
`require'
<internal:/s/usr/local/lib/ruby/site_ruby/3.2/rubygems/core_ext/kernel_require.rb>:37:in
`require'
<internal:/s/usr/local/lib/ruby/site_ruby/3.2/rubygems/core_ext/kernel_require.rb>:37:in
`require'
<internal:/s/usr/local/lib/ruby/site_ruby/3.2/rubygems/core_ext/kernel_require.rb>:37:in
`require'
<internal:/s/usr/local/lib/ruby/site_ruby/3.2/rubygems/core_ext/kernel_require.rb>:37:in
`require'
/s/usr/local/www/gitlab/config/application.rb:6:in `<main>'
<internal:/s/usr/local/lib/ruby/site_ruby/3.2/rubygems/core_ext/kernel_require.rb>:37:in
`require'
<internal:/s/usr/local/lib/ruby/site_ruby/3.2/rubygems/core_ext/kernel_require.rb>:37:in
`require'
/s/usr/local/www/gitlab/Rakefile:9:in `<main>'
(See full trace by running task with --trace)


I believe it may be related to
https://stackoverflow.com/questions/79360526/uninitialized-constant-activesupportloggerthreadsafelevellogger-nameerror

The SO thread suggests pegging concurrent-ruby at 1.3.4

If I modify Gemfile.lock concurrent-ruby version to 1.3.4 after installing the
1.3.4 package, migration does NOT report an error, and migrations show as:

main: == [advisory_lock_connection] object_id: 48960, pg_backend_pid: 9136
main: == [advisory_lock_connection] object_id: 48960, pg_backend_pid: 9136

-- 
You are receiving this mail because:
You are the assignee for the bug.