Closed pacoguzman closed 7 years ago
@pacoguzman Thanks for catching and working on this! I think we should maintain tests for old and new formats to be sure we don't unintentionally break on anyone. Then later on we can deprecate the old version and remove support in a major release when 1.0.0 is more ubiquitous in production.
Setting up Travis would be awesome!
@freerobby I'll try to setup travis-ci (as we're open source) should be easy to get up an running the two versions using a travis matrix
@pacoguzman Mind bumping nsq-cluster
to 2.1? I just updated it so it will support both NSQ < 1.0 and NSQ >= 1.0. With that change, tests pass for me locally with both NSQ 0.3.8 and NSQ 1.0.0.
Once that's done, this looks ready to merge! Thanks for your work here and for using nsq-ruby
!
Psyched to have Travis set up for this project too -- long overdue :)
I've bumped the nsq-cluster
dependency but I'm getting random timeout errors on Travis. Maybe we can review after merge it.
Thanks @pacoguzman!
You're welcome!
On Mon, Apr 17, 2017, 10:22 PM Brendan Schwartz notifications@github.com wrote:
Thanks @pacoguzman https://github.com/pacoguzman!
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/wistia/nsq-ruby/pull/38#issuecomment-294580882, or mute the thread https://github.com/notifications/unsubscribe-auth/AAAqrkhoYvhp55zPxWWw8AU275EH0KmJks5rw8oTgaJpZM4Mn9bX .
This PR implements a solution for https://github.com/wistia/nsq-ruby/issues/37
Notes: