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

Author	SHA1	Message	Date
Craig Tiller	f33083bfd5	[promises] Add always inline to basic combinators (#36981 ) These are substitutes for language features and never warrant a new function being created. Significantly boosts the benchmarks in #36946 Closes #36981 COPYBARA_INTEGRATE_REVIEW=https://github.com/grpc/grpc/pull/36981 from ctiller:seqqy `1a075be7e9` PiperOrigin-RevId: 645169296	7 months ago
AJ Heller	c9fdef1317	[logging] Centralize configuration for trace flags (#36576 ) All TraceFlags are now configured in `src/core/lib/debug/trace_flags.yaml`. The format is: ``` my_flag: default: false # the default value; default=false description: Some Description debug_only: false # debug_only flags only work in debug builds; default=false internal: false # internal flags will not show up in documentation; default=false ``` To regenerate the trace flag source code, run `tools/codegen/core/gen_trace_flags.py` (requires mako). This script is also run when sanity checking. This PR also adds two new features: ### Glob-based flag configuration Trace flag configuration now supports `?` (single wildcard character) and `` (one or more wildcard characters). For example, using `GRPC_TRACE='event_engine'` will enable all flags that match that glob. It expands to: * event_engine * event_engine_client_channel_resolver * event_engine_dns * event_engine_endpoint * event_engine_endpoint_data * event_engine_poller ### A cleaner trace-logging macro in abseil logging format If your goal is only to add log statements when the `fault_injection_filter` trace flag is enabled, you can use the macro: ``` GRPC_TRACE_LOG(fault_injection, INFO) << "Filtered:" << 42; ``` When the trace flag is enabled, the the log will show something like this: ``` I0000 00:00:1715733657.430042 16 file.cc:174] Filtered:42 ``` ---- Note: just like with the gpr_log to abseil logging conversion, the pre-existing trace logging usages can be replaced with the new tracing macro across multiple PRs. Closes #36576 PiperOrigin-RevId: 641295215	8 months ago
Tanvi Jagtap	7ab3cebdfc	[grpc][Gpr_To_Absl_Logging] Migrating from gpr to absl logging - gpr_log (#36694 ) [grpc][Gpr_To_Absl_Logging] Migrating from gpr to absl logging - gpr_log In this CL we are migrating from gRPCs own gpr logging mechanism to absl logging mechanism. The intention is to deprecate gpr_log in the future. We have the following mapping 1. gpr_log(GPR_INFO,...) -> LOG(INFO) 2. gpr_log(GPR_ERROR,...) -> LOG(ERROR) 3. gpr_log(GPR_DEBUG,...) -> VLOG(2) Reviewers need to check : 1. If the above mapping is correct. 2. The content of the log is as before. gpr_log format strings did not use string_view or std::string . absl LOG accepts these. So there will be some elimination of string_view and std::string related conversions. This is expected. Closes #36694 COPYBARA_INTEGRATE_REVIEW=https://github.com/grpc/grpc/pull/36694 from tanvi-jagtap:python_codegen_gpr_log `54ee362e3d` PiperOrigin-RevId: 636071998	8 months ago
Tanvi Jagtap	c8f85ff037	[grpc][Gpr_To_Absl_Logging] Migrating from gpr to absl logging GPR_ASSERT (#36445 ) [grpc][Gpr_To_Absl_Logging] Migrating from gpr to absl logging GPR_ASSERT Replacing GPR_ASSERT with absl CHECK These changes have been made using string replacement and regex. Will not be replacing all instances of CHECK with CHECK_EQ , CHECK_NE etc because there are too many callsites. Only ones which are doable using very simple regex with least chance of failure will be replaced. Given that we have 5000+ instances of GPR_ASSERT to edit, Doing it manually is too much work for both the author and reviewer. <!-- If you know who should review your pull request, please assign it to that person, otherwise the pull request would get assigned randomly. If your pull request is for a specific language, please add the appropriate lang label. --> Closes #36445 COPYBARA_INTEGRATE_REVIEW=https://github.com/grpc/grpc/pull/36445 from tanvi-jagtap:tjagtap_assert_tools `c160ab231a` PiperOrigin-RevId: 628093687	9 months ago
Craig Tiller	99cafa32d9	[promises] Expand maximum `Seq` length (#35423 ) Closes #35423 COPYBARA_INTEGRATE_REVIEW=https://github.com/grpc/grpc/pull/35423 from ctiller:seqqy `fea10949d3` PiperOrigin-RevId: 595147939	1 year ago
Craig Tiller	6d35000c17	[promises] Log errors in TrySeq (#35319 ) When an error occurs in `TrySeq`, log the error. Also, in the trace statements, capture the file/line that the sequence was constructed at, and log that with the traces. Closes #35319 COPYBARA_INTEGRATE_REVIEW=https://github.com/grpc/grpc/pull/35319 from ctiller:trace-seq `bc0d47395f` PiperOrigin-RevId: 591999228	1 year ago
Craig Tiller	52369882d8	[promises] Add tracing to seq, join variants (#34401 ) Co-authored-by: ctiller <ctiller@users.noreply.github.com>	1 year ago
Craig Tiller	54651a7168	[promises] New `Seq`, `TrySeq` implementation (#33991 ) Our current implementation of `Seq`, `TrySeq` leverage some complicated template stuff to work, which makes them hard to maintain. I've been thinking about ways to simplify that for some time and had something like this in mind - using a code generator that's at least a little more understandable to code generate most of the complexity into a file that is checkable. Concurrently - I have a cool optimization in mind - but it requires that we can move promises after polling, which is a contract change. I'm going to work through the set of primitives we have in the coming weeks and change that contract to enable the optimization. --------- Co-authored-by: ctiller <ctiller@users.noreply.github.com>	1 year ago