google-cloud-cpp
google-cloud-cpp copied to clipboard
C++ Client Libraries for Google Cloud Services
The GCS API supports (or soon will support) an idempotency token header. The header allows GCS to detect if a request is a duplicate, and returns the same value for...
The more interesting bit is this: ``` UNAVAILABLE: Error in non-idempotent operation: failed to connect to all addresses; last error: UNKNOWN: ipv4:127.0.0.1:8787: Invalid argument error_info={reason=, domain=, metadata={gcloud-cpp.retry.function=CreateDatabase, gcloud-cpp.retry.reason=non-idempotent, gcloud-cpp.retry.original-message=failed to...
I have seen this pattern before, but the most damming evidence is: ``` EMULATOR_PID=25281 -.+. /workspace//google/cloud/bigtable/tools/run_emulator_utils.sh: line 28: kill: (25281) - No such process ``` GCB: https://console.cloud.google.com/cloud-build/builds;region=us-east1/debbbe77-c604-492c-8e6c-e1eb6978d643;tab=detail?project=cloud-cpp-testing-resources Raw: https://storage.googleapis.com/cloud-cpp-community-publiclogs/logs/google-cloud-cpp/main/77af2b658664c1ab9d98943e63bdc0725b837515/fedora-34-xsan/log-debbbe77-c604-492c-8e6c-e1eb6978d643.txt
We already do this for custom retry, idempotency policies. Custom `PollingPolicy`s should not be so hard. We need to write the sample: https://github.com/googleapis/google-cloud-cpp/blob/main/generator/internal/sample_generator.cc Update the scaffold with words about the...
- [ ] Add the following attribute: `gcp.project_id` - [ ] Add the server address and port for the [gRPC spans](https://github.com/googleapis/google-cloud-cpp/blob/main/google%2Fcloud%2Finternal%2Fgrpc_opentelemetry.cc#L79-L83)
When comparing the current generation of a proto file to the discovery document being parsed, in `DiscoveryTypeVertex::GetFieldNumber` we interrogate the existence of the `optional` keyword in the .proto file as...
**What component of `google-cloud-cpp` is this feature request for?** Storage Add Support for manual managed folders feature includeFolders. More details see [internal doc](https://docs.google.com/document/d/1bPZtUAI8inzLQhXCpXEDTqSLURPBb2D3zo5DZ9aAXkE/edit?tab=t.0) Note: This is only the manual addition...
It would be ideal if the trace exporter does not block the applications. We would need to generate an async API for `trace_v2::TraceClient::AsyncBatchWriteSpans` We would need to hold the futures...
Please implement the soft delete feature as specified in go/gcs-soft-delete-client-request The operations we need are - [x] Set a soft delete policy on a new or existing bucket - [x]...
* GCB: https://console.cloud.google.com/cloud-build/builds;region=us-east1/e77ca00f-99ba-49d8-bc8e-997f2f116ed5;tab=detail?project=cloud-cpp-testing-resources * Raw: https://storage.googleapis.com/cloud-cpp-community-publiclogs/logs/google-cloud-cpp/11897/2d7c0e227f4347bf7775900139b507f641acc1df/fedora-37-bazel-libcxx/log-e77ca00f-99ba-49d8-bc8e-997f2f116ed5.txt Seems like everything was hunky-dory until we launched the Bigtable emulator and no tests could connect to it. ``` 2023-08-09T19:19:11Z (+3950s): Launching Cloud Bigtable...