Splunk Dev

Ruby gem dependency: i18n limited to v1.1.0 ?

dhempy
New Member

I updated my Ruby app to use signalfx 3.1.0 (from 2.1.0)
 
I was surprised to see this gem downgrade when I bundled:

  Installing i18n 1.1.0 (was 1.8.5)

That's rewinding the i8n gem about two years. 

Looking at signalfx.gemspec, it is locking it in to exactly that version:

  spec.add_dependency "i18n", "= 1.1.0"

Is there a reason for that? It seems an optimistic version such as ">= 1.1.0" would be safe and not so restrictive, and would match most of the other dependencies in the gemspec.

While this is not a blocker for our app, please consider putting in a feature request to relax the i18n version dependency.

Tags (1)
0 Karma

dhempy
New Member

Similarly, I notice the signalfx gem restricts activesupport to <6

Activesupport 6.0 was released over a year ago. This is more likely to be a blocker for signalfx clients moving ahead. 

0 Karma
Get Updates on the Splunk Community!

Splunk + ThousandEyes: Correlate frontend, app, and network data to troubleshoot ...

 Are you tired of troubleshooting delays caused by siloed frontend, application, and network data? We've got a ...

Splunk Observability for AI

Don’t miss out on an exciting Tech Talk on Splunk Observability for AI!Discover how Splunk’s agentic AI ...

🔐 Trust at Every Hop: How mTLS in Splunk Enterprise 10.0 Makes Security Simpler

From Idea to Implementation: Why Splunk Built mTLS into Splunk Enterprise 10.0  mTLS wasn’t just a checkbox ...