This repository was archived by the owner on Jul 26, 2023. It is now read-only.
BUGFIX: Removing infinite loops#4
Open
scotm wants to merge 1 commit into
Open
Conversation
…out it, it will loop forever and retrieve the previous request's data.
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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.
Facebook's thread_info.php now requires a timestamp in the headers. And it must be the same timestamp as the previous thread's last message.
Therefore, I'm adding the previous message's timestamp to the headers - without it, it will loop forever and only retrieve the previous request's data. This will mean it never terminates.
Additionally - I've added a breakpoint in the main loop. If "end_of_history" is in the payload, it terminates. For some reason, matching the string directly no longer works.