graph: fix zombie chan pruning
Change Description
Fixes #10223
This PR fixes the issue where channels with no edge policies escape pruning even though they have been stale for a while.
The fix only affects native SQL backend see why.
In the PR, we modify the SQL query to return channels without an edge policy, and then we check the timestamp of the block that includes the channel's funding transaction to estimate its age and determine if it should be pruned.
Steps to Test
cd graph && go test -run TestIsZombieByAge
cd graph/db && go test -tags test_db_sqlite -run TestChanUpdatesInHorizonWithNoPolicies
Summary of Changes
Hello @Abdulkbk, I'm Gemini Code Assist[^1]! 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 resolves an issue where Lightning Network channels that never received an edge policy update were not being properly pruned as 'zombie' channels. The solution introduces a mechanism to determine the staleness of such channels by examining the timestamp of their funding block. This ensures that all inactive channels, regardless of their policy update status, are correctly identified and removed from the graph, leading to a more accurate and efficient network graph representation, specifically for the native SQL backend.
Highlights
-
Zombie Channel Pruning Logic: Introduced a new function,
IsZombieByAge, to determine if a channel without any edge policies should be considered a 'zombie' based on the timestamp of its funding transaction's block. This addresses a specific issue where such channels were escaping the pruning process. -
Integration into Pruning Process: The
pruneZombieChansmethod has been updated to utilize the newIsZombieByAgelogic for channels where both edge policies are absent. This ensures that stale channels lacking policy updates are now correctly identified and added to the list of channels to be pruned. -
SQL Query Modification: The
ChanUpdatesInHorizonSQL query was modified to explicitly include channels that have no associated edge policies (i.e., bothlast_updatetimestamps are NULL). This change is crucial for the SQL backend to correctly retrieve these channels for age-based zombie detection and pruning. -
New Test Cases: Added
TestIsZombieByAgetograph/builder_test.goto validate the new age-based zombie detection logic, andTestChanUpdatesInHorizonWithNoPoliciestograph/db/graph_test.goto ensure the SQL backend correctly returns channels without policies within various time horizons.
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 :thumbsup: and :thumbsdown: 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.
[^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.
@ziggie1984: review reminder @abdulkbk, remember to re-request review from reviewers when ready
Thanks for taking a look @MPins 🙏