google-cloud-cpp icon indicating copy to clipboard operation
google-cloud-cpp copied to clipboard

C++ Client Libraries for Google Cloud Services

Results 531 google-cloud-cpp issues
Sort by recently updated
recently updated
newest added

This change is [](https://reviewable.io/reviews/googleapis/google-cloud-cpp/14280)

api: pubsub
samples

This change is [](https://reviewable.io/reviews/googleapis/google-cloud-cpp/14278)

Fixes #13998 - - - This change is [](https://reviewable.io/reviews/googleapis/google-cloud-cpp/14270)

Googlers can see: go/cloud-cxx:s-slash-tracing-logging-options --- I say we adopt OpenTelemetry’s naming scheme for our telemetry interfaces. This basically means s/Tracing/Logging/ for these types. We will introduce new types using “Logging”...

type: cleanup

This change is [](https://reviewable.io/reviews/googleapis/google-cloud-cpp/14420)

api: storage

Part of the work for #11485 - - - This change is [](https://reviewable.io/reviews/googleapis/google-cloud-cpp/14401)

In `v1.16.0`, OpenTelemetry started compiling with Abseil all the time with Bazel. See https://github.com/open-telemetry/opentelemetry-cpp/pull/2679 This means their `--io_opentelemetry_cpp//api:with_abseil` flag is now obsolete. Yay. That is good moving forward. They plan...

I started noticing these after the gRPC 1.65.0 update. For example: * GCB: https://console.cloud.google.com/cloud-build/builds;region=us-east1/081483b5-3472-4b85-975a-829afc18b562;tab=detail?project=cloud-cpp-testing-resources * Raw: https://storage.googleapis.com/cloud-cpp-community-publiclogs/logs/google-cloud-cpp/main/2983243965aa3a9974d81bef30a101b322d24e86/demo-ubuntu-jammy-demo-install/log-081483b5-3472-4b85-975a-829afc18b562.txt

type: cleanup
cpp: flake

Certain symbols (e.g. `MakeGoogleDefaultCredentials()`) are missing from our reference docs. The missing types have an `@ingroup foo`. Doxygen renders these as `` tags, which we skip in our docfx ->...

type: cleanup
cpp: operator
cpp: docfx

As we need to keep `bigquery_job` separate from the existing `bigquery` target to avoid introducing REST dependencies, this required some massaging of our ci builds and generated inputs into those...