Skip to content

Conversation

@ffranr
Copy link
Contributor

@ffranr ffranr commented Jan 9, 2026

Related (but dont close yet): #1911

Summary

  • Add retry logic to AssertAddrCreated to handle race conditions when querying addresses
  • Simplify context handling in full value send test

ffranr added 2 commits January 9, 2026 16:14
Remove the shared timeout context previously passed from the parent
test. The context was only used for NewAddr RPC calls, which do not
require explicit timeout handling as the test harness already enforces
test-level timeouts.

Simplify the function signature by removing the context parameter and
create Background contexts locally at each call site as needed.
Replace direct QueryAddrs calls with retry-enabled logic to ensure the
target address is found within the list. Prevents flakiness in test
cases where the address list might not be immediately updated.
@gemini-code-assist
Copy link

Summary of Changes

Hello @ffranr, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request aims to improve the reliability of integration tests, specifically addressing flakiness in the full value send test. It resolves timing-related issues by implementing a robust retry mechanism for address lookups and streamlines context usage within the test suite for better maintainability.

Highlights

  • Flakiness Fix: Introduced retry logic in AssertAddrCreated to handle potential race conditions when querying for newly created addresses, ensuring test stability.
  • Context Handling Simplification: Refactored context management in the full value send test by removing a global context with timeout and instead using context.Background() for individual RPC calls, leading to cleaner code.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@ffranr ffranr moved this from 🆕 New to 👀 In review in Taproot-Assets Project Board Jan 9, 2026
Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request aims to fix flakiness in the full value send integration test. It achieves this by adding retry logic when querying for a newly created address, which is a solid improvement. It also simplifies context handling in the test by removing a broad timeout. My review focuses on this context handling change, suggesting the re-introduction of scoped timeouts for RPC calls to ensure test robustness against hangs.

@coveralls
Copy link

Pull Request Test Coverage Report for Build 20858210230

Details

  • 11 of 14 (78.57%) changed or added relevant lines in 1 file are covered.
  • 80 unchanged lines in 17 files lost coverage.
  • Overall coverage decreased (-0.02%) to 56.96%

Changes Missing Coverage Covered Lines Changed/Added Lines %
itest/assertions.go 11 14 78.57%
Files with Coverage Reduction New Missed Lines %
itest/assertions.go 1 87.27%
asset/group_key.go 2 72.15%
commitment/tap.go 2 85.42%
fn/iter.go 2 62.07%
mssmt/compacted_tree.go 2 77.65%
tapdb/addrs.go 2 76.56%
proof/verifier.go 3 85.57%
tapgarden/planter.go 3 80.4%
asset/asset.go 4 80.7%
rpcserver.go 4 61.52%
Totals Coverage Status
Change from base Build 20856540500: -0.02%
Covered Lines: 65556
Relevant Lines: 115092

💛 - Coveralls

@ffranr ffranr requested review from GeorgeTsagk and jtobin January 11, 2026 13:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Status: 👀 In review

Development

Successfully merging this pull request may close these issues.

3 participants