Skip to content
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

[export] [grpc][Gpr_To_Absl_Logging] Migrating from gpr to absl logging - gpr_log #36621

Merged
merged 1 commit into from
May 16, 2024

Conversation

copybara-service[bot]
Copy link

[export] [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 :
  4. If the above mapping is correct.
  5. 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.

DO NOT SUBMIT. This PR is for testing purposes only. cl/633802446

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.

PiperOrigin-RevId: 634278682
@copybara-service copybara-service bot merged commit bb201db into master May 16, 2024
@copybara-service copybara-service bot deleted the test_633802446 branch May 16, 2024 09:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants