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
Gem.loaded_specs can sometimes be effected by issues similar to Capybara, where Ruby is not booted with rubygems enabled, but the gem can be require'd in and available. Therefore, as a fallback, it would be good to also check for the existence of the version number
defined by the library itself, instead of only accessing
it via Gem.loaded_specs.
It may be good to introduce this first to the api/sdk and then to the instrumentations to reduce the surface of the change
The text was updated successfully, but these errors were encountered:
Gem.loaded_specs
can sometimes be effected by issues similar to Capybara, where Ruby is not booted with rubygems enabled, but the gem can berequire
'd in and available. Therefore, as a fallback, it would be good to also check for the existence of the version numberdefined by the library itself, instead of only accessing
it via
Gem.loaded_specs
.It may be good to introduce this first to the api/sdk and then to the instrumentations to reduce the surface of the change
The text was updated successfully, but these errors were encountered: