Fix for bug #285 and possibly #301 #369
Open
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
uvzz
changed the title
added 9 commits
February 12, 2024 09:59
…ollowers list to load
…ollowers list to load
…ollowers list to load
…ollowers list to load
…ollowers list to load
…ollowers list to load
…ollowers list to load
…ollowers list to load
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.
Description
the bot sometimes detects reels as carousels with 0 items and stops responding for hours until it crashes
refer to:
#285 (comment)
#301 (comment)
Fixes # (issue)
In a case where a carousel is detected with 0 items - change the media type detected to Reel
How Has This Been Tested?
The test was running for several sessions. A carousel with 0 items was detected and the bot did not crash.
Test Configuration:
Checklist:
Needs testing in more configurations?