Chao Yang

@rishavs You need to add the cluster name to the db name as prefix, and also enable `cleartext` auth methods: `postgres://[email protected]:26257/somedbname.defaultdb?auth_methods=cleartext,md5,scram-sha-256&sslmode=verify-full&sslrootcert=cc-ca.crt` But `sslmode=verify-full` is not implemented.

@wontruefree You should be able to connect with below connection string, you need to add the cluster name as db prefix and accept cleartext auth method. But the problem is...

It seems like this has been fixed with the docker nightly build.

@mamantoha Could you try it out with latest crystallang/crystal:nightly-alpine? It works for me. ``` # crystal -v Crystal 1.3.0-dev [0f0852f33] (2021-12-08) LLVM: 10.0.0 Default target: x86_64-unknown-linux-musl ```

OAS 3.1 support has been added to swagger-parser in https://github.com/swagger-api/swagger-parser/pull/1730

Rails active_record supports two types of locking: https://api.rubyonrails.org/classes/ActiveRecord/Locking/Optimistic.html https://api.rubyonrails.org/classes/ActiveRecord/Locking/Pessimistic.html

I got the same error when generating crystal client for stripe api. It seems like 2 get operations are interfering each other with required params. Here's a minimal spec file...

The implementation in #8563 probably doesn't work with nested json objects. I think a model flattener is better than the current implementation.

This bug seems to be fixed by https://github.com/crystal-lang/crystal/pull/12536

The interpreter could run majority of std lib tests successfully. A lot of the failing tests fork new processes. Fixing #12241 could really help the test coverage.