This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-04-15
Channels
- # announcements (2)
- # babashka (41)
- # beginners (10)
- # calva (62)
- # chlorine-clover (70)
- # cider (19)
- # clara (2)
- # clj-http (1)
- # clj-kondo (1)
- # cljs-dev (3)
- # cljsrn (8)
- # clojure (168)
- # clojure-austin (1)
- # clojure-australia (2)
- # clojure-canada (1)
- # clojure-europe (15)
- # clojure-france (9)
- # clojure-nl (3)
- # clojure-serbia (5)
- # clojure-spec (14)
- # clojure-uk (8)
- # clojurescript (14)
- # community-development (30)
- # core-async (42)
- # core-typed (1)
- # datahike (2)
- # datalog (23)
- # datomic (4)
- # emacs (4)
- # figwheel-main (4)
- # fulcro (67)
- # ghostwheel (4)
- # girouette (1)
- # gorilla (7)
- # graalvm (11)
- # heroku (8)
- # integrant (42)
- # jobs (6)
- # jobs-discuss (47)
- # kaocha (7)
- # lambdaisland (2)
- # leiningen (5)
- # lsp (29)
- # off-topic (1)
- # pathom (9)
- # portal (6)
- # re-frame (5)
- # reagent (11)
- # releases (6)
- # remote-jobs (10)
- # shadow-cljs (112)
- # testing (55)
- # vrac (1)
> ERROR in unit (core.clj:6) @marharyta.obraztsova are those three lines all the info you are getting? is there a stacktrace? does it mention a file in /tmp with more info? It's really hard to glean anything from what you've shared.
@schmandle could you add
[lambdaisland/glogi "1.0.100"]
{lambdaisland/glogi {:mvn/version "1.0.100"}}
to your deps.edn or project.clj and see if that allows you to use the latest kaocha-cljs?yes, this works:
{lambdaisland/kaocha {:mvn/version "RELEASE"}
lambdaisland/kaocha-cljs {:mvn/version "RELEASE"}
lambdaisland/glogi {:mvn/version "1.0.100"}
lambdaisland/kaocha-junit-xml {:mvn/version "RELEASE"}}
Hi, I’m having an issue where when running at the repl kaocha looses the binding for the current plugins when running the :post-summary
hook. I narrowed it down to here https://github.com/lambdaisland/kaocha/blob/55d1321aec6ecb3ec21af1dd910da52c15c324f3/src/kaocha/repl.clj#L155
Wanted to get a second set of eyes before I logged an issue as I don’t see anyway for plugin/run-hook
to still have plugin/*current-chain*
outside of the api/run
function.
Thanks for letting us know! So you're trying to access plugin/*current-chain*
from a hook? What do you need it for, in case there's an alternative to using plugin/*current-chain*
?
@U01FJUDL57C I found this when using the “profiling” plugin, which uses the :post-summary
hook. Currently running this with the repl api doesn’t output the profiling summary because of plugin/*current-chain*
no longer being bound outside the api/run
call.