Yahya Jirari
Yahya Jirari
I can confirm that using the 2.0.0 pre release version fixed my problem when using "socket.io": "4.5.1",
Does the rust port obscure the creation order or does it have the same problem as the original cuid v1 implementation in this regard ? If no, I really think...
Also facing the same issue, with a pgbouncer deployed on Google Compute Engine and a Google Cloud SQL postgresql instance. @alexghattas @Abhinav0449 did tuning connect_timeout still workout fine for you...
Any news on this ? This creates a very scary bug when using extensions to do a generic history / audit log
@Jolg42 Not exactly the same setup but i believe the root problem is the same. Here is a simple reproduction: https://github.com/whygee-dev/client-extensions-tx-bug-reproduction
@AgustLuj facing the same issue, did you have any luck with solving it ?
Having the same error randomly in our pipeline
@ZoranPandovski I did get an error until I've changed to rag_engine. It also does not make sense that in some sections of this same documentation page engine = "rag_engine" is...
> I think most of the docs examples are mentioning `rag_engine` because that is the name assigned to the `rag` engine with: > > ``` > CREATE ML_ENGINE rag_engine >...
I have read the CLA Document and I hereby sign the CLA