| Commit message (Collapse) | Author | Age |
|
|
|
| |
when calling a method which is server_streamer and is not implemented by user
|
| |
|
| |
|
|\
| |
| | |
Ruby: remove duplicated `Unimplemented` error definition
|
|\ \
| | |
| | | |
Switch to `send` instead of `method(...).call`
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This commit switches `method(...).call` to `send`. The call sites I
changed were all immediately calling `call` on the method object, then
throwing the method object away. Using `send` should be equivalent and
will not allocate the intermediate `method` object.
|
| |/ |
|
|/ |
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| | |
Unify nearly same methods
|
| |
| |
| |
| |
| |
| | |
`@call` instance variable is same in
ActiveCall#merge_metadata_and_send_if_not_already_sent and
ActiveCall#send_initial_metadata.
|
|/ |
|
| |
|
| |
|
|\
| |
| | |
Don't raise call errors for failed reads or writes of ruby bidi streams
|
| | |
|
|/ |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
1. Organize collapsed ruby yard doc.
2. Update contents about ClientStub#bidi_streamer because
bidi#writes_done hasn't existed.
https://github.com/grpc/grpc/pull/14535#discussion_r171452923
3. Fix yardoc warnings.
Warings:
[warn]: Invalid tag format for @return in file `lib/grpc/core/time_consts.rb` near line 36
[warn]: @param tag has duplicate parameter name: set_input_stream_done
in file `lib/grpc/generic/bidi_call.rb' near line 70
[warn]: Unknown tag @result in file `lib/grpc/generic/rpc_server.rb` near line 287
[warn]: @param tag has unknown parameter name:
in file `lib/grpc/generic/interceptors.rb' near line 158
[warn]: In file `lib/grpc/generic/rpc_server.rb':217: Cannot resolve link to key: from text:
...{key: val, ..}
[warn]: In file `lib/grpc/generic/rpc_server.rb':217:
Cannot resolve link to key: from text:
...{key: val, ..}
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| | |
Bump 1.8.0-dev to 1.9.0-dev
|
|\ \
| | |
| | | |
Fix a race in ruby server shutdown and cleanup for ruby tests
|
| | | |
|
| |/
|/| |
|
| | |
|
| | |
|
|/
|
|
| |
trailer wasnt set
|
| |
|
|
|
|
| |
status from a grpc::Status
|
|\
| |
| | |
Master version bump to 1.7.x
|
| | |
|
|/
|
|
|
|
|
|
|
|
| |
The old code only caught `StandardError`, which doesn't include
`NotImplementedError`. Despite the name, this error indicates a failure
of low-level OS interaction rather than unimplemented user code.
Any errors not caught by this section will cause the server to
terminate, which is generally undesirable because it might be happily
handling other requests.
|
|
|
|
| |
error
|
| |
|
|\
| |
| | |
Release resources more eagerly on ruby server
|
| |
| |
| |
| | |
calls
|
| | |
|
| | |
|
|/ |
|
|\
| |
| | |
Fix typos
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
`require-relative` breaks Rubygems' ability to use the arch-specific
directory in `extensions`. When building grpc extensions from source,
we're left with a lot of intermediate object files and a duplicate
shared object file as well. This space can be reclaimed by finding these
object files inside the `gems` subdirectory of the installation
location, while leaving the shared object file in the `extensions`
subdirectory. See the comments at
https://github.com/rubygems/rubygems/issues/926 for more on this
behavior, which has been present in Rubygems for years.
By using `require` instead, those of us who build from source can
reclaim space consumed by duplicate and intermediate files, which
amounts to a savings of 46MB (in a build of 1.3.2 on Alpine
Linux). This is helpful when trying to minimize the size of a Docker
image.
I'm unclear on whether or not the reclaiming of this space can be
automated as part of the build process. If so, it may be worth
considering as a separate effort.
|
| | |
|
| | |
|