-
Notifications
You must be signed in to change notification settings - Fork 37
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
SocketError with MM 3.0.14 and MM-LR 3.1.0 #32
Comments
Any reason you're still on Middleman 3.0? |
No reason in particular, but I'll bump everything this evening and report back. |
Same error after bumping. New Gemfile.lock:
|
I think I've fixed this in #48 via commit bhollis@9951654 |
I'm doing some issue-gardening 🌿🌷🌾 and came across this issue. Sorry that this has lingered for quite a while! I'd suggest either closing this issue or submitting a PR with an implementation or at least a failing test. (this repo is maintained by a few people contributing their free time, unfortunately we can't solve every issue on our own, so help from others is needed for some of the more exotic issues that crops up) |
I apologize if this has been addressed somewhere else, but I've been having this error for a while and have been just working around it. More frustrating is that it is occurring on only one of two environments that are essentially the same. Posting here instead of the forums just in case, but will cross-post there.
Whenever I activate Middleman-Livereload, I always recieve the following error, even with fresh gemsets:
In the terminal:
Gemfile:
Any help is really welcome - I have gone down a ton of paths to try and figure this out. I can also provide any additional details.
The text was updated successfully, but these errors were encountered: