These are chat archives for atomix/atomix

28th
Jun 2018
Jordan Halterman
@kuujo
Jun 28 2018 04:15
Multicast is disabled by default
currently
man
I’m working from a laptop and don’t even have a desk ATM
this sucks
nvm found a suitable laundry basket
Jordan Halterman
@kuujo
Jun 28 2018 05:41
@johnou all the failing tests should be fixed now
we should also remove Travis once this is done
kind of annoying having multiple CI services on PRs
Johno Crawford
@johnou
Jun 28 2018 05:57
yeah
Jordan Halterman
@kuujo
Jun 28 2018 05:57
wait I can remove it from the PR
Johno Crawford
@johnou
Jun 28 2018 05:57
and i've worked out how to run it against multiple jdks now
atomix/atomix#665
Jordan Halterman
@kuujo
Jun 28 2018 05:57
neat
Johno Crawford
@johnou
Jun 28 2018 05:57
i rebased this
and you were right about different types of issues
atomix/atomix#661
Jordan Halterman
@kuujo
Jun 28 2018 06:00
oh that’s awesome
I thought I seemed to remember that from when they released the template faeture
Johno Crawford
@johnou
Jun 28 2018 06:00
it takes the markdown from the top part and turns it into a button on the issue tab page
Jordan Halterman
@kuujo
Jun 28 2018 06:00
nice
I think Travis should be disabled now
that's cool
i haven't seen many projects use that
i had to dig around the documentation a fair bit
wrt Oracle and OpenJDK
Q: What is the difference between the source code found in the OpenJDK repository, and the code you use to build the Oracle JDK?
A: It is very close - our build process for Oracle JDK releases builds on OpenJDK 7 by adding just a couple of pieces, like the deployment code, which includes Oracle's implementation of the Java Plugin and Java WebStart, as well as some closed source third party components like a graphics rasterizer, some open source third party components, like Rhino, and a few bits and pieces here and there, like additional documentation or third party fonts. Moving forward, our intent is to open source all pieces of the Oracle JDK except those that we consider commercial features such as JRockit Mission Control (not yet available in Oracle JDK), and replace encumbered third party components with open source alternatives to achieve closer parity between the code bases.
Jordan Halterman
@kuujo
Jun 28 2018 06:05
wow that’s awesome
Johno Crawford
@johnou
Jun 28 2018 06:06
lol
yeah i think we'll be moving to openjdk at work
ERROR] io.atomix.core.barrier.RaftDistributedCyclicBarrierTest Time elapsed: 28.835 s <<< ERROR!
java.util.concurrent.TimeoutException
Jordan Halterman
@kuujo
Jun 28 2018 06:13
man there are some crazy request timeouts
Jordan Halterman
@kuujo
Jun 28 2018 06:32
:-(
Johno Crawford
@johnou
Jun 28 2018 06:32
i see why it failed
but it's weird
Jordan Halterman
@kuujo
Jun 28 2018 06:33
This project has been banned from the build due to previous failures.
what’s with that
Johno Crawford
@johnou
Jun 28 2018 06:33
you can ignore that
that's just a bad maven msg
means previous modules failed to compile
Jordan Halterman
@kuujo
Jun 28 2018 06:33
terrible
Johno Crawford
@johnou
Jun 28 2018 06:34
    <jdk>!8</jdk>
maybe it should be !1.8
Johno Crawford
@johnou
Jun 28 2018 07:23
@kuujo barrier test seems to consistently fail?
Not locally of course..
Johno Crawford
@johnou
Jun 28 2018 07:41
PrimaryBackupDistributedCyclicBarrierTest>DistributedCyclicBarrierTest.testBarrier:72
Another single CPU issue?
Johno Crawford
@johnou
Jun 28 2018 08:24
oh yes atomix running on java 11! :clap:
Alexis Hernandez
@AlexITC
Jun 28 2018 14:42
I wonder is you guys have any planned date for releasing version 3
rbondar
@rbondar
Jun 28 2018 21:41

hi , had stable work on ```

<dependency>
<groupId>io.atomix</groupId>
<artifactId>atomix</artifactId>
<version>2.1.0-20180511.233419-94</version>
</dependency>
<dependency>
<groupId>io.atomix</groupId>
<artifactId>atomix-cluster</artifactId>
<version>2.1.0-20180511.233357-97</version>
</dependency>
<dependency>
<groupId>io.atomix</groupId>
<artifactId>atomix-messaging</artifactId>
<version>2.1.0-20180511.233354-97</version>
</dependency>
<dependency>
<groupId>io.atomix</groupId>
<artifactId>atomix-primitive</artifactId>
<version>2.1.0-20180511.233404-90</version>
</dependency>
<dependency>
<groupId>io.atomix</groupId>
<artifactId>atomix-storage</artifactId>
<version>2.1.0-20180511.030228-95</version>
</dependency>
<dependency>
<groupId>io.atomix</groupId>
<artifactId>atomix-utils</artifactId>
<version>2.1.0-20180511.040023-97</version>
</dependency>
<dependency>
<groupId>io.atomix</groupId>
<artifactId>atomix-raft</artifactId>
<version>2.1.0-20180511.233410-96</version>
</dependency>
<dependency>
<groupId>io.atomix</groupId>
<artifactId>atomix-primary-backup</artifactId>
<version>2.1.0-20180511.233413-89</version>
</dependency>
```
moved to 3.0.0-rc1 , i guess i missed when Member.Type disappeared. Is it correct to forget about it as of now?

Alexis Hernandez
@AlexITC
Jun 28 2018 22:10
from what I saw, it is not there anymore
I was able to do a small upgrade without using the type
rbondar
@rbondar
Jun 28 2018 22:24
Looks like over9000 changes in code base including: 1) removing Member.Type 2) replacing messagingService() with getCommunicationService() 3) add builder.addProfiles(Profile.DATA_GRID) 4) remove builder.withPartitionGroups() and builder.withManagementGroup() - finally passed smoothly to build. Nice!
And it works .