Fix Twitter 100% CPU (#335) #347
Closed
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
|
I'm not sure that's the right fix: the sleep certainly prevents it from using all of your CPU, but it looping constantly means there's something else going wrong. It's probably because the user-stream API has pretty much been shutdown by Twitter. I guess we can remove it from Beehive altogether now. |
|
Posting still works! see #335 |
|
Oh sorry, I didn't mean to remove the Twitter hive entirely. I only meant to remove the user stream from the code. |
|
Replaced by #348. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This fixes the 100% CPU problem of #335.