Fork me on GitHub
#clojure
<
2018-12-08
>
valerauko08:12:01

is this a known problem?

WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by clojure.lang.Reflector (file:/usr/share/java/leiningen-2.8.1-standalone.jar) to method com.sun.xml.internal.stream.XMLInputFactoryImpl.createXMLStreamReader(java.io.Reader)
WARNING: Please consider reporting this to the maintainers of clojure.lang.Reflector
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release

kulminaator08:12:44

where exactly does that happen for you , when starting a leiningen application lein repl or lein run ?

valerauko08:12:09

lein ancient on clojure:openjdk-11-lein

kulminaator09:12:09

i run two projects here on leiningen 2.8.1 ontop of openjdk-11 ... and i haven't seen that one popping up

Daouda09:12:46

hey guys, somebody using emacs on debian?

schmee09:12:27

@vale known problem, has been fixed in 1.10: https://dev.clojure.org/jira/browse/CLJ-2066

valerauko09:12:42

glad to hear!

caleb.macdonaldblack13:12:40

I have data that doesn't stream in, just the whole lot read at once. I have multiple sources of data. I am running transformation on this data, combining them and then running further transformations. Would it be computationally quicker to use core.async channels and transducers? I would need to use core.async channels to converge the data transformation streams along the pipeline.

caleb.macdonaldblack13:12:13

Transducers on their own will probably be quicker for a single branch of transformations. But I'm wondering converging them with core.async channels is a good idea

alexmiller14:12:57

@vale @schmee the result of this ticket is a bit more nuanced than just “fixed”. I am working on some updated docs about it for the web site. You are likely to still get this warning in Clojure 1.10, but note, it is a warning and the code will work fine up through Java 11 (and possibly beyond)

alexmiller14:12:31

there are a variety of ways to make the warning stop, but really the best way is to disambiguate the call so it’s not using reflection in the first place. In this case, looks like that’s probably in a tooling dep so might be out of your hands.

schmee14:12:56

cool, thanks for clarifying!

abdullahibra18:12:55

i'm trying to interop with rdf4j java lib but i can't cause some weird errors

abdullahibra18:12:17

call to method createIRI can't be resolved (target class is unknown).