Anyone have any ideas on why the analysis might be timing out for my library? https://app.circleci.com/pipelines/github/cljdoc/builder/54119/workflows/00dbf534-86ab-47eb-8d8d-b683727f4464/jobs/70494
Happy to take a look sometime soon...
Awesome, I'd appreciate that 🙏
Ok... so something is not exiting after zero.core is loaded.
Without cljdoc, let's run a sanity first:
$ clj -Sdeps '{:deps {me.raystubbs/zero {:mvn/version "0.1.19"}}}' -M -e "(+ 1 2 3)"
6
And now, let's require zero.core
$ clj -Sdeps '{:deps {me.raystubbs/zero {:mvn/version "0.1.19"}}}' -M -e "(require '[zero.core])"
This does not return for me, I have to hit ctrl-c to quit.Does that help @stubbs.ray? Cljdoc-analyzer is timing out because of this.
Ya... if I change your Timer to a daemon thread in your base.cljc via (Timer. true), I see my little test above exiting.
I don't know what the requirements of your lib are, so this may not be appropriate.
Aah, okay didn't realize it actually loaded the code. Figured the analysis was static. That's very helpful, thanks a bunch.
Any chance I can ask how you spotted the Timer so quickly? Any neat tooling? Or sheer skill? 😅
Ha! No, I ran my example above and used visualvm to look at threads, saw a timer thread and searched your code for timers. And 🎉
Nice, thanks man