Chiebot-Mirror/grpc - grpc - Gitea: Git with a cup of tea

Commit Graph

Author	SHA1	Message	Date
Esun Kim	4e396883d4	Update by review	5 years ago
Esun Kim	1e74c102cd	Add GRPC_USE_ABSL flag	5 years ago
Lidi Zheng	c34bef4ca4	Format all Bazel files with buildifier	5 years ago
Richard Belleville	444d5b7760	Revert "Reuse the definition already in the bazel/ directory" Turns out that putting this in the main build definition starklark file means that our users will also incur a dependency on the repo rule. That's no bueno. This reverts commit `78e443b4f6`.	5 years ago
Richard Belleville	78e443b4f6	Reuse the definition already in the bazel/ directory	5 years ago
Richard Belleville	4c8935761d	Add wrapper layer for Blaze	5 years ago
Esun Kim	8086d8ee42	Update abseil-cpp to HEAD	5 years ago
Eytan Kidron	6aa41ee760	Removed LARGE_MACHINE from bazel/grpc_build_system.bzl	5 years ago
vam-google	91c0d093bd	Fix unnecessary dependency and add new line	5 years ago
vam-google	5d9eeb34fc	Address PR feedback. Also add a dummy plugin.	5 years ago
Eytan Kidron	c97ce9057b	Simplify the platform and constraints settings for remote execution * Remove the toolchains //third_party/toolchains:local and //third_party/toolchains:local_large. * Remove the platforms :rbe_ubuntu1604, :rbe_ubuntu1604_large, :local and :local_large. * No longer inherit from @rbe_default//config:platform but instead use it directly. It is now the only non-windows platform. * When creating @rbe_default//config:platform directly with rbe_autoconfig, set dockerAddCapabilities and dockerPrivileged directly in the exec_properties field. No need to set dockerNetwork to "off" and dockerSiblingContainers to false since these are the defaults. * Also set gceMachineType = "n1-highmem-2" on the default platform. This value can be overridden by specific targets that want to use LARGE_MACHINE. * Use create_exec_properties_dict where appropriate. * Use custom_exec_properties to define LARGE_MACHINE. I wasn't able to test thoroughly that this PR does not break any existing targets. I was not able to run anything on windows/mac and I also don't have access to gRPC's RBE setup.	5 years ago
Jan Tattermusch	e5e3f70a1a	Revert "Revert "Upgrade to bazel 1.0.0""	5 years ago
vam-google	d27cbe443a	Add an ability to call an optional custom plugin for py_proto_library and py_grpc_library. This is needed for googleapis (it uses a special doc formatter plugin to fix and pritify the docs (comments) in the generated stubs).	5 years ago
Juanli Shen	0a736c0d37	Update envoy API to HEAD	5 years ago
Esun Kim	21df81dfc2	Squashed 'third_party/upb/' content from commit 9effcbcb27 git-subtree-dir: third_party/upb git-subtree-split: 9effcbcb27f0a665f9f345030188c0b291e32482	5 years ago
Jan Tattermusch	675732cb29	update third_party/boringssl-with-bazel to latest master-with-bazel branch	5 years ago
Esun Kim	4d88f39d54	Squashed 'third_party/upb/' content from commit 9effcbcb27 git-subtree-dir: third_party/upb git-subtree-split: 9effcbcb27f0a665f9f345030188c0b291e32482	5 years ago
vam-google	dbe62a6e6c	Switch to `py2and3_test` rule from py_test	5 years ago
vam-google	564dc771dc	Return PyInfo provider with imports from _gen rules and pass that as deps in py_library. This allows hiding _virtual_imports include path from the surface.	5 years ago
Nicolas Noble	04d7e0d11f	Revert "Upgrade to bazel 1.0.0"	5 years ago
Danjie Wenren	93e8830070	Address comments. - Fix sanit test check_bazel_workspace.py. - Use the new `grpc_extra_deps` in the Bazel workspace test.	5 years ago
Jan Tattermusch	74ade125f2	toolchains no longer support machine types	5 years ago
Jan Tattermusch	396d8c07f6	update bazel toolchains to 1.0.0	5 years ago
Danjie Wenren	c22c215ea5	Move extra dependencies out of WORKSPACE to its own macro. This could be useful for projects that use gRPC as an external repository. This could not be done within the same grpc_deps.bzl due to the problem discussed in - https://github.com/bazelbuild/bazel/issues/1550 - https://github.com/bazelbuild/bazel/issues/1943	5 years ago
Jan Tattermusch	0460b9bb4b	fixup	5 years ago
Jan Tattermusch	b77cb8ae7c	replace git_repository occurence by http_archive	5 years ago
Esun Kim	1743519aa9	Activate C++ stdlib	5 years ago
Jan Tattermusch	3ece581720	win RBE tests with uses_polling=True need to run as well	5 years ago
Jan Tattermusch	5b9e08d9a3	try updating bazel toolchains	5 years ago
Jan Tattermusch	6822d9a779	correctly generate tests for bazel tests that dont use polling	5 years ago
Jan Tattermusch	4a539ffb7c	regenerate	5 years ago
Richard Belleville	1d1aebb920	Remove unused import	5 years ago
Rafi Kamal	7c85e29076	Add protobuf_deps to python_test_repo WORKSPACE	5 years ago
Esun Kim	300077aac1	Update upb to HEAD	5 years ago
Juanli Shen	0a3b333c04	Fix internal warning	5 years ago
Richard Belleville	c11539f79e	Document kwargs	5 years ago
Richard Belleville	ecf7274aaa	Add docstring to py2and3_test	5 years ago
vam	59f909df79	address PR feedback	5 years ago
vam	461c053c37	[bazel][python] Support _virtual_imports input for py_proto_library and py_grpc_library rules `proto_library` targets are used as deps for `py_proto_library` and `py_grpc_library` rules. The `proto_library` targets can be configured using `import_prefix` and/or `strip_import_prefix` (which essentially move original location of the proto file and, as result, affects import path within proto files themselves and in the generated language-specific stubs). The biggest question to answer when generating stubs from moved protos is where to put result (this decision affects all downstream rules as well, because the location of file affects its import path). This PR tries to follow same logic as the native `cc_proto_library` (created and maintained by Bazel team). For example, if we have `firestore.proto` file, which is located under `google/firestore/v1beta1` Bazel package and want to move it under `google/cloud/firestore_v1beta1/proto` (this is axactly what happens in googleapis repository), it can be configured the following way: ```bzl proto_library( name = "firestore_moved_proto", srcs = ["firestore.proto"], import_prefix = "google/cloud/firestore_v1beta1/proto", strip_import_prefix = "google/firestore/v1beta1", ) ``` The rule above will first generate virtual `.proto` files (under new location) and only after that generate a binary descriptor from them. Specifically it will generate the following "virtual" file under `_virtual_imports` subdirectory of same package: ``` bazel-bin/google/firestore/v1beta1/_virtual_imports/firestore_moved_proto/google/cloud/firestore_v1beta1/proto/common.proto ``` When supplied to `cc_proto_library`, like the following: ```bzl cc_proto_library( name = "firestore_moved_cc_proto", deps = ["firestore_moved_proto"], ) ``` The rule will generate .cc and .h files like the following: ``` bazel-bin/google/firestore/v1beta1/_virtual_imports/firestore_moved_proto/google/cloud/firestore_v1beta1/proto/firestore.pb.h bazel-bin/google/firestore/v1beta1/_virtual_imports/firestore_moved_proto/google/cloud/firestore_v1beta1/proto/firestore.pb.cc ``` Notice, that each generated `.cc` and `.h` file is prefixed with `_virtual_imports/<name_of_proto_library_target>`. The python rules try to do same thing, so for the following py_proto_library rule: ```bzl py_proto_library( name = "firestore_moved_py_proto", deps = [":firestore_moved_proto"], ) ``` It wil generate the following file: ``` bazel-bin/google/firestore/v1beta1/_virtual_imports/firestore_moved_proto/google/cloud/firestore_v1beta1/proto/firestore_pb2.py ``` I.e in same path as cc_proto_library. This all woks, but an annoying part is that to use the generated library in some other py_library, in needs to specify the "_virtual_imports/proto_target" path as its "includes" parameter (and I can't make it better than that). Another option would be to skeep the `_virtual_imports/<name_of_proto_library_target>` the suffix for the generated python stubs, which will make the path look like the following: ``` bazel-bin/google/firestore/v1beta1/google/cloud/firestore_v1beta1/proto/firestore_pb2.py ``` That will make using generated stubs simpler and cleaner (no need to specify imports argument), but it will make it inconsistent with the other rules (like cc_proto_library) and also more susseptible to naming conflicts (if there is already something under the generated path).	5 years ago
Richard Belleville	d649880044	Add strip_prefix to python protoc plugin and py_grpc_library	5 years ago
Richard Belleville	9c4de3a983	Move reference to external workspace to OSS-specific file	5 years ago
Richard Belleville	1444cd1dd3	Revert "Revert "Merge pull request #20097 from gnossen/dual_version_python_tests"" This reverts commit `24c562dbaa`.	5 years ago
Richard Belleville	24c562dbaa	Revert "Merge pull request #20097 from gnossen/dual_version_python_tests" This reverts commit `c9c847f334`, reversing changes made to `07ba4de392`.	5 years ago
Jan Tattermusch	7357f63c09	update check_submodules.sh and grpc_deps.bzl	5 years ago
Muxi Yan	96c11d153f	Revert "Revert #19704 and #20060"	5 years ago
Muxi Yan	d1f4456dc6	Revert "Merge pull request #19704 from muxi/isolate-call-implementation-2" This reverts commit `ac5f8062dd`, reversing changes made to `8ae549431c`.	5 years ago
Richard Belleville	d3cd387e03	Bump rules_apple	5 years ago
Jan Tattermusch	abc384164a	fix kwargs syntax error	5 years ago
Richard Belleville	6dfa96524d	Fix failing CPP test	5 years ago
Jan Tattermusch	b7667478cf	bump bazel version to 0.27	5 years ago

1 2 3 4 5 ...

441 Commits (7d6b12fe73b15bdb02dbc6154d9cfa0f1f6d14ea)