Skip to content

Conversation

GeorgeTsagk
Copy link
Member

Description

Routine golang bump, in preparation for other PRs that depend on latest LND.

LND recently updated to v1.24.6: lightningnetwork/lnd#10167

These tapd PRs bump the LND dependency, and will require this repo to update its golang version:

Govet: new printf rule

With go v1.24.6 a new govet rule was added that disallows calling printf with non-constant format strings. Thankfully we didn't have many occurrences of this in tapd. The first commit takes care of any call sites that relied on this behavior.

In preparation to the next commit which will bump the golang version we
want to avoid calling printf with non-constant format strings. This
needs to be done as the govet will include a new rule that prohibits
exactly that -- calling into printf with non-constant format strings.
@GeorgeTsagk GeorgeTsagk self-assigned this Sep 24, 2025
Copy link

Summary of Changes

Hello @GeorgeTsagk, 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 performs a routine update of the Go programming language version to v1.24.6 across the repository. This update is crucial for maintaining compatibility with the latest LND version and is a prerequisite for upcoming feature development. It also includes a minor code adjustment to adhere to a new govet rule introduced in Go 1.24.6, ensuring code quality and preventing potential issues related to format string usage.

Highlights

  • Go Version Bump: The Go programming language version has been updated across the project to v1.24.6, affecting various Dockerfiles, Makefiles, and go.mod files.
  • Govet Rule Compliance: Adjustments were made to comply with a new govet rule introduced in Go 1.24.6, which disallows calling printf with non-constant format strings. Specifically, a t.Fatalf call was changed to t.Fatal in a test utility.
  • Prerequisite for LND Updates: This Go version bump is a necessary preparatory step for subsequent pull requests that will update the LND dependency, as LND itself recently moved to Go 1.24.6.
Ignored Files
  • Ignored by pattern: .github/workflows/** (2)
    • .github/workflows/main.yaml
    • .github/workflows/release.yaml
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.

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 correctly bumps the Go version to v1.24.6 across various configuration files, including Dockerfiles and go.mod files. The changes are consistent and align with the goal of keeping the project's dependencies up-to-date. The modification in internal/test/copy.go to use t.Fatal instead of t.Fatalf with a variable is a proper fix for the new govet rule introduced in Go 1.24. The changes are well-contained and address the stated purpose of the pull request effectively.

Copy link
Contributor

@darioAnongba darioAnongba left a comment

Choose a reason for hiding this comment

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

LGTM

@coveralls
Copy link

Pull Request Test Coverage Report for Build 17979473000

Details

  • 0 of 1 (0.0%) changed or added relevant line in 1 file are covered.
  • 1189 unchanged lines in 40 files lost coverage.
  • Overall coverage decreased (-1.0%) to 56.268%

Changes Missing Coverage Covered Lines Changed/Added Lines %
internal/test/copy.go 0 1 0.0%
Files with Coverage Reduction New Missed Lines %
asset/asset.go 2 80.3%
fn/func.go 2 58.82%
fn/iter.go 2 62.07%
rfqmsg/records.go 2 70.8%
tapdb/migrations.go 2 76.06%
tapdb/universe_federation.go 2 88.55%
itest/multisig.go 3 97.94%
proof/courier.go 3 79.53%
tapdb/sqlc/db_custom.go 3 70.83%
universe/archive.go 3 78.49%
Totals Coverage Status
Change from base Build 17814811986: -1.0%
Covered Lines: 63311
Relevant Lines: 112517

💛 - Coveralls

@ffranr ffranr added this pull request to the merge queue Sep 24, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Sep 24, 2025
@ffranr ffranr added this pull request to the merge queue Sep 24, 2025
Merged via the queue into main with commit 07fc1df Sep 24, 2025
18 of 19 checks passed
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.

4 participants