| Commit message (Collapse) | Author | Age |
|\ |
|
| |\
| | |
| | | |
Move a script which has a pre-requirement to outside of spec
|
| | |
| | |
| | |
| | | |
And make it to be execute when using `./tools/run_tests/run_tests.py -l ruby`
|
|/ / |
|
|\ \
| | |
| | | |
Pin gevent
|
| | | |
|
| | | |
|
| | | |
|
| |/
|/| |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
PHP: add persistent list upper bounnd check
change upper bound from global to each target
add ref/unreef; Only delete ref_count=0; make the code cleaner
persistent map update after review
u2nd pdate after the review
|
| | |
|
| | |
|
|/
|
|
|
|
|
|
|
|
| |
See https://github.com/grpc/grpc/issues/15253 for more context. The
original behavior when running Python tests is to try to create a
virtual env with the specifed Python version. If there is an issue
with that, fallback to the system's default Python version. This leads to
misleading test results, so removing the fallback and failing the test
when virtual env fails to instantiate the specified Python version is
the new behavior.
|
| |
|
|
|
|
|
|
| |
With the upgrade of Kokoro macOS workers to Sierra, not all versions of
Python have a pip version new enough to have TLSv1.2. This change should
make macOS Python testing more resilient to environment changes.
|
| |
|
|
|
|
|
|
|
| |
Fix for issue #14815. Pinning to 9.0.3 doesn't work because pip fails to
recognize that as a valid version. Newer versions of pip have a fallback
on macOS to use SecureTransport instead of their outdated OpenSSL that
doesn't support TLSv1.2.
|
|\
| |
| | |
Updates the ruby generator RubyTypeOf to correctly account for underscores in packages
|
|\ \
| | |
| | | |
Use GRPC_RB_MEMSIZE_UNAVAILABLE in grpc_rb_md_ary_data_type
|
| | | |
|
|/ /
| |
| |
| |
| | |
Because some cpp code ends up leaking into cython, we change
the cython generator to generate cpp code.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
in packages
Prior to this change, when the ruby generator tried to reference an entity that was not part of the same package
(or a direct parent package) and the package contains underscores,
the result would simply uppercase the first character.
It should however uppercase each letter that proceeds an underscore and remove underscores.
i.e.
```
package my_package.service;
import "my_package/data.proto";
service MyService {
rpc Test (data.Request) returns data.Response {}
}
```
Was
```ruby
# ...
rpc :Test, My_package::Data::REquest, My_package::Data::Response
# ...
```
Should be:
```ruby
# ...
rpc :Test, MyPackage::Data::REquest, My_package::Data::Response
# ...
```
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
|/ |
|
| |
|
|
|
|
|
|
| |
This removes all of the node code and tests from the repo, along with the
scripts for running Node unit tests, performance tests, and artifact builds.
The scripts for running tests from the grpc-node repository are untouched.
|
| |
|
|\
| |
| | |
Add testing of grpc-node for Linux and MacOS
|
| | |
|
|/ |
|
| |
|