platform · inferred from evidence
GCP
Google Cloud Platform, a suite of cloud computing services.
- Cloud SQL Proxy: "couldn't connect ... dial tcp ...:3307: getsockopt: connection timed out"
Connecting to a Cloud SQL MySQL instance through the proxy from a GCE VM hung forever, and the proxy log showed: couldn't connect to INSTANCE: dial tcp IP:3307: getsockopt: connection timed out. The VM's service account had the Cloud SQL Cl
- Flipt 1.9.0 Postgres dial tcp lookup postgres device or resource busy
Upgrading Flipt from 1.8.3 to 1.9.0 or 1.10.0 breaks Postgres connectivity in Kubernetes with: getting db driver for: postgres: dial tcp: lookup postgres.database.svc.cluster.local: device or resource busy. Versions 1.8.2 and 1.8.3 worked f
- ChromaDB DuplicateIDError on memgpt load (duplicate embedding IDs)
Running `memgpt load` with a large .jsonl dataset failed with "chromadb.errors.DuplicateIDError: Expected IDs to be unique, found duplicates of: ...". The dataset produced duplicate embedding IDs on load, and Chroma's `validate_ids` rejecte
- Google Secret Manager Could not load the default credentials from AWS Lambda nodejs client
Creating secrets in GCP Secret Manager from an AWS Lambda using the Node.js client fails with: Error: Could not load the default credentials, even when projectId and the path to a service-account JSON key file are passed to the SecretManage
- `google-cloud-documentai` imports fail in GCP notebooks: kernel Python does not match pip
After `pip install google-cloud-documentai==0.3.0` (successful install), I get: `ImportError: cannot import name 'documentai_v1beta3' from 'google.cloud' (unknown location)`. This happens in multiple environments, including a GCP notebook i
- Crawlee SQLite "disk I/O error" in container (Cloud Run)
A Crawlee/Apify crawler works locally on macOS but throws SQLite `disk I/O error` when creating the RequestQueue inside a container on Google Cloud Run. Filesystem writes themselves work fine in the container, so it is not a missing volume