When the REPL stubs are being generated, often the following warning will occur many times and result in a scary looking error popup. This has led to confusion about whether anything actually went wrong or not. These should be filtered out since they're mostly harmless.
Error generating stubs for module xxx:
WARNING: boolean? already refers to: #'clojure.core/boolean? in namespace: fipp.visit, being replaced by: #'fipp.visit/boolean?
WARNING: boolean? already refers to: #'clojure.core/boolean? in namespace: hara.common.checks, being replaced by: #'hara.common.checks/boolean?
WARNING: double? already refers to: #'clojure.core/double? in namespace: hara.common.checks, being replaced by: #'hara.common.checks/double?
WARNING: bigdec? already refers to: #'clojure.core/bigdec? in namespace: hara.common.checks, being replaced by: #'hara.common.checks/bigdec?
WARNING: uuid? already refers to: #'clojure.core/uuid? in namespace: hara.common.checks, being replaced by: #'hara.common.checks/uuid?
WARNING: uri? already refers to: #'clojure.core/uri? in namespace: hara.common.checks, being replaced by: #'hara.common.checks/uri?
WARNING: bytes? already refers to: #'clojure.core/bytes? in namespace: hara.common.checks, being replaced by: #'hara.common.checks/bytes?
WARNING: bytes? already refers to: #... (show balloon)
When the REPL stubs are being generated, often the following warning will occur many times and result in a scary looking error popup. This has led to confusion about whether anything actually went wrong or not. These should be filtered out since they're mostly harmless.