Fix GitHub OAuth Device Flow tests

[SayanthRock]

User description

Fix test assertion for the github device flow gateway tests to ensure proper type checking with nested exception hierarchy.

---

PR created automatically by Jules for task 15353266881948238193 started by @SayanthRock

---

CodeAnt-AI Description

Verify the nested network exception type in GitHub OAuth tests

What Changed

• GitHub OAuth device flow tests now confirm that the underlying network failure is an IOException, in addition to checking the user-facing error message and retry behavior

Impact

✅ Clearer coverage of network failure handling
✅ Fewer regressions in GitHub OAuth error reporting

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.

Summary by CodeRabbit

• Tests
  • Expanded coverage for persistent network failures during GitHub sign-in by verifying that the underlying error is correctly identified as an I/O issue.

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[codeant-ai]

🤖 CodeAnt AI — Review Status

Status	Commit	Started (UTC)	Finished (UTC)
✅ Reviewed your PR	eb624af	Jul 29, 2026 · 15:31	15:33

[codeant-ai]

---

Thanks for using CodeAnt! 🎉

We're free for open-source projects. if you're enjoying it, help us grow by sharing.

Share on X ·
Reddit ·
LinkedIn

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[coderabbitai]

📝 Walkthrough

Walkthrough

The persistent GitHub OAuth network failure test now verifies that the thrown GitHubNetworkException contains an underlying IOException in its nested cause chain.

Changes

OAuth network failure validation

Layer / File(s)	Summary
Nested exception cause assertion core-network/src/test/java/.../GitHubOAuthDeviceFlowGatewayTest.kt	The persistent network failure test now asserts that the deeper cause is an IOException.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Possibly related PRs

• Sayanthrock-Developer/Rock-Release-Hub#59: Adds the related persistent network-error test for postFormWithRetry.
• Sayanthrock-Developer/Rock-Release-Hub#63: Updates assertions around the same exception cause chain.
• Sayanthrock-Developer/Rock-Release-Hub#65: Validates the underlying IOException in the same failure path.

Suggested labels: size:XS

Suggested reviewers: copilot

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title matches the PR's actual change: a fix to GitHub OAuth Device Flow test assertions.

✨ Finishing Touches 💡 1

📝 Generate docstrings 💡

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix-tests-15353266881948238193

---

_{Comment @coderabbitai help to get the list of available commands.}

[ai-coding-guardrails]

Nice work! 😎

I didn't find anything of concern

Risk: 🟢 Low

Risk analysis

This PR modifies a single line in a test file to fix an assertion related to exception type checking. Since it only affects test code and does not introduce any functional or structural changes, all risk dimensions are scored as 0.

Think our bots are missing some context? Add custom requirements or guardrails in our management console