Are you absolutely sure you’re not compiling on Java 9? I think Java 9 added a
position on ByteBuffer with covariant return (other versions have it on the
Buffer super class).
>From the error it looks like AOT compilation found the method and compiled it
>into the byte code, but then that metho
Okay, I think I have a good understanding now.
Internally, I was using the Clojure build which bundles the dependency with it.
That's why that namespace shows up inside my Clojure Jar.
It makes sense also not to guarantee binary compatibility. We will make sure to
always build and run using the
I was away from Clojure for a year and I missed it. I am pleased to be
back. But I've forgotten certain common errors. I feel like this is
something I used to know but now I've lost the knowledge.
I'm using Factual's durable-queue to put a step inbetween the import of
large JSON files, and the
Sorry, I'm an idiot. The real error was when I called put!
I don't understand this error:
INFO: java.lang.NoSuchMethodError: java.util.zip.Checksum.update([B)V
java.lang.NoSuchMethodError: java.util.zip.Checksum.update([B)V
at durable_queue$checksum.invokeStatic (durable_queue.clj:64)
dur
On the new EC2 instance, running Ubuntu:
java -version
openjdk version "1.8.0_191"
OpenJDK Runtime Environment (build 1.8.0_191-8u191-b12-0ubuntu0.18.04.1-b12)
OpenJDK 64-Bit Server VM (build 25.191-b12, mixed mode)
Is it possible this version does not have the checksum signature that
durable-qu
So, I upgraded to Java 11, and now everything works. So I guess this was a
version conflict.
Just curious, but is there a way for Factual to make durable-queue to tell
Leiningen that Java 11 is necessary?
On Wednesday, January 16, 2019 at 3:17:49 PM UTC-5, lawrence...@gmail.com
wrote:
>
>
Are you using aot?
We have used that durable queue with 1.8. In fact, we have a compatibility
later that allows you to move from the durable queue to an Aws queue:
(mostly undocumented)
https://github.com/techascent/tech.queue
Is the problem possibly a difference between your compilation enviro
Hi!
We are discussing the possibility of an online meeting around data science
in clojure:
https://clojureverse.org/t/online-meeting-clojure-data-science/3503
- would love to hear your comments.
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To p
I am pretty sure I'm using Java 8. I do have both Java 8 and Java 11
installed, but the environment it's built with:
$ java -version
java version "1.8.0_162"
Java(TM) SE Runtime Environment (build 1.8.0_162-b12)
Java HotSpot(TM) 64-Bit Server VM (build 25.162-b12, mixed mode)
$ echo $JAVA_HOME
I've been able to reproduce this by deliberately building with Java
11/Clojure 1.10, then running on Java 8. Doing the same thing but built
with Java 8 is fine.
So, somehow some classes built with Java 11 must have gotten into the
build. Time to check my build cleanliness...
Thanks again, and
Off the top of my head, I think the only stuff in this area is the big bump in
the asm bytecode version, which could theoretically come into play here. There
were changes in reflection but I don’t think you’re doing reflection. I am
going to poke at this some more so it would probably be good to
Oh, well disregard my last message then!
> On Jan 16, 2019, at 5:47 PM, Alex Miller wrote:
>
> Off the top of my head, I think the only stuff in this area is the big bump
> in the asm bytecode version, which could theoretically come into play here.
> There were changes in reflection but I don
Am Di., 15. Jan. 2019 um 14:58 Uhr schrieb :
>
> Imagine I try on the one side to represent something like a database table
> in memory, while on the other to make it pluggable into all meaningful
> sequence and vector/map functions in Clojure. In the most naive
> implementation a table is a vecto
Am Do., 17. Jan. 2019 um 00:52 Uhr schrieb Herwig Hochleitner <
hhochleit...@gmail.com>:
> 5. I could attach table like descriptions to each Record object (be it in
>> its metadata or else), but then enforcing that all Records share the same
>> Table data could get penalizing at runtime.
>>
>
> Th
On 16 Jan 2019, at 18:17, Alex Miller wrote:
> Yes, it's one of the downsides of AOT.
I'd say it's not so much a downside of AOT - but of having a single output path
for classes. I've long wanted Chas's patch to be applied, or something like it.
Having everyone reinvent the mechanism whenever
15 matches
Mail list logo
