Skip to content

Conversation

@casperisfine
Copy link

It is now a gem, and since spring load before bundler if you have multiple set versions installed, you might load the wrong one causing already defined constant warnings.

Initially wrongly reported as a bundler issue: ruby/rubygems#5127

Reported to be my @Bowman-42

# Make sure to close other clients otherwise their graceful termination
# will be impossible due to reference from this fork.
@clients.select { |c| c != client }.each(&:close)
@clients.each_key { |c| c.clonse if c != client }
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
@clients.each_key { |c| c.clonse if c != client }
@clients.each_key { |c| c.close if c != client }

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Woops, thank you :)

It is now a gem, and since spring load before bundler
if you have multiple `set` versions installed, you might
load the wrong one causing already defined constant warnings.
@casperisfine
Copy link
Author

cc @rafaelfranca, this isn't a big bug as it's still very rare to have set installed as a gem, but would be nice to have it released.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants