Catch an IOError that happens on Ruby 2.0 #52

Merged
johnkchow merged 1 commits from master into master 2014-07-18 11:32:13 +00:00
johnkchow commented 2014-03-01 21:17:49 +00:00 (Migrated from github.com)

Would get a #<IOError: closed stream> error when running in my MRI 2.0 environment (works fine on 1.9.3). Either there's a Ruby change in the net/http works or something else in the guard-livereload server (I'm using an old 1.0.3 here), but this looks to work for me.

Would get a #<IOError: closed stream> error when running in my MRI 2.0 environment (works fine on 1.9.3). Either there's a Ruby change in the `net/http` works or something else in the `guard-livereload` server (I'm using an old 1.0.3 here), but this looks to work for me.
johnkchow commented 2014-07-18 00:03:18 +00:00 (Migrated from github.com)

@johnbintz The failures on Travis looks like it's a config error and not an actual failure, I was wondering if you could possibly accept this PR?

@johnbintz The failures on Travis looks like it's a config error and not an actual failure, I was wondering if you could possibly accept this PR?
johnkchow commented 2014-07-18 13:31:41 +00:00 (Migrated from github.com)

@johnbintz Thanks a lot man!

@johnbintz Thanks a lot man!
Sign in to join this conversation.
No reviewers
No Label
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: github-migration/rack-livereload#52
No description provided.