This repository has been archived by the owner on Dec 1, 2017. It is now read-only.
[#448] Early return if no websockets #449
Merged
+2
−0
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@humphd would you consider merging this? |
|
#396 |
|
Oops, right.. wrong bug. |
k88hudson
changed the title
|
If we want to land this for mozfest and fix properly later, that's cool with me. @alicoding? |
|
Since this will help by at least not blocking the whole Webmaker.app front end I think we should land this and then do a real fix later on. |
alicoding
added a commit
that referenced
this pull request
Oct 24, 2014
[#448] Early return if no websockets
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I know this isn't a complete solution to what to do if no websockets exist, but it will prevent makedrive from throwing as long as the
connectfunction isn't called and unblock us on #396