• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

cameri / nostream / 41695445305 / 1
78%
main: 78%

Build:
DEFAULT BRANCH: main
Ran 03 Nov 2026 06:46PM UTC
Files 331
Run time 4s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

03 Nov 2026 06:36PM UTC coverage: 31.84% (-1.3%) from 33.137%
41695445305.1

push

github

web-flow
feat(peering): sync configured peers over NIP-77 and a live feed (#1043)

<!--- Provide a general summary of your changes in the Title above -->

## Description
<!--- Describe your changes in detail -->

This PR adds an outbound peering-sync worker that reads each configured
peer's NIP-11 peering scopes, authenticates with NIP-42, reconciles
history over NIP-77, and keeps a live subscription for the same scopes.
Missing events are fetched by id and verified before upsert; live events
are broadcast to local subscribers. Per-peer sync state (last
reconciliation, lag, missing count, errors) is exposed in the admin
console and diagnostics export.
## Related Issue
<!--- This project only accepts pull requests related to open issues -->
<!--- If suggesting a new feature or change, please discuss it in an
issue first -->
<!--- If fixing a bug, there should be an issue describing it with steps
to reproduce -->
<!--- Please link to the issue here: -->
Closes - #935 
## Motivation and Context
<!--- Why is this change required? What problem does it solve? -->

## How Has This Been Tested?
<!--- Please describe in detail how you tested your changes. -->
<!--- Include details of your testing environment, and the tests you ran
to -->
<!--- see how your change affects other areas of the code, etc. -->

## Screenshots (if appropriate):

## Types of changes
<!--- What types of changes does your code introduce? Put an `x` in all
the boxes that apply: -->
- [ ] Non-functional change (docs, style, minor refactor)
- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to change)

## Checklist:
<!--- Go over all the following points, and put an `x` in all the boxes
that apply. -->
- [ ] My code follows the code style of this project.
- [ ] My change requires a change to the documentation.
- [ ] I have updated the documentation acc... (continued)

1426 of 6765 branches covered (21.08%)

Branch coverage included in aggregate %.

4835 of 12899 relevant lines covered (37.48%)

14.13 hits per line

Source Files on job Integration - 41695445305.1
  • Tree
  • List 331
  • Changed 10
  • Source Changed 9
  • Coverage Changed 10
Coverage ∆ File Lines Relevant Covered Missed Hits/Line Branch Hits Branch Misses
  • Back to Build 41695445305
  • 744eeb3e on github
  • Prev Job for on main (#41530042526.2)
  • Next Job for on main (#41733009942.1)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE TRIAL · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc