-
Notifications
You must be signed in to change notification settings - Fork 10.4k
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
Improvements to Debian packaging targeting unstable #1905
Conversation
Use consistent port numbers
…ements Various tweaks to improve server stability
Update C# readme
Updates gRPC Ruby to 0.9.0
Updated to version 0.9.0a0.
Workaround: Prevent threads sitting in epoll forever
Correct the test request/response size, to be consistent with the tes…
Updated Node.js version to 0.9.0
Sync Python version to rest of project
OpenSSL offers 3 ways to express the same thing: * BIO_ctrl_pending(BIO *) * BIO_ctrl(BIO *, BIO_CTRL_PENDING, 0, NULL) * BIO_pending(BIO *) BoringSSL standardizes on the last of these.
Updating our protobuf submodule to alpha3
It also clarifies the Cocoapods part for people new to Cocoapods, and links to the sample app for examples on how to use the generated library.
…tions Add simpler instructions for ObjC (using Homebrew)
Standardize on |BIO_pending| and |BIO_wpending|.
Added tracing for grpc_server_request_call
Replaced underscore and underscore.string modules with lodash
Increase RPC timeout in _links_test.py.
Redirect build_python.sh to requirements.txt.
Fix jenkins build on windows
Expose gpr_asprintf and gpr_strdup
Some compilers don't like C99.
Add ability to override default thread pool
Manually cherry-picked from gcsideal's pull request commit 02ba43d
Manual cherry pick from Laszlo's commit 8e8b191
These don't seem to need to be included, as upstream appears to be doing the right thing.
We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for the commit author(s). If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google. |
Thanks for your pull request. It looks like this may be your first contribution to a Google open source project, in which case you'll need to sign a Contributor License Agreement (CLA). 📝 Please visit https://cla.developers.google.com/ to sign. Once you've signed, please reply here (e.g.
|
Grumble. I'll get this right in a minute... |
Contributions from Laszlo Boszormenyi, who is the other Debian Developer who was independently working packaging gRPC.
Some cleanup, make rebuildable.
This is for #662