| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2025-05-04 | Remove the duplicate resize hack | Jesper Jensen | |
| It turns out this problem also included a bunch of other data corruption issues. I don't really know how that got in there, but I don't think this was a data-structure issue. We should revert to an assert to crash hard. We now have some checks that should give us a warning closer to when the corruption happens next time. | |||
| 2025-05-04 | Check that the load is accurate | Jesper Jensen | |
| 2025-05-04 | time_t is apparently signed? | Jesper Jensen | |
| 2025-05-04 | Extract the expire metric out | Jesper Jensen | |
| 2025-05-04 | Add metric to track next hash expire | Jesper Jensen | |
| 2025-05-04 | Add some check for expiry time | Jesper Jensen | |
| 2025-05-04 | Add some code to assert that there are no dupes | Jesper Jensen | |
| 2025-05-04 | Drop duplicated peer entries | Jesper Jensen | |
| Apparently it's somehow possible for us to duplicate the peer entry. While we figure out how, let's just drop them instead of crashing. | |||
| 2025-04-14 | Add current hash metric | Jesper Jensen | |
| It seems like it would be nice to know how many infohashes we actually know about. Let's add a guage that tells us that directly. | |||
| 2025-04-12 | Add prometheus monitoring | Jesper Jensen | |
| 2025-04-12 | I don't know | Jesper Jensen | |
| 2025-04-12 | I don't remember | Jesper Jensen | |
 |
index : dht.git | |
| BitTorrent DHT peer |
| summaryrefslogtreecommitdiff |