Skip to content

Rubystats gem causes name conflict that won't allow Rails application to start properly #706

Open
@tferrerm

Description

@tferrerm

Describe the bug
I'm opening this issue here because the rubystats gem has no clear way of reporting issues :(
The gem rubystats causes an error that completely breaks my particular Rails application because it has a module named Beta.

This is the error:

Failure/Error: module Beta

     TypeError:
       Beta is not a module
       some-directory/vendor/bundle/ruby/3.2.0/gems/rubystats-0.3.0/lib/rubystats.rb:37: previous definition of Beta was here

To Reproduce
Create a Rails application with a module named Beta and add split >= 4.0 to the Gemfile.

Expected behavior
The application should work just fine; a subdependency shouldn't break the entire application, which worked just fine using split == 3.4.1.

Additional context
As a workaround, version 3.4.1 of this gem can be used.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions