Jenkins build is back to normal : Geode-nightly-flaky #56

See

Build failed in Jenkins: Geode-nightly #887

See -- [...truncated 53.42 KB...] :extensions/geode-modules-session:testClasses :extensions/geode-modules-session:checkMissedTests :extensions/geode-modules-session:spotlessJavaCheck :extensi

[GitHub] geode issue #619: Feature/geode 2901

Github user DivineEnder commented on the issue: https://github.com/apache/geode/pull/619 Still working on adding javadoc, but the actual code is all in place --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project

[GitHub] geode issue #619: Feature/geode 2901

Github user DivineEnder commented on the issue: https://github.com/apache/geode/pull/619 @ladyVader @nabarunnag @boglesby @jhuynh1 @upthewaterspout @gesterzhou --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your proj

[GitHub] geode pull request #619: Feature/geode 2901

GitHub user DivineEnder opened a pull request: https://github.com/apache/geode/pull/619 Feature/geode 2901 Thank you for submitting a contribution to Apache Geode. In order to streamline the review of the contribution we ask you to ensure the following steps have been ta

[Spring CI] Spring Data GemFire > Nightly-ApacheGeode > #607 was SUCCESSFUL (with 1908 tests)

--- Spring Data GemFire > Nightly-ApacheGeode > #607 was successful. --- Scheduled 1910 tests in total. https://build.spring.io/browse/SGF-NAG-607/ -- This

Re: Review Request 60664: GEODE-3153 Client receives duplicate events during rolling upgrade

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/60664/#review179699 --- Ship it! Ship It! - Barry Oglesby On July 5, 2017, 7:01 p.m.

Re: Review Request 60664: GEODE-3153 Client receives duplicate events during rolling upgrade

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/60664/#review179694 --- Ship it! Ship It! - Dan Smith On July 5, 2017, 7:01 p.m., Br

Re: Geode "minor minor" versions

Hi Roi, > Is there any plan to release a 1.1.2, or a 1.2.1, or will this be simply > an "ad hoc" situation, such that only an important bug fix will trigger > it... I understand now that this is the case. > That's exactly it. We'll only release a newer minor revision of older version of geode if

[GitHub] geode pull request #618: GEODE-3167: Added commons-validator dependency to m...

Github user asfgit closed the pull request at: https://github.com/apache/geode/pull/618 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabl

Review Request 60666: geode-3166: remove the uncalled getCredential method

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/60666/ --- Review request for geode, Emily Yeh, Jared Stewart, Ken Howe, Kirk Lund, and Pat

Review Request 60664: GEODE-3153 Client receives duplicate events during rolling upgrade

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/60664/ --- Review request for geode, Barry Oglesby, Hitesh Khamesra, and Dan Smith. Bugs:

Re: Geode "minor minor" versions

@Roi Apelker: There is a big effort going on right now in the community to get a 1.2 release of Geode out. You can follow the release notes here: https://cwiki.apache.org/confluence/display/GEODE/Release+Notes#ReleaseNotes-1.2.0 -- Mike Stolz Principal Engineer, GemFire Product Manager Mobile: +1-

Re: Review Request 60629: GEODE-3129 - Added error messages to protobuf protocol

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/60629/#review179641 --- Fix it, then Ship it! Ship It! geode-protobuf/src/test/java/o

[GitHub] geode issue #618: GEODE-3167: Added commons-validator dependency to modify_w...

Github user DivineEnder commented on the issue: https://github.com/apache/geode/pull/618 @ladyVader @nabarunnag @boglesby @jhuynh1 @upthewaterspout @gesterzhou --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your proj

[GitHub] geode pull request #618: GEODE-3167: Added commons-validator dependency to m...

GitHub user DivineEnder opened a pull request: https://github.com/apache/geode/pull/618 GEODE-3167: Added commons-validator dependency to modify_war script a… …nd Tomcat required jars Thank you for submitting a contribution to Apache Geode. In order to streamlin

