fix duplicate key deletion when forget called #14
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.
Hey @janos,
I believe your implementation of singleflight is affected by the issue described here:
golang/go#31420.
This issue specifically impacts your implementation because a thread can call
Forget()
after its own context has expired.I implemented the solution found in this CL:
https://go-review.googlesource.com/c/sync/+/171897.
All existing tests pass successfully, and I also added the test from the CL to ensure that the new behavior is consistent with Google’s implementation.
Note: Before applying the fix, the TestForgetMisbehaving test failed.