Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dependencies causing frozen string literal issues #224

Open
wakemaster39 opened this issue Mar 20, 2020 · 0 comments
Open

Dependencies causing frozen string literal issues #224

wakemaster39 opened this issue Mar 20, 2020 · 0 comments

Comments

@wakemaster39
Copy link

I am running into an issue trying to use some sensu plugins with sensu-go due to the age of certain dependencies causing Check failed to run: can't modify frozen String to be the output of my checks.

The error and a possible work around can be found here: sensu-plugins/sensu-plugins-rabbitmq#86

The issue with this work around is with bonsai assests I need to go into every box that uses them, and modify the file for the check to work. Every time I upgrade an asset in the future, I need to redo that change.

Digging around, I found that the issue is related to mixlib-cli and the problem was fixed in version 1.7.1. The issue is that this version was never released to rubygems and as such isn't being found when packages are building. chef/mixlib-cli#57

I am not a ruby programmer, so my knowledge of the ecosystem is minimal, but I see that the minimal dependency for mixlib-cli is set at ~> 1.5 . Based on the mixlib-cli ticket listed about, support for ruby 2.4 was added back to the package in version 2.0.3.

The issue there is that the current sensu-plugin supports ruby 2.3, which puts me in a world of hurt with no good way to solve the problem. With the deprecation of sensu 1.x, and with bonsai distributing sensu 2.4, is it possible to upgrade this package to have a new minimum supported version of ruby of 2.4 and upgrade the dependencies accordingly?

I do not know the impact or scale of the ask here, just trying to figure out how I can work through the problem given the current constraints.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant