Docker image updated on DockerHub

Just updated our Docker image on DockerHub [1] with M3. docker run -it apachegeode/geode:1.0.0-incubating.M3 The command above will give you `gfsh` now for default. Append "bash" to the end if you'd like access to the prompt. [1] https://hub.docker.com/r/apachegeode/geode/tags/ Cheers, -- ~/

[GitHub] incubator-geode pull request #237: GEODE-1821: fix termination of invokeAsyn...

GitHub user pdxrunner opened a pull request: https://github.com/apache/incubator-geode/pull/237 GEODE-1821: fix termination of invokeAsync threads You can merge this pull request into a Git repository by running: $ git pull https://github.com/pdxrunner/incubator-geode feature/

Re: Review Request 51618: GEODE-1836: remove defunct Java 1.6 block for Mac from GFSH script

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/51618/#review147710 --- Ship it! If the below comment concerning warning the user does

Review Request 51618: GEODE-1836: remove defunct Java 1.6 block for Mac from GFSH script

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/51618/ --- Review request for geode, Anthony Baker, Jinmei Liao, John Blum, William Markito

Re: Review Request 51612: GEODE-1834: initilize the socketcreator with the correct ssl settings

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/51612/#review147705 --- Ship it! Ship It! - Kirk Lund On Sept. 2, 2016, 6:38 p.m., J

Re: Review Request 51612: GEODE-1834: initilize the socketcreator with the correct ssl settings

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/51612/#review147703 --- geode-core/src/main/java/com/gemstone/gemfire/management/internal

SystemFailure and VirtualMachineErrors

The Geode codebase currently includes the component SystemFailure which is initiated by any instance of VirtualMachineError: } catch (VirtualMachineError e) { SystemFailure.initiateFailure(e); throw e; SystemFailure will ultimately react by closing the DistributedSystem and

Re: M3 is done, what's next?

+1 On Fri, Sep 2, 2016 at 11:52 AM Kirk Lund wrote: > +1 > > > On Fri, Sep 2, 2016 at 11:45 AM, Sai Boorlagadda < > sai.boorlaga...@gmail.com> > wrote: > > > +1 for package renaming. > > > > Sai > > > > On Fri, Sep 2, 2016 at 11:42 AM, William Markito > > wrote: > > > > > ++1 to finally do it!

Re: M3 is done, what's next?

+1 On Fri, Sep 2, 2016 at 11:45 AM, Sai Boorlagadda wrote: > +1 for package renaming. > > Sai > > On Fri, Sep 2, 2016 at 11:42 AM, William Markito > wrote: > > > ++1 to finally do it! This is great! > > > > We should include not only Spring Data Geode but also Apache Zeppelin, > > Apache Apex.

Re: M3 is done, what's next?

+1 for package renaming. Sai On Fri, Sep 2, 2016 at 11:42 AM, William Markito wrote: > ++1 to finally do it! This is great! > > We should include not only Spring Data Geode but also Apache Zeppelin, > Apache Apex... > > > > On Fri, Sep 2, 2016 at 8:46 AM, Anthony Baker wrote: > > > Hi everyone

Re: M3 is done, what's next?

++1 to finally do it! This is great! We should include not only Spring Data Geode but also Apache Zeppelin, Apache Apex... On Fri, Sep 2, 2016 at 8:46 AM, Anthony Baker wrote: > Hi everyone, > > We completed the M3 release in August and now we should consider the scope > for the next release:

Re: Review Request 51612: GEODE-1834: initilize the socketcreator with the correct ssl settings

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/51612/ --- (Updated Sept. 2, 2016, 6:38 p.m.) Review request for geode, Bruce Schuchardt,

Re: Review Request 51612: GEODE-1834: initilize the socketcreator with the correct ssl settings

> On Sept. 2, 2016, 6:14 p.m., Kirk Lund wrote: > > geode-core/src/test/java/com/gemstone/gemfire/management/ConnectToLocatorSSLDUnitTest.java, > > line 56 > > > > > > Change this to @Rule so each Test method gets it

Re: Review Request 51612: GEODE-1834: initilize the socketcreator with the correct ssl settings

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/51612/#review147677 --- geode-core/src/test/java/com/gemstone/gemfire/management/ConnectT

Re: M3 is done, what's next?

+1 for making changes sooner rather than later. Also, thank you Dan for mentioning this effort will need to coordinated with *Spring Data Geode*. On Fri, Sep 2, 2016 at 10:39 AM, Darrel Schneider wrote: > +1 for renaming the packages > > > On Fri, Sep 2, 2016 at 9:57 AM, Michael Stolz wrote: >

Review Request 51612: GEODE-1834: initilize the socketcreator with the correct ssl settings

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/51612/ --- Review request for geode, Bruce Schuchardt, Kevin Duling, Kirk Lund, and Udo Koh

Re: M3 is done, what's next?

+1 for renaming the packages On Fri, Sep 2, 2016 at 9:57 AM, Michael Stolz wrote: > +1 for renaming packages now. > > We might consider having a look at the examples to make sure we have > covered off-heap and integrated security. > > -- > Mike Stolz > Principal Engineer - Gemfire Product Manag

Re: M3 is done, what's next?

+1 for renaming packages now. We might consider having a look at the examples to make sure we have covered off-heap and integrated security. -- Mike Stolz Principal Engineer - Gemfire Product Manager Mobile: 631-835-4771 On Sep 2, 2016 9:47 AM, "Dan Smith" wrote: > +1 For renaming the packages.

Re: M3 is done, what's next?

+1 For renaming the packages. It would be really nice to graduate ASAP! Is there anything else from a code perspective that we need to do before graduation? If so we should also get that in 1.0. It would be nice to get a few more examples in the codebase for 1.0. We should probably just generally

Re: M3 is done, what's next?

On Fri, Sep 2, 2016 at 8:46 AM, Anthony Baker wrote: > with one exception: we need to rename our source packages to > ‘org.apache.geode’ [3]. > > I think we should move forward with package renaming *now* and include > that in the scope for the 1.0.0-incubating release. > > As previously discuss

M3 is done, what's next?

Hi everyone, We completed the M3 release in August and now we should consider the scope for the next release: 1.0.0-incubating. We’ve had previous discussions on this topic [1] but I would like us to reopen the conversation and make sure we are all still in agreement. In particular, I think

Build failed in Jenkins: Geode-nightly #580

See Changes: [gzhou] GEODE-1833: should save the reference locally in case other thread [dschneider] GEODE-1818: fix NPE in Bug37377DUnitTest [hkhamesra] GEODE-1805 Now test retries to fetch the all pr-meta-data [hiteshk25] GEODE-1774 M