fix(pipeline): forward pinned parameters in thin-source retry logic#795
Open
bastitva0-blip wants to merge 4 commits into
Open
fix(pipeline): forward pinned parameters in thin-source retry logic#795bastitva0-blip wants to merge 4 commits into
bastitva0-blip wants to merge 4 commits into
Conversation
Contributor
2 tasks
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 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.
Summary
This PR fixes a bug in
_retry_thin_sourceswheresubreddits,tiktok_hashtags,tiktok_creators, andig_creatorswere silently dropped during Phase 2b retry attempts. When these targeted sources returned low-volume data (<3 items) in Phase 1, the fallback retry fired without the user's explicit constraints—falling back to broad public discovery instead of honoring pinned--subreddits,--tiktok-creators, or--ig-creatorsflags.Changes
skills/last30days/scripts/lib/pipeline.py_retry_thin_sourcesfunction signature to acceptsubreddits,tiktok_hashtags,tiktok_creators, andig_creators.run()to correctly pass all four parameters down into_retry_thin_sources._retry_one_sourceto forward these parameters cleanly into the inner_retrieve_streamcall, mirroring the exact signature used in Phase 1.Why This Matters
Unlike strict 5xx network error retries, the thin-source retry logic fires under regular operational conditions on lower-volume topics. Because it fails silently without throwing an exception, users simply receive weak or misattributed generic fallback results with no warnings. This is particularly problematic for niche brand monitoring where dedicated subreddits naturally have low volume and depend heavily on accurate retries.
Note:
trustpilotremains safely isolated from this path via the existing_skipset (line 1159).Testing
uv run python -m pytest -q --tb=shortRelated Issues
bug,pipeline,social-sources,retry-logic,data-integrity