library · inferred from evidence
gRPC
A high-performance RPC framework referenced in the context of port naming and protocol handshake issues.
- Stale internode gRPC connections after pod termination when using Kubernetes Deployments
How to fix stale internode gRPC connections after pod termination when using Kubernetes Deployments (Temporal). The verified answer from the upstream issue, distilled into steps.
- Satellite error (reading from server: read: connection timed out)
[idelvall (maintainer)]: The read: connection timed out errors when building on a Satellite were caused by the client stripping the gRPC status code from the error. Fixed and released in v0.7.19: upgrade earthly.
- [Bug] Metadata string value returned as datetime.date
How to fix '[Bug] Metadata string value returned as datetime.date' in Pinecone, straight from the verified resolution in gh:pinecone-io/python-sdk#161. Root cause plus what to change.
- protobuf 3.19.3 is a bit outdated and due to this I can not install pinecone[grpc]
How to fix 'protobuf 3.19.3 is a bit outdated and due to this I can not install pinecone[grpc]' in Pinecone, straight from the verified resolution in gh:pinecone-io/python-sdk#151. Root cause plus what to change.
- Very high server load average after upgrading Qdrant to v1.14.0 with batch search
The maintainers reproduced and confirmed this as a regression in v1.14.0 related to batched search (suspected PR #6326). The fix shipped in the v1.14.1 patch release; maintainer timvisee confirmed on the thread that 1.14.1 includes the patc
- CockroachDB on Kubernetes with Istio: "connection refused" - how to run insecure statefulset with istio mTLS
Rename the 26257 port from grpc to tcp in the CockroachDB Service and StatefulSet manifests so the Istio sidecar treats the traffic as plain TCP instead of trying gRPC protocol sniffing. That is the fix multiple users confirmed (one via mik
- Aserto Node library drags in express dependencies for users on fastify
What this covers: The aserto-node library bundles express helpers, forcing express and its dependency tree on users who use fastify instead. The fix that worked: The team shipped exactly that as a new package: topaz-node, available at asert