This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-11-26
Channels
- # announcements (2)
- # aws (4)
- # babashka (5)
- # beginners (91)
- # calva (4)
- # cider (17)
- # clara (13)
- # clj-kondo (14)
- # cljsrn (11)
- # clojure (159)
- # clojure-europe (2)
- # clojure-nl (14)
- # clojure-norway (2)
- # clojure-taiwan (2)
- # clojure-uk (32)
- # clojurescript (101)
- # clojutre (4)
- # cursive (13)
- # data-science (1)
- # datomic (46)
- # emacs (68)
- # figwheel-main (5)
- # fulcro (48)
- # graalvm (7)
- # graphql (6)
- # instaparse (5)
- # joker (4)
- # lambdaisland (1)
- # leiningen (2)
- # malli (9)
- # off-topic (41)
- # pedestal (15)
- # re-frame (47)
- # reagent (7)
- # reitit (14)
- # shadow-cljs (180)
- # spacemacs (58)
- # specter (1)
- # tools-deps (13)
hello, anybody here uses sayid on spacemacs?
I have no idea why but when I do (sayid-get-workspace)
the buffer is empty π
(iβm trying to use it to debug tests)
the error i get on *Messages*
is: sayid-find-existing-file: Wrong type argument: stringp, nil
@imparato.andrea Evaling the buffer first can sometimes fix the latter issue
i did that π
it seems like that the workspace buffer is βstuckβ
I've only used the cider-debugger
which works nicely for specific functions. sayid looks really powerful, but havent had chance to make use of it yet.
@imparato.andrea maybe you've capture too much? Do you get a timeout when it tries to render the *sayid*
buffer?
i think i found the problem:
java.lang.NullPointerException: null
at clojure.lang.Compiler.maybeResolveIn (Compiler.java:7309)
clojure.core$ns_resolve.invokeStatic (core.clj:4336)
clojure.core$ns_resolve.invokeStatic (core.clj:4325)
clojure.core$resolve.invokeStatic (core.clj:4338)
clojure.core$resolve.invoke (core.clj:4338)
com.billpiel.sayid.trace$untrace_var_STAR_.invokeStatic (trace.clj:155)
com.billpiel.sayid.trace$untrace_var_STAR_.invoke (trace.clj:151)
com.billpiel.sayid.inner_trace3$eval7971$fn__7972.invoke (inner_trace3.clj:795)
clojure.lang.MultiFn.invoke (MultiFn.java:233)
clojure.lang.AFn.applyToHelper (AFn.java:156)
clojure.lang.AFn.applyTo (AFn.java:144)
clojure.core$apply.invokeStatic (core.clj:657)
clojure.core$apply.invoke (core.clj:652)
com.billpiel.sayid.workspace$disable_all_traces_BANG_.invokeStatic (workspace.clj:114)
com.billpiel.sayid.workspace$disable_all_traces_BANG_.invoke (workspace.clj:107)
com.billpiel.sayid.workspace$disable_all_traces_BANG_.invokeStatic (workspace.clj:108)
com.billpiel.sayid.workspace$disable_all_traces_BANG_.invoke (workspace.clj:107)
clojure.lang.Var.invoke (Var.java:381)
i was just following the sayid README
good to know π
ok so this is how spacemacs starts the repl
[nREPL] Starting server via /usr/local/bin/lein update-in :dependencies conj \[nrepl\ \"0.6.0\"\] -- update-in :plugins conj \[com.billpiel/sayid\ \"0.0.18\"\] -- update-in :plugins conj \[refactor-nrepl\ \"2.5.0-SNAPSHOT\"\] -- update-in :plugins conj \[cider/cider-nrepl\ \"0.23.0-SNAPSHOT\"\] -- repl :headless :host localhost
after that i switch the repl to the buffer namespace
and load the buffer
then i load the namespace on sayid (sayid-trace-ns-by-pattern)
i get
Traced namespaces:
15 / 15 *name_of_the_namespace*
6 / 6 *name_of_the_namespace*
0 / 0 *name_of_the_namespace*
and the (sayid-get-workspace) and it hangs
do i need to execute functions on the repl?
funny enough, same configs, same emacs on different laptop and it works
different project tho
could be that is the project the problem
problem, project is not mine π
i see stuff on the repl so the code is running
and i also get the results from the function
hmm i gotta a workspace no idea how lol
ok i wasnβt not capturing data indeed
thx for the help @bpiel π
and thx very much for having created this amazing tool