You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
In addition to creating task invalidators for file reads, we also create invalidators for file writes. This extends the fuzzer to cover that.
This is a bit trickier to test. Because the write call doesn't return anything, the caller of write never gets invalidated and re-executed, even though write does. So instead, we must observe that write was re-executed by looking at the contents of the file it wrote to. We write a sentinel value to files when we call the turbo-tasks-fs write function, and write random values to it to trigger an invalidation.
I tested this on Windows and Linux.
I don't care about the code quality here, so this was LLM-generated with very lightweight review.
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.
In addition to creating task invalidators for file reads, we also create invalidators for file writes. This extends the fuzzer to cover that.
This is a bit trickier to test. Because the
writecall doesn't return anything, the caller ofwritenever gets invalidated and re-executed, even thoughwritedoes. So instead, we must observe thatwritewas re-executed by looking at the contents of the file it wrote to. We write a sentinel value to files when we call the turbo-tasks-fswritefunction, and write random values to it to trigger an invalidation.I tested this on Windows and Linux.
I don't care about the code quality here, so this was LLM-generated with very lightweight review.