bazel build //src/python/grpcio/grpc/_cython:cygrpc.so
took a LONG time and after I moved the .so cp bazel-bin/src/python/grpcio/grpc/_cython/cygrpc.so src/python/grpcio/grpc/_cython/
it seems to be running my modified code... so I guess worth it?
So i've got a project that is pretty simple. basically just one streaming call in kotlin. rpc Outputs (messages.OutputsRequest) returns (stream messages.OutStreamChunk);
point is to stream stdOut/stdErr from server running a process back to the client real time.
what I am finding is that nothing gets sent until the flow on the server side gets closed, then all of it dumps to the client at once. total content size is around 512kb in raw text.
so what it feels like is that it is buffering at the server for far too long. this is my first grpc anything so i don't know what I don't know. is there anything that seems like a gotcha I should check first? sort of prodding at it blind now
init_openssl()':
ssl_transport_security.cc:(.text+0xc8): undefined reference to
OpenSSL_add_all_algorithms'peer_property_from_x509_common_name(x509_st*, tsi_peer_property*)':
ssl_transport_security.cc:(.text+0x5ff): undefined reference to
OPENSSL_free'add_pem_certificate(x509_st*, tsi_peer_property*)':
ssl_transport_security.cc:(.text+0x667): undefined reference to
BIO_get_mem_data'add_subject_alt_names_properties_to_peer(tsi_peer*, stack_st_GENERAL_NAME*, unsigned long)':
ssl_transport_security.cc:(.text+0x7c3): undefined reference to
OPENSSL_free'
Hi. I'm having some issues connecting to a go grpc server from c# grpc client:
I0215 07:57:22.940083 123145488719872 /tmpfs/src/github/grpc/workspace_csharp_ext_macos_x64/src/core/ext/filters/client_channel/subchannel.cc:1060: Connect failed: {"created":"@1613372242.939926000","description":"Cannot check peer: missing selected ALPN property.","file":"/tmpfs/src/github/grpc/workspace_csharp_ext_macos_x64/src/core/lib/security/security_connector/ssl_utils.cc","file_line":160}
I'm unclear if this error in a client or server issue. I'm able to connect to a different go grpc server using the exact same client code which makes me think it must be an issue with the server. Any ideas? Thanks
syntax = "proto3";
package system;
import "google/protobuf/empty.proto";
message UptimeResponse {
uint64 os_uptime_seconds = 1;
repeated float os_load_average = 2;
}
service System {
rpc uptime (google.protobuf.Empty) returns (UptimeResponse) {};
}
Join us for February's 🐶 gRPC Community Meetup! 🎉
Agenda: gRPC Community Doc
This virtual event is designed for end users, a space for our community to meet, get to know each other, and learn about uses and applications of gRPC project. In this meeting, we will hear working group updates.
Ahmet Alp Balkan, Software Engineer at Google, will present "Serverless gRPC on Google Cloud" where he'll run gRPC applications as serverless on Google’s infrastructure. (Hint: It's not Kubernetes). With Cloud Run, we can run any container image using any RPC type or language quite easily. But don’t get scared: You don't have to learn containers to use this. In this demo, we'll show how you can use technologies like ko and Buildpacks.
Looking forward to seeing most of you at the meetup next week!
Check out the meetup page: https://www.meetup.com/gRPCio/events/276403597/
Join with Google Meet
meet.google.com/ohf-nizn-wxx
Join by phone
(US) +1 929-277-6563 PIN: 893 502 491#
We will be hosting a new community meetup next Tuesday, February 23. If you are part of a working group, please share any updates you want gRPC users to be aware of. Add your updates, with any relevant links, here: http://bit.ly/grpcmeetings
Deadline to submit an update is Monday, February 22.
linux1/obj/svc/src/proto/clock-service.clock.pb.o:clock.pb.cc:vtable for svc::RtcDateTime: error: undefined reference to 'google::protobuf::Message::GetTypeName() const'
linux1/obj/svc/src/proto/clock-service.clock.pb.o:clock.pb.cc:vtable for svc::RtcDateTime: error: undefined reference to 'google::protobuf::Message::InitializationErrorString() const'
hey @ejona86 was there a commit that added the enter
and exit
calls you proposed here? grpc/grpc-java#1949
the issue was closed but i don't see those methods on SimpleForwardingClient/ServerCall
name == '' # True
instead of name == None # True
RST_STREAM with error code 2
errors in the client (in particular grpc cpp 1.32.0) when the server (in particular golang 1.36.0) does a Send and then returns from the RPC in quick succession? I'm using a bidi streaming rpc. I see this behavior when using nginx proxies and an L4 Load Balancer in the cloud. It looks like a race condition is happening between the last Send and the EOS frame when returning from the rpc in the server. The logs in the server show a transport is closing
error when I turn on the logging. The rpc itself finishes around 100 to 200 ms and the bytes sent and received are around 300 bytes. Indeed, if I add a sleep(1)
between the last Send and the return nil
in the server, I no longer see RST_STREAM errors.