Skip to content

Conversation

@scribe
Copy link
Contributor

@scribe scribe commented Apr 15, 2019

I'm not sure how to write a unit test for this issue, but after working a lot with Kyle I believe this is a fix.

@scribe
Copy link
Contributor Author

scribe commented Apr 18, 2019

@rpmoore I'm trying to think about how to test this still.

}

try {
striped.get(key).lock();
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why not get the lock once instead of twice?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is fixed, we only call striped.get once now. See changes in 878c16a

@rpmoore rpmoore merged commit c227f84 into master Apr 23, 2019
scribe added a commit that referenced this pull request Apr 23, 2019
* This still needs testing but this is the sparse fix

* using slices

* removing extra get for slice
rpmoore pushed a commit that referenced this pull request Apr 23, 2019
* This still needs testing but this is the sparse fix

* using slices

* removing extra get for slice
@RachelTucker RachelTucker deleted the FixForSparse branch October 7, 2020 18:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants