fix(common): stop expireCache looping with no archived attachments - #1092
Open
giaBaoJS wants to merge 1 commit into
Open
fix(common): stop expireCache looping with no archived attachments#1092giaBaoJS wants to merge 1 commit into
giaBaoJS wants to merge 1 commit into
Conversation
🦋 Changeset detectedLatest commit: 5642822 The changes in this PR will be included in the next version bump. This PR includes changesets to release 6 packages
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 |
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.
The bug
AttachmentQueue.expireCache()never resolves when the number of archived attachments is at or belowarchivedCacheLimit, which is the normal case. It keeps re-running the sameSELECTagainst the attachments table forever.Reproduction
Root cause
AttachmentContext.deleteArchivedAttachmentsreturns a "cleanup finished" flag: the last line returnsarchivedAttachments.length < limit, so a partial page means there is nothing left to page through. The early return for an empty page returnedfalseinstead, which is the opposite: an empty page is the smallest possible partial page.AttachmentQueue.expireCacheloopswhile (!isDone)on that flag, so the empty case spins forever.The other caller,
AttachmentQueue.syncStorage, ignores the return value, which is why this has not shown up there.For comparison, the same operation in the older
@powersync/attachmentspackage (AbstractAttachmentQueue.expireCache) returns immediately when the query comes back empty.What the tests assert
AttachmentContext > deleteArchivedAttachments > reports completion when there is nothing to delete:deleteArchivedAttachments()returnstruefor an empty page, and neither the callback nor the delete statement runs. Without the fix this fails withexpected false to be true.AttachmentContext > deleteArchivedAttachments > reports completion after deleting a partial page: pins the existing behaviour thattruemeans "done" for a page smaller than the internal limit.AttachmentQueue > expireCache > stops once there is nothing archived left to delete:expireCache()resolves after a single query. The fake database throws after a few queries so the non-terminating case fails as an assertion rather than hanging the suite.pnpm --filter @powersync/common test: 27 tests passing before, 30 after.