
                    For clojure, we pick up the best solutions provided by github life savers.
                    If google brings you here, you are so lucky! These life savers are angels, they have well solved your problems.
                    So do not waste time scrolling the original issue threads just to dig out solutions... 
                    Here you are, you are welcome. Then, go back to work!
                    

@agilliland ? is the Postgres JSONB operator to check whether an object contains a given key 

metabase Question mark in SQL query (postgres JSON operator) interpreted as prepared statement param

I was having the same issue and this solved it:
I'm running a docker image of metabase and a separate docker image of mongo 

metabase Connect to MongoDB error: Connection to ... successful, but could not connect to DB.

Receiving the exact same error message:
com.mongodb.MongoTimeoutException: Timed out after 3000 ms while waiting to connect 

metabase Unable to connect to MongoDB Atlas Cluster

It would be great if we could pass variables to nested questions: At its simplest 

metabase Add a template tag to use already defined queries

Just chiming in to say I'm also interested in using clojure.core.match with babashka! 

babashka clojure.core.match

Another option is:
When there is no :as foo or :refer [foo] the tooling MUST assume that this namespace is implicitly used?
I think this works for 99% of my implicit requires?
Example from a file that was in front of me right now:

The implicit requires are dre.yada.html and dre.yada.xml which are exactly the only ones that do not have an alias or a :refer.

clj kondo Convention for necessarily required but not explicitly used namespaces

I had the same issue I don't know Emacs Lisp very well Use the template below when reporting bugs Please 

cider cannot restart repl after killed it

had this issue yesterday when upgrading from 0.30.* to 0.32.8 and fixed it by adding
trustServerCertificate=true
to Additional JDBC connection string options: for the database.

metabase Connections can not be acquired from the underlying database!

I would like to be able to hide/disable x-rays for a different reason - they may result in expensive queries being run if tables or views are very large and not intended to be used for global arbitrary field correlations and metrics.

metabase Hide x-rays on homepage (alternatively: make it possible to select which database is shown)

I had this issue and solved it by doing:
rm -r node_modules/
rm -r ios/Pods
npm install
cd ios && pod install
Open XCode 