Skip to content

Conversation

@Bubballoo3
Copy link
Contributor

Fixes #4147 by adding the ostruct, bigdecimal, and mutex_m gems to the Gemfile. Also silences two duplicated key warnings by resolving the duplication.

Comment on lines 54 to 56
gem 'ostruct'
gem 'bigdecimal'
gem 'mutex_m'
Copy link
Contributor

Choose a reason for hiding this comment

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

Are you still seeing these? I think seeing ostruct is new, but activesupport already has these in rails 7.1, you can see them in your vendor/bundle.

https://github.com/rails/rails/blob/ffcbf6f205363f8c2fb3e9834bc86690dd59f1cb/activesupport/activesupport.gemspec#L44-L45

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I wasn't seeing any them during tests, but I figured it was better to be overly cautious in case they were originating somewhere that wasn't being hit. I couldn't find a good way to scan the whole dashboard for depreciation warnings. I will look into them though and see if they were part of the 7.1 upgrade

@Bubballoo3
Copy link
Contributor Author

Not sure how I missed it before, but I also added abbrev which has been giving a notice toward the end of bin/setup. I think this is ready for a final review now.

Comment on lines +54 to +55
gem 'ostruct'
gem 'abbrev'
Copy link
Contributor

Choose a reason for hiding this comment

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

We should put a comment here because these are not direct dependencies but actual like rubygems or bundler dependencies that we're trying to silence.

Which is to say we can get rid of them eventually and/or just not include them now and let bundler/rubygems/whatever update itself on the systems.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

or just not include them now and let bundler/rubygems/whatever update itself on the systems.

Would you rather do that? I was thinking that we were including these in lieu of any upgrades for the moment

Copy link
Contributor

Choose a reason for hiding this comment

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

Would you rather do that? I was thinking that we were including these in lieu of any upgrades for the moment

I could go either way.

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

Projects

Status: Awaiting Review

Development

Successfully merging this pull request may close these issues.

Gem/Ruby warnings on Dashboard start (4.0.0)

4 participants