cljdoc

Jakub Holý (HolyJak) 2022-02-11T15:40:06.198439Z

Hi! When we get import errors like https://cljdoc.org/builds/53065 >

Could not find revision v0.1.4 in repo ",
>  :data {:origin "<https://g>
wouldn't it be best to simply throw away that revision? In this case it seems http://scicloj.ml had a v0.1.4 but then removed it. As a result, https://cljdoc.org/d/scicloj/scicloj.ml/ will lead to the failed import site until a new, same or higher version is released (instead of the last actually available, v0.1.4)

lread 2022-02-11T19:10:11.347859Z

@holyjak I think cljdoc search is currently driven by clojars data, and it has that revision https://clojars.org/scicloj/scicloj.ml/versions/0.1.4. But yeah, maybe when an import results in 0 articles and 0 namespaces, it should be excluded for search results, if that is what you are getting at?

Jakub Holý (HolyJak) 2022-02-11T19:21:49.050699Z

That as well as what is attempted displayed at https://cljdoc.org/d/scicloj/scicloj.ml/

lread 2022-02-11T19:33:58.628799Z

Right… I see what you mean. Maybe navigating to the last good import would make more sense? But… also knowing that there are later releases is also interesting to the reader.

Jakub Holý (HolyJak) 2022-02-14T09:24:56.177339Z

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

lread 2022-02-14T13:51:42.791809Z

Coolio! Thanks!

Jakub Holý (HolyJak) 2022-02-12T16:27:38.935379Z

Yes :)

lread 2022-02-12T22:00:03.793469Z

Sounds maybe worthy of a git issue then?

👍 1
2022-02-11T20:15:45.859369Z

2022-02-11T20:19:53.329969Z

2022-02-11T20:19:53.451319Z

2022-02-11T21:11:31.863539Z

2022-02-11T21:26:18.243119Z

2022-02-11T22:17:52.371209Z

2022-02-11T22:22:01.063929Z

2022-02-11T22:22:01.234989Z