-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Fix hook update not being applied when a forced context update was enqueued at the same time #3922
Conversation
📊 Tachometer Benchmark ResultsSummaryduration
usedJSHeapSize
Results02_replace1k
duration
usedJSHeapSize
run-warmup-0
run-warmup-1
run-warmup-2
run-warmup-3
run-warmup-4
run-final
03_update10th1k_x16
duration
usedJSHeapSize
07_create10k
duration
usedJSHeapSize
filter_list
duration
usedJSHeapSize
hydrate1k
duration
usedJSHeapSize
many_updates
duration
usedJSHeapSize
text_update
duration
usedJSHeapSize
todo
duration
usedJSHeapSize
|
Size Change: +129 B (0%) Total Size: 54.3 kB
ℹ️ View Unchanged
|
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.
The test seems reasonable but unfortunately I don't have enough context on the subject matter to be able to approve/deny - adding a tiny comment though
@mdentremont Thanks for the suggestions! Yeah it looks like we need to opt for a more elaborate fix, but I'm confident we can do it now that we know why the error occurred in the first place. |
3d1ade9
to
1ce69e0
Compare
Ok I think I found a better fix. |
1ce69e0
to
2c1f0f1
Compare
2c1f0f1
to
196a65d
Compare
196a65d
to
405c6d3
Compare
Fix hook update not being applied when a forced context update was enqueued at the same time. This fixes a regression that was introduced in #3889 which was released as
10.12.1
.