[GitHub] geode pull request #615: GEODE-2991 Add man page for gfsh destroy gateway-se...

Github user asfgit closed the pull request at: https://github.com/apache/geode/pull/615 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabl

[GitHub] geode-native issue #106: GEODE-2891 connect-timeout violation in C++ Native ...

Github user echobravopapa commented on the issue: https://github.com/apache/geode-native/pull/106 @pivotal-jbarrett fair enough on the branching point, I think the rest is still a valid ask --- If your project is set up for it, you can reply to this email and have your reply appear o

[GitHub] geode-native issue #106: GEODE-2891 connect-timeout violation in C++ Native ...

Github user pivotal-jbarrett commented on the issue: https://github.com/apache/geode-native/pull/106 @echobravopapa the branching scheme only applies to committers working directly with the Geode repositories. Non-committers use pull requests which render the branching/girflow require

Re: Geode "minor minor" versions

On Wed, Jul 5, 2017 at 7:58 AM, Roi Apelker wrote: > > > Is there any plan to release a 1.1.2, or a 1.2.1, or will this be simply > an "ad hoc" situation, such that only an important bug fix will trigger > it... I understand now that this is the case. The simple answer is "yes", both may apply.

RE: Geode "minor minor" versions

I am sorry if I have been misunderstood (and yes I am new :-) ) I did not mean that GEODE is going to stop, I was referring to the subject of minor versions. Is there any plan to release a 1.1.2, or a 1.2.1, or will this be simply an "ad hoc" situation, such that only an important bug fix will

[GitHub] geode-native issue #106: GEODE-2891 connect-timeout violation in C++ Native ...

Github user echobravopapa commented on the issue: https://github.com/apache/geode-native/pull/106 @gregt5259 a couple quick items of feedback that need to be addressed before this is reviewed: - please squash your commits, this cleans up the diffs for everyone to better revie

Re: Different member-timeout for particular jvm’s

I think we would have to send the member-timeout setting in the "join" message and distribute it in the membership view message. I think this is a good idea On 7/5/17 5:03 AM, Aravind Musigumpula wrote: Hi, May be I was not clear in my last mail. My question is that can we monitor a jvm ba

[GitHub] geode-native issue #105: GEODE-2891 connect-timeout violation in C++ Native ...

Github user pivotal-jbarrett commented on the issue: https://github.com/apache/geode-native/pull/105 @gregt5259 please close this pull request since you opened #106. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If you

Re: Geode "minor minor" versions

You make it sound like Geode is going to stop. That's definitely not true. What affects Geode's future are the requests the community makes for new features. Check out our Jira to know what's in our future. Since this is an open source Apache community, all the planning occurs here in the open.

[GitHub] geode-native pull request #106: GEODE-2891 connect-timeout violation in C++ ...

GitHub user gregt5259 opened a pull request: https://github.com/apache/geode-native/pull/106 GEODE-2891 connect-timeout violation in C++ Native Client Pseudo message ID is added to recognize handshake message and use the correct time unit depending on the appropriate configuration p

RE: Different member-timeout for particular jvm’s

Hi, May be I was not clear in my last mail. My question is that can we monitor a jvm based on it’s own member timeout instead of the member timeout of some other jvm(which is monitoring the this jvm). Now if my view is [s1(coordinator), s2, s3, s4, s5] and member timeout for each member is diff

https://issues.apache.org/jira/browse/GEODE-3151

Hi Team, Please assign GEODE-3151 to me. Can anyone please review the pull request. Thanks, Dinesh Akhand This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at https://www.amdocs.com/about/email-discla

getSizeInBytes() return type

Hi, We implement getSizeInBytes() in from Sizeable interface. We have objects with size bigger than MAXINT, bigger than 2GB. What is the impact of refactoring the code to return long instead of int? I mean except the technical aspect of changing the return types of the calling functions etc. Whi