aboutsummaryrefslogtreecommitdiffhomepage
path: root/src/ruby/lib
Commit message (Collapse)AuthorAge
* Regenerate projectsGravatar Sanjay Pujare2019-01-03
|
* ruby-sigint ready to be merged!Gravatar Tommy Chen2018-12-26
|
* Return unimplementedGravatar ganmacs2018-11-25
| | | | when calling a method which is server_streamer and is not implemented by user
* Regenerate projectsGravatar Muxi Yan2018-11-19
|
* Regenerate projectsGravatar Stanley Cheung2018-10-08
|
* Merge pull request #16593 from iguchi1124/remove-duplicate-errorGravatar apolcyn2018-10-08
|\ | | | | Ruby: remove duplicated `Unimplemented` error definition
* \ Merge pull request #16642 from tenderlove/send-instead-of-methodGravatar apolcyn2018-09-20
|\ \ | | | | | | Switch to `send` instead of `method(...).call`
| * | Switch to `send` instead of `method(...).call`Gravatar Aaron Patterson2018-09-17
| | | | | | | | | | | | | | | | | | | | | 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.
| | * Remove duplicate `Unimplemented` error definitionGravatar Shota Iguchi2018-09-10
| |/
* / Rescue GRPC::Core::CallError not to kill the worker threadsGravatar ganmacs2018-08-28
|/
* Regenerate projectsGravatar Juanli Shen2018-08-27
|
* Regenerate projectsGravatar Srini Polavarapu2018-07-19
|
* GRPC::Cancelled should be occured when calling Enumrable#next on canceled callGravatar ganmacs2018-06-23
|
* Delete unused @metadata_tagGravatar ganmacs2018-06-18
|
* Merge pull request #15755 from ganmacs/unify-duplicated-methodGravatar apolcyn2018-06-14
|\ | | | | Unify nearly same methods
| * Unify nearly same methodGravatar ganmacs2018-06-14
| | | | | | | | | | | | `@call` instance variable is same in ActiveCall#merge_metadata_and_send_if_not_already_sent and ActiveCall#send_initial_metadata.
* | Regenrate projectsGravatar Srini Polavarapu2018-06-08
|/
* Add more details to a resource exhausted ruby errorGravatar Alexander Polcyn2018-05-18
|
* Regenerate projectsGravatar Mehrdad Afshari2018-05-02
|
* Merge pull request #14922 from apolcyn/ruby_bidi_errorGravatar apolcyn2018-04-04
|\ | | | | Don't raise call errors for failed reads or writes of ruby bidi streams
* | Regenerate projectsGravatar Mehrdad Afshari2018-04-04
| |
| * Never throw CallErrors for failed bidi reads or writesGravatar Alexander Polcyn2018-04-03
|/
* Fix ruby documentGravatar nownabe2018-03-13
| | | | | | | | | | | | | | | | | | | | | | | | | 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, ..}
* Regenerate projectsGravatar Mehrdad Afshari2018-02-22
|
* Guarantee no race between ruby server's shutdown_and_notify and destroyGravatar Alexander Polcyn2018-02-06
|
* Refactor ruby server shutdown to fix a raceGravatar Alexander Polcyn2018-01-22
|
* Regenerate projectsGravatar Mehrdad Afshari2018-01-19
|
* Merge pull request #13515 from mehrdada/bump-master-versionGravatar Mehrdad Afshari2017-11-28
|\ | | | | Bump 1.8.0-dev to 1.9.0-dev
* \ Merge pull request #12710 from apolcyn/speedup_ruby_end2end_testsGravatar apolcyn2017-11-27
|\ \ | | | | | | Fix a race in ruby server shutdown and cleanup for ruby tests
| * | Remove some sleeps in ruby tests and fix test server shutdownGravatar Alex Polcyn2017-11-27
| | |
| | * Bump 1.8.0-dev to 1.9.0-devGravatar Mehrdad Afshari2017-11-27
| |/ |/|
* | remove use of keyword argsGravatar Alexander Polcyn2017-10-31
| |
* | Update version to 1.8.0-dev, update g word to 'generous'Gravatar murgatroid992017-10-02
| |
* | return nil from google rpc status conversion if the grpc-status-details-bin ↵Gravatar Alexander Polcyn2017-09-26
|/ | | | trailer wasnt set
* Add Ruby server interceptorsGravatar Shaun McCormick2017-09-25
|
* add a client side utility for extracting a google rpcGravatar Alexander Polcyn2017-09-18
| | | | status from a grpc::Status
* Merge pull request #12213 from dgquintas/v1.7.x-version-bumpGravatar David G. Quintas2017-08-17
|\ | | | | Master version bump to 1.7.x
| * Master version bump to 1.7.xGravatar David Garcia Quintas2017-08-16
| |
* | Catch NotImplementedError exceptions and forward them to the client.Gravatar John Millikin2017-08-16
|/ | | | | | | | | | 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.
* cancel calls with an error message when bidi write loop fails with userGravatar Alexander Polcyn2017-08-07
| | | | error
* properly finish bidi calls when there is an initial errorGravatar Alexander Polcyn2017-07-27
|
* Merge pull request #11764 from apolcyn/fix_ruby_socket_leakGravatar apolcyn2017-07-20
|\ | | | | Release resources more eagerly on ruby server
| * add missing fields on server call context and improve robustness of finished ↵Gravatar Alexander Polcyn2017-07-19
| | | | | | | | calls
| * make sure that client-side view of calls is robustGravatar Alexander Polcyn2017-07-18
| |
| * dont wait for gc to destroy calls on ruby serverGravatar Alexander Polcyn2017-07-13
| |
* | remove an unused methodGravatar Alexander Polcyn2017-07-11
|/
* Merge pull request #9823 from mjkim/fix_unkownGravatar Mehrdad Afshari2017-06-12
|\ | | | | Fix typos
* | auto-fix most of licensesGravatar Jan Tattermusch2017-06-08
| |
* | master bumped to 1.5.xGravatar David Garcia Quintas2017-05-30
| |
* | Remove unnecessary require_relativeGravatar Ernie Miller2017-05-12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `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.
generated by cgit v1.2.3 (git 2.39.1) at 2024-06-09 05:23:54 +0000