Skip to content

fix: retry Discussions GraphQL calls once on transient network failure - #592

Open
essentialbit wants to merge 2 commits into
mainfrom
fix/gh-discussions-graphql-retry-transient-failure
Open

fix: retry Discussions GraphQL calls once on transient network failure#592
essentialbit wants to merge 2 commits into
mainfrom
fix/gh-discussions-graphql-retry-transient-failure

Conversation

@essentialbit

Copy link
Copy Markdown
Owner

Summary

Test plan

  • Verified via scratch mocked-`requests` script, 5 cases (transient-then-recover, persistent-failure-bounds-at-2-attempts, legitimate-success-no-spurious-retry, etc.), all pass — script deleted after.

🤖 Generated with Claude Code

_get_discussions() and _post_discussion_comment() call requests.post()
directly against the GraphQL endpoint, bypassing _gh_get/_gh_post entirely
- so they were missed by the same transient-5xx retry fix already applied
to the REST helpers (_gh_get in PR #584, _gh_post/_gh_delete in PR #588).
Live-caught this cycle during a real GitHub partial outage (githubstatus.com
reporting "Partial System Outage") where a plain `gh issue view` GraphQL call
503'd. Same single-retry, 2s-delay pattern as the REST fixes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant