-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: basic in-memory de-duping revalidation queue #360
Conversation
🦋 Changeset detectedLatest commit: e134601 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 |
commit: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I took a quick look but I'm not sure to understand how dedup works here.
Can you add some tests?
Thanks
I made a super dumb mistake last night and forgot to actually check if a revalidation was in progress 😅. Obviously immediately visible when adding tests. |
7005134
to
95bb5be
Compare
This reverts commit 42739ae.
21c85f5
to
bc84f8b
Compare
bc84f8b
to
6256150
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
I added some comments but this looks good to go.
Thanks for your work on this and sorry for the review delay.
Docs PR - opennextjs/docs#74 |
Super basic de-duping on a per-isolate basis for the queue.
This approach uses the MessageGroupId for the de-duping key as it is based on just the path, and the key for ISR pages in the incremental cache is also the path, so we can compute the correct key to free from the list of revalidated paths.