This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-02-21
Channels
- # announcements (39)
- # architecture (7)
- # aws (9)
- # babashka (111)
- # beginners (139)
- # bristol-clojurians (1)
- # calva (47)
- # chlorine-clover (5)
- # cider (17)
- # clj-kondo (26)
- # clojars (25)
- # clojure (251)
- # clojure-berlin (1)
- # clojure-dev (5)
- # clojure-europe (22)
- # clojure-france (1)
- # clojure-hungary (6)
- # clojure-losangeles (8)
- # clojure-nl (18)
- # clojure-spec (3)
- # clojure-uk (68)
- # clojured (32)
- # clojurescript (32)
- # core-async (10)
- # core-typed (120)
- # cursive (8)
- # datascript (10)
- # datomic (11)
- # docker (2)
- # emacs (6)
- # figwheel-main (4)
- # fulcro (10)
- # graalvm (92)
- # hoplon (2)
- # instaparse (9)
- # jobs (3)
- # jobs-discuss (31)
- # joker (2)
- # kaocha (1)
- # lambdaisland (5)
- # leiningen (10)
- # luminus (1)
- # lumo (14)
- # meander (30)
- # mid-cities-meetup (1)
- # midje (1)
- # off-topic (46)
- # pathom (22)
- # perun (2)
- # re-frame (10)
- # reitit (1)
- # remote-jobs (8)
- # shadow-cljs (71)
- # spacemacs (7)
- # sql (40)
- # tools-deps (31)
- # tree-sitter (11)
- # vim (14)
- # vscode (2)
- # xtdb (5)
Hey! 👋 Any idea on why this doesn't work?
$ clj -e '(doc ns-map)'
Syntax error compiling at (REPL:1:1).
Unable to resolve symbol: doc in this context
Full report at:
/tmp/clojure-135646063998456412.edn
No, Clojure.main does this in the repl setup
I would guess it would be more correct to say that starting repl requires clojure.repl for you
I would guess even more correct thing to say that clojure.main/repl-requires are required when you start a repl https://github.com/clojure/clojure/blob/38524061dcb14c598c239be87184b3378ffc5bac/src/clj/clojure/main.clj#L355
Making some increasingly half-hearted attempt to get DynamoDBLocal running to start embedded for tests, but it seems to depend on sqllite4java which exists in the mvn repos but with <packaging>dylib</packaging>
. Am I right in assuming that tools-deps doesn't have support for downloading dylib dependencies?
I prefer to use docker-compose to set up local service dependencies:
version: '2'
services:
dynamodb-local:
image: 'dwmkerr/dynamodb'
@thenonameguy Yeah, I will probably move to something like that. Dynamo local, at least in theory, does support embedded running so should be possible to throw up an in-memory version in a text fixture and tear it down afterwards, but the dependency on sqllite (and thus native libraries), is a bit of a hurdle. I'll probably give up, but just thought I would check that I am not missing a route I could at least try, but I think the docker-compose option is probably the way to go. Thanks.
Downloading native (thus platform dependent) libraries, is a bit awful anyway, I wouldn't be surprised if it's not supported.
@vlaaad @dominicm @alexmiller thanks for the help clearing that up! I realize why doc
shouldn't work above, and I get the expected result when I require it as I "should" do.
$ clj -e "(require '[clojure.repl :refer [doc]]) (doc ns-map)"
-------------------------
clojure.core/ns-map
([ns])
Returns a map of all the mappings for the namespace.
Not sure if this is a known regression or not… but I was using some private S3 buckets as mvn repos; with a URL of the form s3p://<bucket>/<directory>/
I’ve been using this for years (previously with leiningen) and found earlier in the week that I could no longer resolve deps via the clj
tool.
I suspect this was caused by the recent changes in t.d.a to using the cognitect aws lib; but I can’t be certain.
Anyway I’ve just tried changing the bucket URL’s to be of the form s3://
and it now works. No idea what the difference is in the protocols; but I’ve seen both forms over the years.
not an official protocol. AWS has a few other protocols for similar reasons (with EMR specially): s3a and s3n come to mind.
https://github.com/s3-wagon-private/s3-wagon-private i see this of course
yeah iirc tools.deps used the s3 wagon until recently
Yeah that’s why I’m mentioning it.
The (end user) fix is trivial (just change to use s3://
) once you know what the problem is though.
s3p has never been a documented supported protocol for clj
So was working before by accident, not by intent
s3p is an invention of the spring aws wagon
Ah interesting, I think I just copied my URLs from lein and didn’t think anything of it when they worked
Anyway it’s not a problem, I just thought I’d mention it incase it happens to others