You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
v1.1.6 seems to have introduced a new code usage of the etc gem, but does not properly register it as a gem dependency, resulting in a runtime LoadError while attempting to install v1.1.6 via bundler.
FYI: Our gem depends on concurrent-ruby indirectly.
Error trace:
14: from /usr/lib/ruby/gems/2.5.0/gems/azure_mgmt_network-0.17.4/lib/azure_mgmt_network.rb:5:in `<top (required)>'
13: from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require'
12: from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require'
11: from /usr/lib/ruby/gems/2.5.0/gems/azure_mgmt_network-0.17.4/lib/2018-08-01/generated/azure_mgmt_network.rb:17:in `<top (required)>'
10: from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require'
9: from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require'
8: from /usr/lib/ruby/gems/2.5.0/gems/concurrent-ruby-1.1.6/lib/concurrent-ruby/concurrent.rb:4:in `<top (required)>'
7: from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require'
6: from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require'
5: from /usr/lib/ruby/gems/2.5.0/gems/concurrent-ruby-1.1.6/lib/concurrent-ruby/concurrent/configuration.rb:9:in `<top (required)>'
4: from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require'
3: from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require'
2: from /usr/lib/ruby/gems/2.5.0/gems/concurrent-ruby-1.1.6/lib/concurrent-ruby/concurrent/utility/processor_counter.rb:1:in `<top (required)>'
1: from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require'
/usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require': cannot load such file -- etc (LoadError)
After further investigation, it seems that the root cause of this issue is alpine linux issue #9216, where the ruby-etc package was excluded from the alpine linux v3.8 image despite the fact that etc has been a standard gem since ruby v2.5.0. Apparently, this issue caused problems for multiple ruby-based systems when built on top of alpine v3.8.
v1.1.6 seems to have introduced a new code usage of the
etc
gem, but does not properly register it as a gem dependency, resulting in a runtime LoadError while attempting to install v1.1.6 viabundler
.FYI: Our gem depends on concurrent-ruby indirectly.
Error trace:
Env info
concurrent-ruby
version: 1.1.6 (1.1.5 was fine)concurrent-ruby-ext
installed: unknownconcurrent-ruby-edge
used: unknowncat /etc/os-release
:NAME="Alpine Linux"
ID=alpine
VERSION_ID=3.8.1
PRETTY_NAME="Alpine Linux v3.8"
HOME_URL="http://alpinelinux.org"
BUG_REPORT_URL="http://bugs.alpinelinux.org"
The text was updated successfully, but these errors were encountered: