This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-10-17
Channels
- # alda (5)
- # bangalore-clj (1)
- # beginners (9)
- # bigdata (1)
- # boot (51)
- # carry (1)
- # cider (9)
- # cljs-dev (22)
- # clojars (39)
- # clojure (118)
- # clojure-brasil (1)
- # clojure-czech (8)
- # clojure-france (2)
- # clojure-italy (5)
- # clojure-korea (9)
- # clojure-russia (9)
- # clojure-spec (17)
- # clojure-uk (42)
- # clojurescript (48)
- # core-async (1)
- # emacs (3)
- # figwheel (1)
- # funcool (3)
- # hoplon (39)
- # klipse (51)
- # lein-figwheel (4)
- # leiningen (2)
- # luminus (5)
- # off-topic (245)
- # om (18)
- # onyx (19)
- # parinfer (1)
- # pedestal (18)
- # re-frame (47)
- # reagent (19)
- # ring-swagger (1)
- # specter (18)
- # untangled (93)
- # vim (8)
- # yada (56)
Hello. Does it look like valid traceroute
for http://clojars.org?
The problem is that all my lein deps
, lein uprgade
or even e.g. lein new figwheel ...
commands basically hang
@andrewboltachev: that trace looks very similar to what I get (stars past http://core7-aggr403b-9.iad3.rackspace.net), but lein deps
works fine
I don't think lein upgrade
hits clojars, so that might be a clue that something else is going wrong on your end
I mean, when you download new stuff, ofc
The thing is it's on both my local machine (Kirov, Russia) and server (Amsterdam, The Netherlands)
you'll get a warning from lein about having repos in the :user
profile, but you can ignore that for now
I haven't had this file btw:
{:user {
:repositories [["clojars" {:url ""}]]
:plugin-repositories [["clojars" {:url ""}]]
}}
should this be valid?
Well, with this, I have:
18 sec for 14.6M sounds quite serious
that doesn't use clojars though: https://github.com/technomancy/leiningen/blob/master/bin/lein#L73
yep, I've had GitHub also working with delays for me
Okay, either I have VPN or not, my physical connection stays the same
So that might be it's issues
thanks @tcrawley and I would check everything more carefully. This CDN should be helpful btw
we've been working on an ansible setup for it that would ease that, but there are still lots of clojars.org-specific bits in there
@mpenet: we haven't given specific thought to where we need to make changes to support private instances, we've been focused first on getting a reproducible setup, so don't have a list of what needs to happen. You are welcome to take a look at what you have to see what would need to change if you like: https://github.com/clojars/clojars-server-config
one of the big missing piece might be auth on the artifacts. if I am not mistaken now they are served via nginx directly
then maybe it makes sense to map auth on these to user/groups credentials (thinking out loud)
also another question would be do we want to allow auth per artifact or is it an on/off switch that applies to the whole instance