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
/home/runner/runner/agent/_work/..vendor/bundle/ruby/3.2.0/gems/property_sets-3.13.0/lib/property_sets/active_record_extension.rb:62: warning: method redefined; discarding old ssl_enabled?
/home/runner/runner/agent/_work/..vendor/bundle/ruby/3.2.0/gems/property_sets-3.13.0/lib/property_sets/active_record_extension.rb:62: warning: previous definition of ssl_enabled? was here
/home/runner/runner/agent/_work/..vendor/bundle/ruby/3.2.0/gems/property_sets-3.13.0/lib/property_sets/active_record_extension.rb:69: warning: method redefined; discarding old ssl_enabled
/home/runner/runner/agent/_work/..vendor/bundle/ruby/3.2.0/gems/property_sets-3.13.0/lib/property_sets/active_record_extension.rb:69: warning: previous definition of ssl_enabled was here
/home/runner/runner/agent/_work/..vendor/bundle/ruby/3.2.0/gems/property_sets-3.13.0/lib/property_sets/active_record_extension.rb:75: warning: method redefined; discarding old ssl_enabled=
/home/runner/runner/agent/_work/..vendor/bundle/ruby/3.2.0/gems/property_sets-3.13.0/lib/property_sets/active_record_extension.rb:75: warning: previous definition of ssl_enabled= was here
... <many many more>
Looking at some docs, it seems like is not a big deal, but annoying. Can we do something about it?
Method Redefined1
This warning helps us find when a method is overridden. This is not necessarily a bad thing, most of the time this is fine and it’s needed for some gems to be able to do their job. In general, this warning serves an informative purpose and is not necessarily something that needs to be fixed, but can help us find monkey patches, for example.
Whats the best approach to avoid these warnings?
Looking at some docs, it seems like is not a big deal, but annoying. Can we do something about it?
Footnotes
https://www.fastruby.io/blog/exploring-ruby-warnings.html ↩
The text was updated successfully, but these errors were encountered: