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

clientv3/integration: cover all client operations #4338

Closed
8 tasks done
gyuho opened this issue Jan 29, 2016 · 0 comments
Closed
8 tasks done

clientv3/integration: cover all client operations #4338

gyuho opened this issue Jan 29, 2016 · 0 comments

Comments

@gyuho gyuho changed the title c clientv3/integration: cover all client operations Jan 29, 2016
@gyuho gyuho added this to the v3.0.0-alpha0 milestone Jan 29, 2016
gyuho added a commit to gyuho/etcd that referenced this issue Jan 29, 2016
gyuho added a commit to gyuho/etcd that referenced this issue Jan 29, 2016
gyuho added a commit to gyuho/etcd that referenced this issue Jan 29, 2016
gyuho added a commit to gyuho/etcd that referenced this issue Jan 29, 2016
gyuho added a commit to gyuho/etcd that referenced this issue Jan 29, 2016
gyuho added a commit to gyuho/etcd that referenced this issue Jan 29, 2016
gyuho added a commit to gyuho/etcd that referenced this issue Jan 29, 2016
gyuho added a commit to gyuho/etcd that referenced this issue Jan 29, 2016
For etcd-io#4338.
And resp.Header.Revision should be from the one in storage
when we just do range, because there is no storage data
change.
gyuho added a commit to gyuho/etcd that referenced this issue Jan 29, 2016
For etcd-io#4338.
And resp.Header.Revision should be from the one in storage
when we just do range, because there is no storage data
change.

update
gyuho added a commit to gyuho/etcd that referenced this issue Jan 30, 2016
For etcd-io#4338.
And resp.Header.Revision should be from the one in storage
when we just do range, because there is no storage data
change.
@gyuho gyuho closed this as completed Feb 5, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

1 participant