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

Commit Graph

Author	SHA1	Message	Date
Jan Tattermusch	e816aa34af	buildifier format	4 years ago
Jan Tattermusch	7533b4bfb4	RBE: rely on labels to select the right worker pool	4 years ago
Jan Tattermusch	cdb3d823fd	migrate windows RBE to win2019 pool	5 years ago
Richard Belleville	3d876a656f	Buildifier	5 years ago
Lidi Zheng	c34bef4ca4	Format all Bazel files with buildifier	5 years ago
Richard Belleville	4b49a95801	Fix internal lint warnings	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
Esun Kim	21df81dfc2	Squashed 'third_party/upb/' content from commit 9effcbcb27 git-subtree-dir: third_party/upb git-subtree-split: 9effcbcb27f0a665f9f345030188c0b291e32482	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
Nicolas Noble	04d7e0d11f	Revert "Upgrade to bazel 1.0.0"	5 years ago
Jan Tattermusch	ea3fd924bd	fixup rbe_default	5 years ago
Jan Tattermusch	c2447a0308	switch RBE builds to use exec_properties	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
Rafi Kamal	fac04ffe6e	Add protobuf_deps to WORKSPACE See https://github.com/grpc/grpc/pull/20224#issuecomment-531355209	5 years ago
Richard Belleville	3638167e40	Call grpc_python_deps() from grpc_deps().	5 years ago
Richard Belleville	7b2c8c27b0	Separate py_grpc_library and py_proto_library. By popular demand, we'll now be offering separate py_grpc_library and py_proto_library targets sharing the same interface as within google3. This change necessitated some modifications to how we pull in our own Python-level dependencies and how we make those available to those pulling in our project via Bazel. There is now a grpc_python_deps() Bazel workspace rule that pulls in the appropriate dependencies, which should be called from the client project's WORKSPACE file. A test has been added to the bazel/test/ directory to verify that this behavior works as intended. It's worth noting that the protobuf repository's usage of Starlark bind() caused a great deal of trouble in ensuring that we could also pull in six. This change also required a change in the way generated proto code is imported in the channelz and health-check modules, as well as in their associated tests. We were importing them two different ways, each relative. This resulted in two different module objects being imported into the process, which were incompatible. I am not sure exactly what caused this behavior to begin, as this should have been possible before this PR. As a workaround, I am simply trying two different absolute imports and using the one that works. This should function both inside and outside of Bazel environments.	5 years ago
Tony Lu	44868ae12a	Starting a new branch with same changes from https://github.com/grpc/grpc/pull/19621	5 years ago
Marcel Hlopko	49f0fb9035	Migrate from dep.proto to dep[ProtoInfo]	6 years ago
Nicolas "Pixel" Noble	8de64087a3	Clean bazel 0.26 upgrade.	6 years ago
Moiz Haidry	49e7f4b2e4	Added more rules to resolve deps	6 years ago
Moiz Haidry	4995670257	Add support to import envoy protos	6 years ago
Moiz Haidry	6c3e3aeb77	Removed git repo from WORKSPACE as that was the incorrect location. Added the code to grpc_deps.bzl instead	6 years ago
Moiz Haidry	e8a18969bb	Added upb repo to grpc workspace	6 years ago
Richard Belleville	930cec4e27	Revert "Merge pull request #18912 from grpc/revert-bazel-changes" This reverts commit `c9a259aa3a`, reversing changes made to `9c882bc725`.	6 years ago
Richard Belleville	50b5240d0a	Revert "Merge pull request #18859 from grpc/internal_py_proto_library" This reverts commit `5b720f19c1`, reversing changes made to `a64ae3c0d5`.	6 years ago
Richard Belleville	05f37c8143	Remove dependency on pubref/rules_proto. This commit resolves #18331. This commit resolves #18256. This commit resolves... another TODO that apparently didn't have an associated github issue. We swap out pubref's implementation of py_proto_library with our own, which more closely mirrors the interface of the internal py_proto_library, taking the descriptor file output of a proto_library rule as input. One minor change in behavior was introduced for simplicity. When a py_proto_library depends on a proto_library with a source proto file in a subdirectory of the bazel package, the import module of the resultant python library will reflect the package, not the full directory of the proto file, including both the bazel package and the subdirectories, as pubref did previously. This behavior also more closely mirrors google internal behavior. This commit also introduces a slightly more stringent bazel format script. Buildifier on its own will not take care of long lines, but by running yapf first, we end up with a more legible file. At the moment, there is no sanity check associated with this formatter.	6 years ago
Bill Feng	5158c3db27	naming update, documentation fix	6 years ago
Bill Feng	df89d8e157	bazel RBE Windows build	6 years ago
Richard Belleville	615c95ed5c	Mitigate #18256	6 years ago
Nicolas Lopez	bdbe0483b0	update docs	6 years ago
Nicolas Lopez	a9ffc03d1b	remove ubsan rbe_autoconfig target	6 years ago
Nicolas Lopez	ad4926d5c6	avoid local runs from accessing remote platforms This should fix Bazel Basic Tests for Python (Local) and other local CI runs that are now failing. I also have a plan to fix Bazel RBE Opt C/C++. Bazel RBE UBSAN C/C++ might need to wait for gRPC to upgrade to using 0.23.0	6 years ago
Nicolas Lopez	d6dbaeee74	doc fixes	6 years ago
Nicolas Lopez	d1640057f2	use rbe_autoconfig	6 years ago
Nicolas "Pixel" Noble	2e139e35fc	Bazel 0.20.0 workspace fixes.	6 years ago
Lidi Zheng	8bed44b2c4	Make WORKSPACE compatible with Bazel 0.20.0 for Python	6 years ago
Nicolas Noble	dc930c7868	Workarounding bazelbuild/bazel#6831 This will take care of the bazel crash until we have a proper fix upstream.	6 years ago
Nicolas "Pixel" Noble	f0fbee5932	Bazel 0.20.0 workspace fixes.	6 years ago
Bill Feng	1e53e3c17f	added back platform registration to WORKSPACE	6 years ago
Bill Feng	70f9992d77	modified execution platform registration, added host platform	6 years ago
Bill Feng	a548f1cc64	fixed typo on WORKSPACE file	6 years ago
Bill Feng	c04583f647	registered toolchain and platform	6 years ago
Naresh	873e0757cb	Bazel rules for Python grpcio_health_checking Add Bazel rules for building and testing grpcio_health_checking. An unofficial fork for rules_protobuf is used for now as it incorporates a change (#196 by duduko on the upstream repo pubref/rules_protobuf) which allows the protoc compiler to compile generated protos too. This was not merged because the change was failing for golang, but works as expected for Python. This is needed because grpcio_health_checking fetches it's proto file from a different directory (previously achived through setup.py) and thus needs to be moved to the required location within bazel-genfiles using a genrule.	6 years ago
Naresh	11f199e34d	Workspace changes to build gRPC Python with Bazel - Include new rules from bazelbuild/rules_python, which allow for importing pip dependencies with Bazel. - Make Cython BUILD file visible to WORKSPACE. - Use a custom requirements file for Bazel python. This is added to allow for requirements previously added only during build steps.	6 years ago
Alex Polcyn	aa56034b58	Add python bazel deps needed to run resolver component tests	7 years ago
Ning Ren	4856782510	Packs contents of WORKSPACE into a bzl function, so that it can be resued by other projects, and simplifies cares build.	7 years ago
Ning Ren	174e02ae3e	Packs contents of WORKSPACE into a bzl function, so that it can be resued by other projects, and simplifies cares build.	7 years ago
Adele Zhou	0384127aa8	Copy key data	7 years ago
Adele Zhou	b9cb3379d5	Add bazel_toolchains	7 years ago

1 2

78 Commits (004480e706324c9e7ead31ba06682720d999811e)