Skip to content

Conversation

@jessicayu626
Copy link
Contributor

No description provided.

@jessicayu626 jessicayu626 requested a review from Antzen November 28, 2017 06:04
Copy link
Contributor

@Antzen Antzen left a comment

Choose a reason for hiding this comment

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

Overall, this looks good to me. I'm just a little concerned that the integration tests don't fully test correctness since Travis has been having issues / ReadWriteTests is still commented out. I think it might be best for us to clarify the testing situation before merging this in.

return;
}
if (children.size() > 0) {
if (children.size() > 1) {
Copy link
Contributor

Choose a reason for hiding this comment

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

Is this a fix for an unrelated bug?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

It's a fix for a bug.

Copy link
Contributor

Choose a reason for hiding this comment

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

👍

RenewLeaseRequestProto req;
req.set_clientname(client_name);
RenewLeaseResponseProto res;
renew_lease(req, res);
Copy link
Contributor

@Antzen Antzen Nov 29, 2017

Choose a reason for hiding this comment

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

This looks like a workaround for creating a lease. Do we not have a "helper function" for creating leases? I might be wrong about there being a cleaner way though; just wondering.

@jessicayu626
Copy link
Contributor Author

I think this pr is isolated from the ReadWriteTest failing and I do not understand why this needs to wait before other test is fixed. I

@Antzen
Copy link
Contributor

Antzen commented Dec 6, 2017

As we discussed in person last week, resolving the ReadWrite issue before introducing these changes would allow for debugging to be easier, so we held back from merging this PR. But it appears to have been fixed (?), and we need to merge what we have at some point anyhow.

Let's go ahead and resolve the merge conflicts and then merge.

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