-
Notifications
You must be signed in to change notification settings - Fork 74
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
dont monkeypatch String#snakecase #101
Comments
we started seeing kitchen-ec2 launch failures after this was released with nori 2.7.1. not sure where the best place to report this is but figured I would start here. pinning nori 2.7.0 stops the errors. |
@samrecord can you provide a stacktrace, or the involved gems/versions? |
@pcai here's the bundle output from a failed build: 16:44:55 Fetching gem metadata from https://rubygems.org/........ |
I noticed you're using I believe winrm v2.3.9 + nori v2.7.1 should work together. Apologies for the trouble - with hindsight this probably needed to be a more gradual deprecation than a minor point release. |
I suspect you're right since the first thing kitchen-ec2 tries to do once the instance is ready is to connect with winrm, and that's exactly when we see the error. We'll try with winrm 2.3.9 and see if that helps. Thanks. |
Confirmed that we no longer see the error with nori 2.7.1 and winrm 2.3.9. Thanks again. |
While savon no longer monkeypatches, nori still does.
related issue: savonrb/savon#984
The text was updated successfully, but these errors were encountered: