Fix notification flow by removing backwards dependency chain#571
Fix notification flow by removing backwards dependency chain#571danieldotnl merged 1 commit intomasterfrom
Conversation
Replace the 4-layer notify_scrape_exception() chain with a forward-only flow where the coordinator owns a _force_reauth flag and passes it to ContentRequestManager.get_content() at request time. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (8)
📝 WalkthroughWalkthroughThe PR replaces a backwards Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~22 minutes Possibly related PRs
Poem
✨ Finishing Touches
🧪 Generate unit tests (beta)
📝 Coding Plan
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment Tip CodeRabbit can approve the review once all CodeRabbit's comments are resolved.Enable the |
Summary
notify_scrape_exception()backwards chain (Entity → Coordinator → ContentRequestManager → HttpSession → FormAuthenticator) with a forward-only flow_force_reauthflag and passes it forward viaget_content(force_reauth=...)at request timeinvalidate()on FormAuthenticator,invalidate_auth()on HttpSession,request_reauth()on CoordinatorTest plan
pytest tests/)request_reauth()→force_reauth=True→invalidate_auth()called → flag resetnotify_scrape_exceptionremain in source codeCloses #553
🤖 Generated with Claude Code
Summary by CodeRabbit