Repository navigation
Conversation
Collaborator
|
Plz can to remove the tests folder |
Toomad23
force-pushed
the
fix/device-share-expiry-8044
branch
from
September 27, 2026 20:54
cb386d6 to
8df2305
Compare
Author
|
Removed the test directory as requested. The diff now contains only the one-line fix in |
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.
Summary
Fixes #8044.
createDeviceShareLinkremoves expired entries withdelete docs[i]. This leaves a sparse array;common.Clone()serializes the event through JSON, converting holes tonull. The recipient'sevent.deviceSharesloop then readsuseridfromnull.Use
docs.splice(i--, 1)instead, preserving a dense array and checking the next entry after removal. Existing expiry boundary, recurring/unlimited-share behavior, field stripping, and per-recipient URL filtering are unchanged.Verification (local harness, not part of the diff)
Per maintainer feedback, the regression harness is kept locally and is not included in this PR. It uses Node's built-in test runner with no extra dependencies. It executes the actual database callback and recipient loop extracted from
meshuser.js, plus the actualcommon.Clone. Database and event transport are in-memory doubles.Against upstream
029b7338ecfeeacc65da3b5a1a4cc069baeb2f65: 4 failures / 7 tests. After the fix: 7 / 7 passed.Coverage: expired + live entries, consecutive expired entries, all expired, empty result, active/unlimited/recurring/boundary shares, owner versus other-recipient URL visibility, database-error path.
The local harness was re-run after removing the test directory; all checks still pass. The PR diff now contains only the one-line
meshuser.jsfix.Scope and QA