but the scm entry in the pom.xml seems okay? https://gist.github.com/sritchie/226dc7d2e57458e2f84c30ef7e98ae92

hmm, analysis failed too… looks like cljdoc’s analyzer is taking the clj path in the forked macro: https://github.com/sicmutils/sicmutils/blob/main/src/sicmutils/util/def.cljc#L139

https://app.circleci.com/pipelines/github/cljdoc/builder/39342/workflows/d69df9e7-2d15-4c38-863b-5137688bd678/jobs/55716

Sure @U017QJZ9M7W, I can take a peek!

If I look https://repo.clojars.org/sicmutils/sicmutils/0.23.0/sicmutils-0.23.0.pom, I see the following for scm config:

<scm>
    <tag>v0.23.0</tag>
  </scm>

Oh right.. 2nd problem API analysis failure... please hold...

Ok... Clojure analysis is passing. It is ClojureScript analysis that is failing...

Huh, you are attempting import-vars-ish-ness for cljs. At one point, I did have an import-vars version working for cljs. It is buried in the history of rewrite-cljc. But as part of that effort I also updated cljdoc to understand such manipulations for cljs.

(personally, I abandoned load time import-vars due to too many oddities, I got fed up and went for code generation instead)

@U017QJZ9M7W how do you run our cljs unit tests for sicmutils?

I'd like to see stuff in cljs passing/working before taking a deeper peek into what might be happening with cljdoc here.

Back to problem 1, https://github.com/sicmutils/sicmutils/blob/02e7a6edaab345e5c6a516f663ecaeb6507cda26/build.clj#L42. That's fine if you also have a pom.xml that specifies the other scm values, but you don't seem to have that.

“Npm run test “ will do it!

Ohhh @UE21H2HHD nice catch. Locally weirdly the entries from my Pom.xml template were making it in, vs getting bumped by what you found. That would have taken me forever to find, thank you!

My pleasure. That's some extensive test suite @U017QJZ9M7W, it is still running...

Close to 7300 and counting

Lots of generative tests too… it is a little nuts for sure

Ah done after 11m!

One person's crazy, is another person's thorough!

So... dunno yet about the cljs failure. Can take a peek. One diff is that cljdoc uses the plain old ClojureScript compiler, and your test runs under shadow-cljs.

I’m happy to rewrite that macro- I really just want (def something somewhereelse.something) in cljs, nothing fancier

Yeah, it seems so simple, I remember.

Haha I definitely found other trip reports of clojurists dashed against these surprisingly rocky shores, just like us

The parenthe-seas can be rough!

Woah, mind blown

Not sure if it is agreeable to you, but you could https://github.com/cljdoc/cljdoc/blob/master/doc/userguide/for-library-authors.adoc#api-languages.

That’s fine, the APIs are the same so I’ll turn it off for now, fix the scm entry and publish an incremental version

Do you want me to file a ticket with the build etc,

?

You can do it in your https://github.com/sicmutils/sicmutils/blob/main/doc/cljdoc.edn, you have to fix that pom anyway, so would get will get picked in next release.

I don't know much about how shadow-cljs works but I'm thinking that might be the difference. If I try to run sicmutils under plain old (outside cljdoc) ClojureScript I get a similar error.

Okay I can use that info to make a small repro. What command do you use to run it with vanilla cljs?

Lemme get back to you on that. I'm just pasting from other projects to explore. Have to knock the rust off my cljs knowledge, it has been a while!

No problem

Ok, this seems like a maybe a simple way to trigger the issue in sicmutils with plain old ClojureScript: First, I added a :lee-cljs alias to sicmutils deps.edn

:lee-cljs
  {:extra-deps {org.clojure/clojurescript {:mvn/version "1.11.60"}}}

❯ clj -M:lee-cljs -m cljs.main --repl-env node 
ClojureScript 1.11.60

❯ clj -M:lee-cljs -m cljs.main --repl-env node
ClojureScript 1.11.60
cljs.user=> (require '[pattern.rule :as rule])
Unexpected error (AssertionError) macroexpanding cljs.core/resolve at (def.cljc:140:14).
Assert failed: Argument to resolve must be a quoted symbol
(core/and (seq? quoted-sym) (= (quote quote) (first quoted-sym)))

I can make a tiny version of that macro and get a repro up

thanks for this, @UE21H2HHD, I should have some time this evening and I’ll see what the cljs folks think

Here's me naively trying the same thing under shadow-cljs:

❯ npx shadow-cljs node-repl 
shadow-cljs - config: /home/lee/proj/oss/sicmutils/sicmutils/shadow-cljs.edn
shadow-cljs - starting via "clojure"
shadow-cljs - server version: 2.20.14 running at 
shadow-cljs - nREPL server started on port 32805
cljs.user=> shadow-cljs - #4 ready!
cljs.user=> (require '[pattern.rule :as rule])
nil

(no assert fail this time)

Lemme know how it goes. If you are really married to roughing the choppy seas with an import-vars type approach, I can dig up my old rewrite-cljc work for you.

(my advice: don't do it, but you are the captain of your ship, sir!)

I have to do it to give folks a namespace that has everything , so they can use it as a replacement for the original scheme library… and MIT scheme has no namespaces at all

@U017QJZ9M7W interesting recent https://clojurians.slack.com/archives/CQT1NFF4L/p1674180518666799 about import-vars that might interest you