cljdoc 2020-01-24 | Slack Archive

@tony.kay interesting, seems to happen with rebuilds too but locally everything works fine.

@tony.kay I’ve looked into this some more but couldn’t find a good explanation yet. If you don’t mind it would be great to log an issue just to make sure we don’t lose this in Slack’s history limits.

tony.kay17:01:58

ok, will do

tony.kay17:01:15

https://github.com/cljdoc/cljdoc/issues/376

borkdude13:01:06

Has been happening with a lot of my recent projects as well. Example: example: https://cljdoc.org/d/borkdude/edamame/0.0.10/doc/readme

borkdude13:01:59

https://circleci.com/gh/cljdoc/builder/16248 Checking out: https://github.com/cljdoc/codox at e0cd26910704c416611fc81f43f890a26861c221 Failed to read artifact descriptor for org.clojure:tools.reader:jar:1.3.2

martinklepsch13:01:50

Super weird, some googling seems to indicate caching issues but rerunning the CI job without cache produces the same result

martinklepsch17:01:59

Thanks for this issue @tony.kay https://github.com/cljdoc/cljdoc/issues/376 @jimmy @borkdude feel free to add your builds and anything else that seems relevant

borkdude17:01:54

added

jimmy17:01:02

Left a comment on the issues. Seems like it is because mavencentral moved to https and the builds are still trying to hit the http route.

borkdude19:01:28

Is that the same issue that was mentioned in cljs-dev?

jimmy19:01:17

https://github.com/cljdoc/cljdoc/pull/377

🙌 12

2020-01-24

Channels