Repository navigation
chore: sunset the StaticMirroringWorker - #924
Open
Priyanshubhartistm wants to merge 3 commits into
Open
Priyanshubhartistm wants to merge 3 commits into
Priyanshubhartistm wants to merge 3 commits into
Conversation
🦋 Changeset detectedLatest commit: a4ab2e1 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
[Medium impact] The PR appears safe to merge; the previous settings-update blocker is fixed.
|
Collaborator
Coverage Report for CI Build 39665588362Coverage increased (+1.7%) to 75.454%Details
Uncovered Changes
Coverage Regressions9 previously-covered lines in 2 files lost coverage.
Coverage Stats💛 - Coveralls |
Signed-off-by: Priyanshubhartistm <bhartipriyanshustm@gmail.com>
Signed-off-by: Priyanshubhartistm <bhartipriyanshustm@gmail.com>
Signed-off-by: Priyanshubhartistm <bhartipriyanshustm@gmail.com>
Priyanshubhartistm
force-pushed
the
chore/sunset-static-mirroring-worker
branch
from
October 21, 2026 19:53
dc3da11 to
a4ab2e1
Compare
greptile-apps
Bot
dismissed
their stale review
October 21, 2026 19:53
Dismissed because a newer commit was pushed; Greptile will re-review the current head.
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Removes the
StaticMirroringWorkerand everything that only existed for it, as the maintainer asked on #909.src/app/static-mirroring-worker.ts), its factory and itsstatic-mirroringworker type insrc/index.ts; the primary process no longer forks mirror workers.mirroring.staticis no longer supported. It is gone from the default settings and the docs, and a value that is still configured is ignored: start-up logs a warning that points to NIP-77. TheMirroringtype stays only as a deprecated marker for that warning./admin/ops/mirrorsroute and controller, and the mirror heartbeats of the ops store and its types. The worker table no longer lists mirror workers.mirroring.staticaddresses are no longer probed.CONFIGURATION.md: themirroring.static[]rows are replaced by one row that says the setting was removed and how to sync with another relay (NIP-77, for examplestrfry sync); two mentions of the worker in theeventIdandnip66.targetsrows are dropped.Related Issue
Closes #923
Motivation and Context
The worker mirrored events through its own admission check, separate from the one
EventMessageHandleruses, so every rule added to the write path had to be repeated in it (for example, mirrored writes skipped subscription expiry), and it had no tests (#904). NIP-77 sync and other ways of syncing with relays cover what it was used for.Operators who set
mirroring.staticlose that mirroring on upgrade. Their settings still load, the key is ignored with a warning.PR #920 also edits
static-mirroring-worker.ts, the admin dashboard and the default settings, so whichever of the two merges second will need to resolve a conflict there.How Has This Been Tested?
mirroring.static, the worker list no longer has mirror workers, and mirror addresses are not probed. Removed the tests of the removed code; the admin settings test now checks redaction with a notification target's bot token, sincemirroringis no longer part of the settings.pnpm lint,pnpm check:deps,pnpm run build:check,pnpm run build,pnpm run verify:cli:build,pnpm run test:unit(2508 passing),pnpm run test:cli(105 passing).