Re: [rng] Releasing 1.3

I would cd into ./target/commons-release-plugin/scm and try the svn commit from there manually. That’s the directory where everything gets staged. I also think your svn password gets cached generally, but that’s predicated on having checked something into svn previously. Given our recent

Re: [Numbers] Arrays of "Complex" objects and RAM

That's interesting. The JTransforms library performs Fourier transforms that can take complex input, output, or both. They do this with interleaved double[] arrays, which I suppose is much more space efficient, and the status of a number as real or imaginary is implicit by its location being odd

Re: [rng] Releasing 1.3

> On 4 Nov 2019, at 19:31, Alex Herbert wrote: > > > >> On 4 Nov 2019, at 18:38, Rob Tompkins > > wrote: >> >> Also keep me posted. I’ll be near my keyboard all day. -Rob >> >>> On Nov 4, 2019, at 1:21 PM, Rob Tompkins >> > wrote: >>>

Re: [rng] Releasing 1.3

> On 4 Nov 2019, at 18:38, Rob Tompkins wrote: > > Also keep me posted. I’ll be near my keyboard all day. -Rob > >> On Nov 4, 2019, at 1:21 PM, Rob Tompkins wrote: >> >>  >> >>> On Nov 4, 2019, at 1:16 PM, Alex Herbert wrote: >>> >>>  > On 04/11/2019 17:36, Alex Herbert wrote:

Re: [rng] Releasing 1.3

Also keep me posted. I’ll be near my keyboard all day. -Rob > On Nov 4, 2019, at 1:21 PM, Rob Tompkins wrote: > >  > >> On Nov 4, 2019, at 1:16 PM, Alex Herbert wrote: >> >>  On 04/11/2019 17:36, Alex Herbert wrote: >>> >>> On 04/11/2019 15:40, Alex Herbert wrote: On

Re: [rng] Releasing 1.3

> On Nov 4, 2019, at 1:16 PM, Alex Herbert wrote: > >  >> On 04/11/2019 17:36, Alex Herbert wrote: >> >> >>> On 04/11/2019 15:40, Alex Herbert wrote: >>> >>> On 04/11/2019 12:43, Gilles Sadowski wrote: Hello. Le lun. 4 nov. 2019 à 13:05, Alex Herbert a écrit : >

Re: [rng] Releasing 1.3

On 04/11/2019 17:36, Alex Herbert wrote: On 04/11/2019 15:40, Alex Herbert wrote: On 04/11/2019 12:43, Gilles Sadowski wrote: Hello. Le lun. 4 nov. 2019 à 13:05, Alex Herbert a écrit : On 04/11/2019 00:42, Gilles Sadowski wrote: Hi. [...] So there are at least two options: 1.

Re: [rng] Releasing 1.3

On 04/11/2019 15:40, Alex Herbert wrote: On 04/11/2019 12:43, Gilles Sadowski wrote: Hello. Le lun. 4 nov. 2019 à 13:05, Alex Herbert a écrit : On 04/11/2019 00:42, Gilles Sadowski wrote: Hi. [...] So there are at least two options: 1. Release using JDK 9 +1 OK. I'll run through

Re: [rng] Releasing 1.3

On 04/11/2019 12:43, Gilles Sadowski wrote: Hello. Le lun. 4 nov. 2019 à 13:05, Alex Herbert a écrit : On 04/11/2019 00:42, Gilles Sadowski wrote: Hi. [...] So there are at least two options: 1. Release using JDK 9 +1 OK. I'll run through the release with JDK 9. I do not think we

Re: [rng] Releasing 1.3

Hello. Le lun. 4 nov. 2019 à 13:05, Alex Herbert a écrit : > > > On 04/11/2019 00:42, Gilles Sadowski wrote: > > Hi. > > > >> [...] > >> > >> So there are at least two options: > >> > >> 1. Release using JDK 9 > > +1 > > OK. I'll run through the release with JDK 9. I do not think we have any >

Re: [rng] Releasing 1.3

On 04/11/2019 00:42, Gilles Sadowski wrote: Hi. [...] So there are at least two options: 1. Release using JDK 9 +1 OK. I'll run through the release with JDK 9. I do not think we have any NIO classes so the issue raised by Gary should not be present. I am looking at the clirr report

Re: [CODEC] Sign Extension Error in Murmur3

There are a number of issues with the format and potential bugs in the Codec Murmur3 code. ( See spotbugs, PMD, and codestyle reports) The one that tripped me up was the mix of tab/space lines. Anyway, these issues can be fixed in later pull requests. I think is one overarching question and one

Re: [CODEC] Sign Extension Error in Murmur3

> On 4 Nov 2019, at 02:13, sebb wrote: > > On Mon, 4 Nov 2019 at 00:53, Claude Warren > wrote: >> >> I think the way to prove they behave correctly is to test the results >> against the original "C" implementation. With this in mind I proposed the >> changes. >> >>