ruby / error_highlight

The gem enhances Exception#message by adding a short explanation where the exception is raised
MIT License
150 stars 23 forks source link

Bundle install hangs #23

Closed kleinjm closed 1 year ago

kleinjm commented 2 years ago

I'm not sure what changed in my app but I'm on Rails 6.1.5 and Ruby 3.2.0. When I try to bundle install, the command hangs with no output. I see the following if I run in verbose debugging mode.

 bundle install
:   0: Starting resolution (2022-04-26 14:33:18 -0600)
:   0: User-requested dependencies: [#<Gem::Resolver::DependencyRequest:0x000000010e37a8e8 @dependency=<Gem::Dependency type=:runtime name="error_highlight" requirements="= 0.3.0">, @requester=nil>, #<Gem::Resolver::DependencyRequest:0x000000010e37a898 @dependency=<Gem::Dependency type=:runtime name="did_you_mean" requirements="= 1.6.1">, @requester=nil>, #<Gem::Resolver::DependencyRequest:0x000000010e37a870 @dependency=<Gem::Dependency type=:runtime name="bundler" requirements="= 2.3.9">, @requester=nil>]
Resolving dependencies...:   0: Creating possibility state for error_highlight (= 0.3.0) (1 remaining)
:   1: Attempting to activate [error_highlight-0.3.0]
:   1: Activated error_highlight at [error_highlight-0.3.0]
:   1: Requiring nested dependencies ()
:   1: Creating possibility state for did_you_mean (= 1.6.1) (1 remaining)
:   2: Attempting to activate [did_you_mean-1.6.1]
:   2: Activated did_you_mean at [did_you_mean-1.6.1]
:   2: Requiring nested dependencies ()
:   2: Creating possibility state for bundler (= 2.3.9) (1 remaining)
:   3: Attempting to activate [bundler-2.3.9]
:   3: Activated bundler at [bundler-2.3.9]
:   3: Requiring nested dependencies ()

:   0: Finished resolution (3 steps) (Took 0.006771 seconds) (2022-04-26 14:33:18 -0600)
:   0: Unactivated:
:   0: Activated: error_highlight, did_you_mean, bundler

I'm not completely sure what this means but it seems related to this gem. Any advice would be appreciated. Thanks!

mame commented 1 year ago

Sorry I haven't responded in so long! But I think this is a bundler issue. Could you please report it to https://github.com/rubygems/rubygems/ ?