This content originally appeared on Phil Nash and was authored by Phil Nash
Last week I was blown away by the response to a problem I was experiencing from maintainers of two of the larger open source projects in the Ruby world. And not just your average large Ruby projects, but implementations of Ruby itself.
I had trouble running the tests for envyable, my gem to manage environment variables in your projects, on Rubinius on TravisCI. After installing the version of Rubinius locally, I couldn't reproduce the issue. So I tweeted.
<blockquote class="twitter-tweet" data-lang="en"><p lang="en" dir="ltr">Anyone seen this error on <a href="https://twitter.com/travisci">@travisci</a> with <a href="https://twitter.com/codeclimate">@codeclimate</a> coverage on <a href="https://twitter.com/rubinius">@rubinius</a>? <a href="https://t.co/fydiHoElCa">https://t.co/fydiHoElCa</a>. I can't repro locally and am confused.</p>— Phil Nash (@philnash) <a href="https://twitter.com/philnash/status/770542433901969409">August 30, 2016</a></blockquote>
Not only did Brian Shirai, maintainer of Rubinius, reach out to suggest some ideas for how to fix it. He also forked the project and tried to get it working himself.
<blockquote class="twitter-tweet" data-conversation="none" data-lang="en"><p lang="en" dir="ltr"><a href="https://twitter.com/philnash">@philnash</a> you're using an ancient version 3.29. Ensure you're using Trusty distro and 'rbx' in .travis.yml <a href="https://twitter.com/travisci">@travisci</a> <a href="https://twitter.com/codeclimate">@codeclimate</a></p>— Rubinius (@rubinius) <a href="https://twitter.com/rubinius/status/770647800514093056">August 30, 2016</a></blockquote>
But that wasn't all. I followed his advice but eventually had to settle with moving Rubinius to the allowed failures list in my TravisCI config. I'm still working with the TravisCI support team to try to fix the issue. We're getting there as it turns out TravisCI was looking in the wrong place for the latest Rubinius binaries. That issue is fixed but I am now getting timeouts for my builds.
This affected JRuby too and when I mentioned that on Twitter, Charles Nutter from the JRuby core team also offered to help out if it was a JRuby bug.
<blockquote class="twitter-tweet" data-lang="en"><p lang="en" dir="ltr"><a href="https://twitter.com/philnash">@philnash</a> <a href="https://twitter.com/travisci">@travisci</a> <a href="https://twitter.com/rubinius">@rubinius</a> That JRuby failure looks like a timeout installing the base gemset in rvm. Happy to help if it is a JRuby bug.</p>— Charles Nutter (@headius) <a href="https://twitter.com/headius/status/770792465955557376">August 31, 2016</a></blockquote>
My project is not the biggest or the most important Ruby project. Not by a long way. The issues are also likely not with Rubinius or JRuby. But the willingness for Brian and Charles to reach out to help was amazing. I'm sure they are very busy people and just the response was appreciated.
Thank you
So thank you Brian and thank you Charles. Thank you for your work in the Ruby community and thank you specifically for offering your help to me. Acts like this maintain my belief in the power and the strength of the Ruby community.
This content originally appeared on Phil Nash and was authored by Phil Nash
Phil Nash | Sciencx (2016-09-05T00:00:00+00:00) A community offers to help. Retrieved from https://www.scien.cx/2016/09/05/a-community-offers-to-help-2/
Please log in to upload a file.
There are no updates yet.
Click the Upload button above to add an update.