From 7065a067764c0358727100770905a8cb8cdb3014 Mon Sep 17 00:00:00 2001 From: DanConwayDev Date: Tue, 13 Jan 2026 09:17:21 +0000 Subject: [PATCH] fix: properly format ID fields in issue files --- 1bb0-event-signature-verification.md | 2 ++ 1f4f-poor-naughty-list-identification.md | 2 ++ 2cdc-nip-86-relay-management-api.md | 2 ++ 76fe-repository-count-metric.md | 36 +++++++++++++++++++++ 7d0b-management-dashboard.md | 2 ++ 8430-storage-limits-and-quota-management.md | 2 ++ b905-deletion-request-support.md | 2 ++ cc36-database-backend-evaluation.md | 2 ++ d6ee-defensive-relay-features.md | 2 ++ 9 files changed, 52 insertions(+) diff --git a/1bb0-event-signature-verification.md b/1bb0-event-signature-verification.md index 5e87bec..6d5ea2d 100644 --- a/1bb0-event-signature-verification.md +++ b/1bb0-event-signature-verification.md @@ -1,5 +1,7 @@ # Event Signature Verification +**ID:** 1bb0 + ## Issue We need to verify that event signatures are being checked for every event we store or issue over websockets. Currently unclear if rust-nostr is doing this automatically or if we need explicit verification. diff --git a/1f4f-poor-naughty-list-identification.md b/1f4f-poor-naughty-list-identification.md index 99c3d05..58eda89 100644 --- a/1f4f-poor-naughty-list-identification.md +++ b/1f4f-poor-naughty-list-identification.md @@ -1,5 +1,7 @@ # Poor Naughty List Identification +**ID:** 1f4f + ## Issue Summary We need to detect malicious behavior from clients and relays to protect our system from abuse, DoS attacks, and bandwidth exhaustion. This should feed into a reputation system or connection throttling/banning mechanism. diff --git a/2cdc-nip-86-relay-management-api.md b/2cdc-nip-86-relay-management-api.md index a5cd058..6db7cfa 100644 --- a/2cdc-nip-86-relay-management-api.md +++ b/2cdc-nip-86-relay-management-api.md @@ -1,5 +1,7 @@ # NIP-86 Relay Management API +**ID:** 2cdc + ## Issue Summary Implement NIP-86 (Relay Management API) to provide authenticated administrative control over the relay. This enables operators to blacklist users, delete repositories, ban event posting, and perform other management actions through a standardized API. diff --git a/76fe-repository-count-metric.md b/76fe-repository-count-metric.md index bd4fa1c..3066fcb 100644 --- a/76fe-repository-count-metric.md +++ b/76fe-repository-count-metric.md @@ -1,5 +1,7 @@ # Issue: ngit_repositories_total Metric Incorrectly Reports 0 +**ID:** 76fe + **Date Discovered:** 2026-01-12 **Date Resolved:** 2026-01-12 **Priority:** Medium @@ -17,14 +19,20 @@ The `ngit_repositories_total` Prometheus metric reports 0 even though: **Current behavior:** ```bash # Metric shows 0 + +**ID:** 76fe $ curl -s http://localhost:8082/metrics | grep ngit_repositories_total ngit_repositories_total 0 # But 15 repos exist on disk + +**ID:** 76fe $ find /persistent/ngit-danconwaydev-com-ngit-grasp/git/ -name '*.git' -type d | wc -l 15 # And git access works + +**ID:** 76fe $ git ls-remote https://ngit.danconwaydev.com/npub15qy.../ngit-grasp.git a63dc8a9e5f9cad50f4ea7c6c5d2ed544bc70656 HEAD ``` @@ -84,9 +92,13 @@ The metric currently counts repositories **released from purgatory** (fully sync ### Test 1: Verify Current Count ```bash # Manual count + +**ID:** 76fe find /persistent/ngit-danconwaydev-com-ngit-grasp/git/ -name '*.git' -type d | wc -l # Should match metric + +**ID:** 76fe curl -s http://localhost:8082/metrics | grep ngit_repositories_total ``` @@ -95,22 +107,34 @@ Test with ngit-grasp repository specifically: ```bash # Clone the repository + +**ID:** 76fe git clone https://ngit.danconwaydev.com/npub15qydau2hjma6ngxkl2cyar74wzyjshvl65za5k5rl69264ar2exs5cyejr/ngit-grasp.git /tmp/ngit-grasp-test # Verify commit history exists + +**ID:** 76fe cd /tmp/ngit-grasp-test git log --oneline | head -20 # Check specific commit matches production + +**ID:** 76fe git log -1 a63dc8a9e5f9cad50f4ea7c6c5d2ed544bc70656 # Verify files exist + +**ID:** 76fe ls -la # Check branch structure + +**ID:** 76fe git branch -r # Cleanup + +**ID:** 76fe cd /tmp rm -rf ngit-grasp-test ``` @@ -118,12 +142,18 @@ rm -rf ngit-grasp-test ### Test 3: After Fix - Count Accuracy ```bash # Restart service + +**ID:** 76fe sudo systemctl restart ngit-grasp-production # Wait 30 seconds for startup + +**ID:** 76fe sleep 30 # Check metric matches disk + +**ID:** 76fe DISK_COUNT=$(ssh dc@ngit.danconwaydev.com "sudo find /persistent/ngit-danconwaydev-com-ngit-grasp/git/ -name '*.git' -type d | wc -l") METRIC_COUNT=$(ssh dc@ngit.danconwaydev.com "curl -s http://localhost:8082/metrics | grep 'ngit_repositories_total ' | awk '{print \$2}'") @@ -254,12 +284,18 @@ $ cargo test --test repository_creation **Verification commands:** ```bash # Check metric value (triggers a count) + +**ID:** 76fe curl -s http://localhost:8082/metrics | grep ngit_repositories_total # Check disk count (should match within 15s) + +**ID:** 76fe sudo find /persistent/ngit-danconwaydev-com-ngit-grasp/git/ -name '*.git' -type d | wc -l # Multiple requests should show same count (idempotent) + +**ID:** 76fe curl -s http://localhost:8082/metrics | grep ngit_repositories_total ``` diff --git a/7d0b-management-dashboard.md b/7d0b-management-dashboard.md index 1c7a3eb..9fc5dea 100644 --- a/7d0b-management-dashboard.md +++ b/7d0b-management-dashboard.md @@ -1,5 +1,7 @@ # Management Dashboard +**ID:** 7d0b + ## Issue Summary We need a web-based management dashboard to monitor relay health, view storage and usage statistics, and provide basic operational visibility. This dashboard should display key metrics about relay operations, resource utilization, and usage patterns. diff --git a/8430-storage-limits-and-quota-management.md b/8430-storage-limits-and-quota-management.md index 20c4909..26d5137 100644 --- a/8430-storage-limits-and-quota-management.md +++ b/8430-storage-limits-and-quota-management.md @@ -1,5 +1,7 @@ # Storage Limits and Quota Management +**ID:** 8430 + ## Issue Summary We currently have no storage limits or quota enforcement, allowing users to push arbitrarily large repositories (e.g., 20GB+) and potentially fill the relay's disk. We need configurable storage limits at multiple levels and graceful handling when approaching disk capacity. diff --git a/b905-deletion-request-support.md b/b905-deletion-request-support.md index cdbad6d..12f85da 100644 --- a/b905-deletion-request-support.md +++ b/b905-deletion-request-support.md @@ -1,5 +1,7 @@ # Deletion Request Support (NIP-09) +**ID:** b905 + **Status:** Planning Complete, Ready for Implementation **Priority:** Medium **Complexity:** High (graph algorithms, multi-database coordination) diff --git a/cc36-database-backend-evaluation.md b/cc36-database-backend-evaluation.md index c60931c..8d15e17 100644 --- a/cc36-database-backend-evaluation.md +++ b/cc36-database-backend-evaluation.md @@ -1,5 +1,7 @@ # Database Backend Evaluation +**ID:** cc36 + ## Issue Summary We currently lack guidance on when to use nostrdb vs lmdb as the database backend. We need to perform an efficiency review comparing these backends and evaluate caching strategies (especially tag caches and filter-related caching) to provide clear recommendations and optimize query performance. diff --git a/d6ee-defensive-relay-features.md b/d6ee-defensive-relay-features.md index 485b47e..7d3515a 100644 --- a/d6ee-defensive-relay-features.md +++ b/d6ee-defensive-relay-features.md @@ -1,5 +1,7 @@ # Defensive Relay Features +**ID:** d6ee + ## Issue Summary Implement comprehensive rate limiting and resource controls to protect the relay from abuse, whether malicious or accidental. This includes connection limits, subscription limits, event rate limiting, and HTTP request throttling.