Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bot/modules/nostr: convert to TS #627

Merged
merged 4 commits into from
Feb 18, 2025

Conversation

webwarrior-ws
Copy link
Contributor

@webwarrior-ws webwarrior-ws commented Jan 7, 2025

Convert bot/modules/nostr to TypeScript.
Specified "lib" property in tsconfig.json because otherwise TypeScript compiler complains about usage of Promise.any in bot/modules/nostr/index.ts:

Property 'any' does not exist on type 'PromiseConstructor'. Do you need to change your target library? Try changing the lib compiler option to 'es2021' or later.

Summary by CodeRabbit

Release Notes

  • New Features

    • Enhanced Nostr module with improved type safety and modern module syntax
    • Added dynamic relay management for Nostr connections
    • Introduced functions for encoding and decoding Nostr public keys
  • Improvements

    • Migrated codebase to TypeScript with ES module syntax
    • Improved error handling for environment variable configurations
    • Updated TypeScript configuration to support ES2021 features
  • Technical Updates

    • Refactored Nostr-related modules for better maintainability
    • Added type annotations across Nostr module functions
    • Removed deprecated configurations and functions related to Nostr keys and relays

Copy link
Member

@Catrya Catrya left a comment

Choose a reason for hiding this comment

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

Hi @webwarrior-ws when I type /nostr have an Error
Captura desde 2025-01-22 18-19-13

and when type /npub with a correct npub this the bot says:
⚠️ ERROR Not a valid NIP-19 (https://github.com/nostr-protocol/nips/blob/master/19.md) npub. Please check your input.

@webwarrior-ws
Copy link
Contributor Author

@Catrya take a look, I added a commit that should fix the error. Assuming NOSTR_SK env. var is hex-encoded. If not, tell me what format it is in.

bot/modules/nostr/index.ts Outdated Show resolved Hide resolved
bot/modules/nostr/index.ts Outdated Show resolved Hide resolved
@Catrya
Copy link
Member

Catrya commented Jan 24, 2025

Hi, @webwarrior-ws it keep getting the same 2 errors: with /nostr and /setnpub

Anyway, what do you think @grunch about removing the /setnpub part because in the end I think that was no longer working anyway (I'm not referring to the current error of not accepting npub, but to what it was intended to do, which was to notify the user through nostr if someone took their order, and I can't find the 20100 events that it should publish in the relays) Or maybe leave it and then evaluate whether to keep that feature and fix it?

Copy link

coderabbitai bot commented Jan 30, 2025

Walkthrough

The pull request introduces a comprehensive modernization of the Nostr module in the bot project. The changes primarily focus on transitioning from CommonJS to ES module syntax, adding TypeScript type annotations, and improving module structure. The modifications span across multiple files in the bot/modules/nostr/ directory, including updates to imports, function signatures, and module exports. The tsconfig.json was also updated to support the new module system and provide additional library support.

Changes

File Change Summary
bot/modules/nostr/commands.ts Migrated to ES module syntax, updated imports from nostr-tools, added TypeScript type annotations for function parameters
bot/modules/nostr/config.js Deleted file with legacy configuration management
bot/modules/nostr/config.ts New TypeScript file with Nostr key and relay management functions
bot/modules/nostr/events.ts Transitioned to ES module syntax, added type annotations for IOrder, improved error handling
bot/modules/nostr/index.ts Updated imports, added TypeScript type annotations for bot configuration and event handlers
bot/modules/nostr/lib.ts Migrated to ES module syntax, added TypeScript type annotations for decodeNpub and encodeNpub functions
tsconfig.json Added "lib":["ES2021", "DOM"] to compiler options

Poem

🐰 Hop, hop, modules anew!
TypeScript dancing, syntax true
From CommonJS to ES delight
Imports sparkle, types shine bright
A rabbit's code, modernly dressed 🌟

✨ Finishing Touches
  • 📝 Generate Docstrings (Beta)

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Convert bot/modules/nostr to TypeScript.
Specified "lib" property in tsconfig.json because otherwise
TypeScript compiler complains about usage of `Promise.any`
in bot/modules/nostr/index.ts:
```
Property 'any' does not exist on type 'PromiseConstructor'. Do you need to change your target library? Try changing the lib compiler option to 'es2021' or later.
```
Decode nostr secret key from environment variable using hex
encoding. Also replace requires with imports.
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 5

🔭 Outside diff range comments (2)
bot/modules/nostr/index.ts (1)

Line range hint 26-36: Improve error handling for event publishing

The Promise.any usage needs better error handling as it will reject if all publishes fail.

   OrderEvents.onOrderUpdated(async (order: IOrder) => {
     try {
       const event = await createOrderEvent(order);
       if (event) {
-        await Promise.any(Config.pool.publish(Config.getRelays(), event));
+        const relays = Config.getRelays();
+        if (relays.length === 0) {
+          throw new Error('No relays configured');
+        }
+        try {
+          await Promise.any(Config.pool.publish(relays, event));
+        } catch (publishError) {
+          throw new Error('Failed to publish to any relay: ' + publishError.message);
+        }
       }
       return event;
     } catch (err) {
-      logger.error(err);
+      logger.error('Failed to process order update:', err);
+      return undefined;
     }
   });
bot/modules/nostr/events.ts (1)

Line range hint 57-82: Add error handling and return type annotation.

The function should handle potential undefined private key and have an explicit return type.

-export const createOrderEvent = async (order: IOrder) => {
+export const createOrderEvent = async (order: IOrder): Promise<{ [key: string]: any } | undefined> => {
   const myPrivKey = Config.getPrivateKey();
+  if (!myPrivKey) {
+    console.error('Private key not configured');
+    return;
+  }
   if (order.is_public === false) {
     return;
   }
🧹 Nitpick comments (7)
bot/modules/nostr/index.ts (3)

1-1: Convert require to import statement

For consistency with ES modules:

-require('websocket-polyfill');
+import 'websocket-polyfill';

9-9: Convert CommunityEvents require to import

For consistency with ES modules:

-const CommunityEvents = require('../events/community');
+import * as CommunityEvents from '../events/community';

20-22: Add type for community object and implement notification logic

The TODO comment should be addressed and proper typing added for the community object.

Would you like me to help implement the notification logic for community updates? I can also help define the proper type for the community object instead of using any.

tsconfig.json (1)

7-7: Consider removing the DOM library.

The inclusion of "DOM" in the lib array seems unnecessary for a bot module that doesn't interact with browser APIs. The "ES2021" library is sufficient for Promise.any support.

-    "lib":["ES2021", "DOM"],
+    "lib":["ES2021"],
bot/modules/nostr/events.ts (3)

1-6: Consider organizing imports by category.

For better maintainability, consider grouping imports into categories:

  1. External dependencies
  2. Internal config/utils
  3. Models/Types
 import { finalizeEvent, verifyEvent } from 'nostr-tools';
+
 import * as Config from './config';
-
-import { Community } from '../../../models';
-import { toKebabCase, removeAtSymbol } from '../../../util';
 import { IOrder } from '../../../models/order';
+import { Community } from '../../../models';
+
+import { toKebabCase, removeAtSymbol } from '../../../util';

12-18: Improve error message and number parsing.

Consider the following improvements:

  1. Make error messages more descriptive by including the expected format/purpose
  2. Add radix parameter to parseInt for explicit base-10 parsing
 const orderToTags = async (order: IOrder) => {
   const orderPublishedExpirationWindow = process.env.ORDER_PUBLISHED_EXPIRATION_WINDOW;
   if(orderPublishedExpirationWindow === undefined)
-    throw new Error("Environment variable ORDER_PUBLISHED_EXPIRATION_WINDOW is not defined");
+    throw new Error("Environment variable ORDER_PUBLISHED_EXPIRATION_WINDOW is not defined. Expected: number of seconds for order expiration window");
   const expiration =
     Math.floor(Date.now() / 1000) +
-    parseInt(orderPublishedExpirationWindow);
+    parseInt(orderPublishedExpirationWindow, 10);

20-24: Simplify fiat_amount array construction.

The current implementation can be simplified using array spread operator.

-  const fiat_amount = ['fa'];
-  if (order.fiat_amount === undefined) {
-    fiat_amount.push(order.min_amount.toString(), order.max_amount.toString());
-  } else {
-    fiat_amount.push(order.fiat_amount.toString());
-  }
+  const fiat_amount = [
+    'fa',
+    ...(order.fiat_amount === undefined
+      ? [order.min_amount.toString(), order.max_amount.toString()]
+      : [order.fiat_amount.toString()])
+  ];
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 819f8a1 and a776738.

📒 Files selected for processing (7)
  • bot/modules/nostr/commands.ts (1 hunks)
  • bot/modules/nostr/config.js (0 hunks)
  • bot/modules/nostr/config.ts (1 hunks)
  • bot/modules/nostr/events.ts (3 hunks)
  • bot/modules/nostr/index.ts (2 hunks)
  • bot/modules/nostr/lib.ts (1 hunks)
  • tsconfig.json (1 hunks)
💤 Files with no reviewable changes (1)
  • bot/modules/nostr/config.js
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: Analyze (javascript)
🔇 Additional comments (3)
bot/modules/nostr/commands.ts (1)

Line range hint 6-22: LGTM! Well-structured command implementation.

The code has proper:

  • Error handling with logging
  • Type annotations
  • HTML escaping for relay URLs
bot/modules/nostr/index.ts (1)

24-24: 🛠️ Refactor suggestion

Move OrderEvents import to top level

The require statement should be moved to the top level with other imports:

-  const OrderEvents = require('../events/orders');

Add to top-level imports:

+import * as OrderEvents from '../events/orders';

Likely invalid or redundant comment.

bot/modules/nostr/events.ts (1)

Line range hint 57-82: Verify event creation functionality.

Given the concerns about Nostr notifications not working properly, let's verify the event creation and publication flow.

✅ Verification successful

Event creation and publication flow is properly implemented

The code correctly handles the complete flow from event creation to publication:

  • Creates events only for public orders
  • Verifies events before publication
  • Publishes to configured relays using the pool
🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Search for usage of createOrderEvent and verify the event publication flow
echo "Searching for createOrderEvent usage..."
rg -A 5 "createOrderEvent" --type typescript

echo "\nSearching for event publication code..."
rg "publish.*Event" --type typescript

echo "\nChecking for any error logging related to Nostr events..."
rg "console\.(error|warn).*nostr" -i --type typescript

Length of output: 557


Script:

#!/bin/bash
# Search with correct file extensions
echo "Searching for createOrderEvent usage..."
rg -A 5 "createOrderEvent" -t ts -t js

echo "\nSearching for event publication code..."
rg "publish.*Event" -t ts -t js

echo "\nChecking for Nostr configuration..."
rg "Config\.get.*(?i)nostr" -t ts -t js

echo "\nChecking for any error logging related to Nostr..."
rg "console\.(error|warn).*nostr" -i -t ts -t js

echo "\nLooking for Nostr-related files..."
fd -e ts -e js . | grep -i nostr

Length of output: 1899

Comment on lines 9 to 11
export const encodeNpub = (hex: string) => {
return Nostr.nip19.npubEncode(hex);
};
Copy link

Choose a reason for hiding this comment

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

⚠️ Potential issue

Add error handling and return type annotation for encodeNpub

The function should handle invalid hex strings and include return type annotation.

-export const encodeNpub = (hex: string) => {
+export const encodeNpub = (hex: string): string => {
+  if (!/^[0-9a-f]{64}$/i.test(hex)) {
+    throw new Error('Invalid hex string');
+  }
   return Nostr.nip19.npubEncode(hex);
 };
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
export const encodeNpub = (hex: string) => {
return Nostr.nip19.npubEncode(hex);
};
export const encodeNpub = (hex: string): string => {
if (!/^[0-9a-f]{64}$/i.test(hex)) {
throw new Error('Invalid hex string');
}
return Nostr.nip19.npubEncode(hex);
};

Comment on lines 3 to 8
export const decodeNpub = (npub: string) => {
try {
const { type, data } = Nostr.nip19.decode(npub);
if (type === 'npub') return data;
} catch (err) {}
};
Copy link

Choose a reason for hiding this comment

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

⚠️ Potential issue

Add error handling and return type annotation for decodeNpub

The function has the following issues:

  1. Empty catch block silently fails
  2. Missing return type annotation
  3. Implicit undefined return when type !== 'npub'
-export const decodeNpub = (npub: string) => {
+export const decodeNpub = (npub: string): string | undefined => {
   try {
     const { type, data } = Nostr.nip19.decode(npub);
     if (type === 'npub') return data;
+    return undefined;
   } catch (err) {
+    logger.error('Failed to decode npub:', err);
+    return undefined;
   }
 };
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
export const decodeNpub = (npub: string) => {
try {
const { type, data } = Nostr.nip19.decode(npub);
if (type === 'npub') return data;
} catch (err) {}
};
export const decodeNpub = (npub: string): string | undefined => {
try {
const { type, data } = Nostr.nip19.decode(npub);
if (type === 'npub') return data;
return undefined;
} catch (err) {
console.error('Failed to decode npub:', err);
return undefined;
}
};

Comment on lines +11 to +15
export const pool = new SimplePool();
const relays = (env => {
if (!env.RELAYS) return [];
return env.RELAYS.split(',');
})(process.env);
Copy link

Choose a reason for hiding this comment

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

⚠️ Potential issue

Add type annotation for relays array and validate relay URLs

The relays array should be typed and URLs should be validated.

 export const pool = new SimplePool();
+const isValidRelayUrl = (url: string): boolean => {
+  try {
+    return new URL(url).protocol === 'wss:';
+  } catch {
+    return false;
+  }
+};
+
+const relays: string[] = ((env: NodeJS.ProcessEnv) => {
   if (!env.RELAYS) return [];
-  return env.RELAYS.split(',');
+  return env.RELAYS.split(',').filter(isValidRelayUrl);
 })(process.env);
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
export const pool = new SimplePool();
const relays = (env => {
if (!env.RELAYS) return [];
return env.RELAYS.split(',');
})(process.env);
export const pool = new SimplePool();
const isValidRelayUrl = (url: string): boolean => {
try {
return new URL(url).protocol === 'wss:';
} catch {
return false;
}
};
const relays: string[] = ((env: NodeJS.ProcessEnv) => {
if (!env.RELAYS) return [];
return env.RELAYS.split(',').filter(isValidRelayUrl);
})(process.env);

Comment on lines +4 to +6
const nostrSkEnvVar = process.env.NOSTR_SK;
const sk = nostrSkEnvVar ? Buffer.from(nostrSkEnvVar, 'hex') : generateSecretKey();
const pk = nostrGetPublicKey(sk);
Copy link

Choose a reason for hiding this comment

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

⚠️ Potential issue

Add validation for NOSTR_SK environment variable

The hex format of NOSTR_SK should be validated before usage.

 const nostrSkEnvVar = process.env.NOSTR_SK;
-const sk = nostrSkEnvVar ? Buffer.from(nostrSkEnvVar, 'hex') : generateSecretKey();
+const sk = nostrSkEnvVar 
+  ? (/^[0-9a-f]{64}$/i.test(nostrSkEnvVar) 
+      ? Buffer.from(nostrSkEnvVar, 'hex') 
+      : generateSecretKey())
+  : generateSecretKey();
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
const nostrSkEnvVar = process.env.NOSTR_SK;
const sk = nostrSkEnvVar ? Buffer.from(nostrSkEnvVar, 'hex') : generateSecretKey();
const pk = nostrGetPublicKey(sk);
const nostrSkEnvVar = process.env.NOSTR_SK;
const sk = nostrSkEnvVar
? (/^[0-9a-f]{64}$/i.test(nostrSkEnvVar)
? Buffer.from(nostrSkEnvVar, 'hex')
: generateSecretKey())
: generateSecretKey();
const pk = nostrGetPublicKey(sk);

Comment on lines +17 to +20
export const addRelay = (relay: string) => {
relays.push(relay);
relays.map(relay => pool.ensureRelay(relay));
};
Copy link

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Improve relay management

The current implementation has potential issues:

  1. Duplicate relays aren't prevented
  2. No validation of relay URL format
  3. No cleanup of disconnected relays
-export const addRelay = (relay: string) => {
+export const addRelay = (relay: string): boolean => {
+  if (!isValidRelayUrl(relay) || relays.includes(relay)) {
+    return false;
+  }
   relays.push(relay);
-  relays.map(relay => pool.ensureRelay(relay));
+  pool.ensureRelay(relay);
+  return true;
 };

Committable suggestion skipped: line range outside the PR's diff.

Using `Nostr` from `nostr-tools` as before resulted in error:
```
Cannot read properties of undefined (reading 'nip19') TypeError: Cannot read properties of undefined (reading 'nip19')
```
@webwarrior-ws
Copy link
Contributor Author

@Catrya I fixed both errors in the last commit.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

♻️ Duplicate comments (2)
bot/modules/nostr/lib.ts (2)

3-8: ⚠️ Potential issue

Add error handling and return type annotation for decodeNpub

The function has the following issues:

  1. Empty catch block silently fails
  2. Missing return type annotation
  3. Implicit undefined return when type !== 'npub'
-export const decodeNpub = (npub: string) => {
+export const decodeNpub = (npub: string): string | undefined => {
   try {
     const { type, data } = nip19.decode(npub);
     if (type === 'npub') return data;
+    return undefined;
   } catch (err) {
+    logger.error('Failed to decode npub:', err);
+    return undefined;
   }
 };

9-11: ⚠️ Potential issue

Add error handling and return type annotation for encodeNpub

The function should handle invalid hex strings and include return type annotation.

-export const encodeNpub = (hex: string) => {
+export const encodeNpub = (hex: string): string => {
+  if (!/^[0-9a-f]{64}$/i.test(hex)) {
+    throw new Error('Invalid hex string');
+  }
   return nip19.npubEncode(hex);
 };
🧹 Nitpick comments (1)
bot/modules/nostr/commands.ts (1)

Line range hint 6-22: Consider adding input validation for publicKey

The function has good error handling and type annotations. However, consider validating the publicKey format before encoding it to npub.

 export const info = async (ctx: MainContext) => {
   try {
     const publicKey = Config.getPublicKey();
     if (!publicKey) return;
+    if (!/^[0-9a-f]{64}$/i.test(publicKey)) {
+      logger.error('Invalid public key format');
+      return ctx.reply('Error: Invalid public key format');
+    }
     const info = {
       publicKey,
       npub: nip19.npubEncode(publicKey),
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between a776738 and 10c646c.

📒 Files selected for processing (2)
  • bot/modules/nostr/commands.ts (1 hunks)
  • bot/modules/nostr/lib.ts (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (2)
  • GitHub Check: ci_to_main
  • GitHub Check: Analyze (javascript)
🔇 Additional comments (1)
bot/modules/nostr/commands.ts (1)

1-4: LGTM! Clean module imports

The imports are well-organized, using specific imports where possible and namespace imports where appropriate. The type imports are correctly separated.

Comment on lines +1 to +2
import { nip19 } from 'nostr-tools';

Copy link

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Add logger import

Import the logger module to support error logging in the decodeNpub function.

 import { nip19 } from 'nostr-tools';
+import { logger } from '../../../logger';
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
import { nip19 } from 'nostr-tools';
import { nip19 } from 'nostr-tools';
import { logger } from '../../../logger';

@grunch grunch merged commit 3e4ac23 into lnp2pBot:main Feb 18, 2025
5 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.

3 participants