This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-09-13
Channels
- # announcements (2)
- # babashka (2)
- # beginners (112)
- # calva (29)
- # cider (33)
- # clj-kondo (41)
- # cljdoc (10)
- # cljs-dev (2)
- # clojure (72)
- # clojure-berlin (3)
- # clojure-europe (10)
- # clojure-italy (6)
- # clojure-nl (15)
- # clojure-spec (5)
- # clojure-uk (40)
- # clojurescript (1)
- # clr (6)
- # community-development (6)
- # core-async (21)
- # cursive (42)
- # datascript (12)
- # duct (6)
- # flambo (1)
- # fulcro (50)
- # jobs (1)
- # leiningen (3)
- # off-topic (16)
- # re-frame (6)
- # reagent (23)
- # reitit (7)
- # ring-swagger (14)
- # shadow-cljs (35)
- # tools-deps (39)
- # vim (12)
That’s what I thought: thanks. I’ll Just need to search for where that’s happening. The stack trace didn’t include anything from my source.
Looking at the code, https://github.com/duct-framework/core/blob/52babf6f0df4846d7e3bf3bc8b16ee47a6898b4c/src/duct/core.clj#L141 it's possible that something that returns the sql boundary isn't placed inside a profile, but on the first level.
It seems that you are using https://github.com/duct-framework/database.sql (that's where the duct.database.sql/Boundary
record is defined). If this is so, make sure :duct.database/sql
key configuration is inside the :duct.profile/base
key configuration, in config.edn
.
here's the config
{:duct.profile/base {:duct.core/project-ns watchdude
:duct.router/ataraxy {:routes {[:get "/example"] [:watchdude.handler/example]
[:get "/"] [:watchdude.handler/index]}}
[:duct.handler.static/ok :watchdude.handler/index]
{:body {:entries "/entries"}}
:watchdude.handler/example {}}
:duct.database.sql/hikaricp {:jdbc-url "jdbc:}
:watchdude.state/init {:db #ig/ref :duct.database.sql/hikaricp}...}