Skip to content
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

GetClientAllocs handles garbage collection events #3452

Merged
merged 2 commits into from
Oct 27, 2017
Merged

Conversation

dadgar
Copy link
Contributor

@dadgar dadgar commented Oct 27, 2017

This fixes an issue in which a garbage collection event may have happened on
the servers and the client would not immediately pull the new set of
allocations.

Copy link
Contributor

@chelseakomlo chelseakomlo left a comment

Choose a reason for hiding this comment

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

Looks good! In general, it would be nice to maybe limit large functions in the future, so maybe in general in the future we can think about splitting functionality into well-named functions. But this looks like a clean and well-documented fix.

if time.Since(start) < 100*time.Millisecond {
t.Fatalf("too fast")
}
if resp3.Index != 200 {
Copy link
Contributor

Choose a reason for hiding this comment

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

Maybe use assert package for continuity.

@dadgar dadgar merged commit a0ce033 into master Oct 27, 2017
@dadgar dadgar deleted the f-system-gc branch October 27, 2017 16:50
@github-actions
Copy link

I'm going to lock this pull request because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 19, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants