Fork me on GitHub

Hi there! @wilkerlucio I was talking with you in private about some resolver problems, and here's what I found: On my current Duck-REPLed project, I'm able to query REPL interactions. To make this happen, I somehow need to know what to query. To make things as simple as possible, I decided to do some "default contents", for example: if I do query [:var/fqn] I probably want the "full qualified name" of the current var in the editor.


This made the planner incredibly slow - it's taking +500ms to plan the query. How can I send you more info, so you can check if it's some bug or it's inherently a problem on how I made my resolvers?


More info about this problem: here's the "slow" query:


And here's the fast one:


hello, can you send an example of how I can reproduce it?


Helpers is duck-repled.repl-helpers eql is generated with duck-repled.core/gen-eql


Ok, in theory if you start a REPL with duck-repled and try to evaluate these codes, it should have the same problem that I had


The problem is that I'm not being able to connect Viz on them: on Clojure, it always return nil for the eval result, and not give me the trace, and in ClojureScript it's crashing node with:

INFO [] - Connecting to websocket { #object[Function], #object[cljs.core.async.impl.channels.ManyToManyChannel], :duck-repled.core/duck}
INFO [] - Waiting for channel to be ready 1000
INFO [] - Waiting for channel to be ready 1000

        (WithMeta. (-with-meta ^not-native x nil) m)
TypeError: x.cljs$core$IWithMeta$_with_meta$arity$2 is not a function
    at Transit$JSONMarshaller.transform (/home/mauricio/projects/duck-repled/.shadow-cljs/builds/tests/dev/out/cljs-runtime/cognitect/transit.cljs:418:9)


I was only be able to truly connect to Viz and check the query inside the Chlorine project 😞 But then, it's quite hard to setup everything to make it work