ximenzaoshi
ximenzaoshi
Here is the related PR https://github.com/etcd-io/etcd/pull/18012.
I also checked the build-in gateway, it seems OK. I think the implementation is different in etcdserver and grpcproxy server, which leads to the different behavior. We mainly use grpcproxy...
Thanks for your reply, Do we have any comments for the watch cancled error? This is another problem which I think is more important than auth. I try to fix...
> > Do we have any comments for the watch cancled error? > > I am not sure what issue you are talking about here. Please feel free to raise...
> > Then start grpc-gateway locally(compiled by the code above). Send watch command to grpc-gateway with curl: > > `curl -X POST -d '{"create_request": {"key":"dGVzdGtleQo=","range_end":"dGVzdGtleTEK"}}' 'localhost:8887/v3/watch'` > > The curl...
> > The watch error happens in this scenario： > > Do you still see the issue after applying the #18012? After applying the https://github.com/etcd-io/etcd/pull/18012, all worked OK.