[GitHub] geode pull request #375: GEODE-2365: Replace gemfire with geode in clicache ...

GitHub user mmartell opened a pull request: https://github.com/apache/geode/pull/375 GEODE-2365: Replace gemfire with geode in clicache src. Note: There are some reformats being done by Visual Studio in both the csharp and the c++/cli sources. You can merge this pull request into

[GitHub] geode issue #374: GEODE-2369: Remove --dir option from export cluster-config

Github user jaredjstewart commented on the issue: https://github.com/apache/geode/pull/374 `HelpCommandsIntegrationTest` failed in precheckin. I've pushed a change to the properties file used by that test and started a new precheckin. --- If your project is set up for it, you can re

Re: buildSrc recompiles anytime I run a dunit test

Looks like you are using gradle 3.5, rather than the gradle wrapper we have checked in? For me, the buildSrc targets all report that they are up to date: ./gradlew -DdistributedTest.single=BasicDUnitTest geode-core:distributedTest Picked up JAVA_TOOL_OPTIONS: :buildSrc:compileJava UP-TO-DATE :bui

buildSrc recompiles anytime I run a dunit test

Right after I do a clean build, if I then execute a single dunit test via gradle, buildSrc recompiles again. Is this intentional? Is there a way to configure our build to not recompile it again? BUILD SUCCESSFUL Total time: 4 mins 34.685 secs /Users/klund/dev/geode_CLEAN [1424]$ gradle -Ddistribu

Re: Proposal to add new 'export artifacts' GFSH command

What about simply having --exclude and --include options that take a regex in order to exclude and include arbitrary files as per the users' choosing. --Jens On Mon, Jan 30, 2017 at 3:33 PM, Swapnil Bawaskar wrote: > On Mon, Jan 30, 2017 at 10:15 AM, Udo Kohlmeyer > wrote: > > > I think stats

Review Request 56106: GEODE-2395: add FlakyCategory to intermittently failing test

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/56106/ --- Review request for geode, Jared Stewart and Kevin Duling. Bugs: GEODE-2395 and

Review Request 56104: not to create AEQ for acceor

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/56104/ --- Review request for geode and Dan Smith. Bugs: GEODE-2384 https://issues.apa

Broken: apache/geode#1904 (release/1.1.0 - 6ae2e17)

Build Update for apache/geode - Build: #1904 Status: Broken Duration: 9 minutes and 49 seconds Commit: 6ae2e17 (release/1.1.0) Author: Bruce Schuchardt Message: GEODE-1965 Create backward-compatibility unit test framework previous commit broke some implementat

Broken: apache/geode#1905 (develop - 5a3d8e2)

Build Update for apache/geode - Build: #1905 Status: Broken Duration: 8 minutes and 18 seconds Commit: 5a3d8e2 (develop) Author: Kirk Lund Message: GEODE-1276: change to IntegrationTest and use caught exceptions See GEODE-1276 description for details. View th

Broken: apache/geode#1903 (develop - 8c11848)

Build Update for apache/geode - Build: #1903 Status: Broken Duration: 8 minutes and 2 seconds Commit: 8c11848 (develop) Author: Bruce Schuchardt Message: GEODE-2368 Need to fix log message in DirectChannel Prior to the membership rewrite for v1.0 we used a dif

[GitHub] geode issue #374: GEODE-2369: Remove --dir option from export cluster-config

Github user jaredjstewart commented on the issue: https://github.com/apache/geode/pull/374 Precheckin started --- 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 s

Re: Review Request 56099: GEODE-2250: gfsh -e connect will throw java.lang.StackOverflowError rather than prompt for username/password

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/56099/#review163601 --- Ship it! Ship It! - Jared Stewart On Jan. 30, 2017, 11:24 p.

Re: Review Request 56002: GEODE-1672 LRU region values are not recovered during disk recovery.

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/56002/#review163602 --- geode-core/src/test/java/org/apache/geode/internal/cache/Persiste

Re: Review Request 56099: GEODE-2250: gfsh -e connect will throw java.lang.StackOverflowError rather than prompt for username/password

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/56099/#review163600 --- Ship it! Ship It! - Kirk Lund On Jan. 30, 2017, 11:24 p.m.,

[GitHub] geode pull request #373: GEODE-2394: config Doxygen to use short names.

GitHub user echobravopapa opened a pull request: https://github.com/apache/geode/pull/373 GEODE-2394: config Doxygen to use short names. Fixes the issue with Windows max file path length being exceeded. You can merge this pull request into a Git repository by running: $ git pul

Re: Review Request 56099: GEODE-2250: gfsh -e connect will throw java.lang.StackOverflowError rather than prompt for username/password

> On Jan. 30, 2017, 3:28 p.m., Kirk Lund wrote: > > geode-core/src/main/java/org/apache/geode/management/internal/cli/commands/ShellCommands.java, > > line 405 > > > > > > What if just one of them is null? Do we wan

Re: Proposal to add new 'export artifacts' GFSH command

On Mon, Jan 30, 2017 at 10:15 AM, Udo Kohlmeyer wrote: > I think stats should always be included by default +1 stats should be included always. If they are not needed, users can use --include-stats=false. I'm not sure I like the --stats-only flag since the command becomes "export logs --sta

Re: Review Request 55742: [GEODE-2324] and what look like a few other bugs in the same method.

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/55742/#review163589 --- Ship it! Ship It! - Bruce Schuchardt On Jan. 30, 2017, 7:44

Re: Review Request 56099: GEODE-2250: gfsh -e connect will throw java.lang.StackOverflowError rather than prompt for username/password

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/56099/#review163587 --- geode-core/src/main/java/org/apache/geode/management/internal/cli

Review Request 56099: GEODE-2250: gfsh -e connect will throw java.lang.StackOverflowError rather than prompt for username/password

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/56099/ --- Review request for geode, Jinmei Liao, Jared Stewart, and Kirk Lund. Repository

Re: [DISCUSS] Release branch for 1.1.0

Thanks Bruce. There is one more ticket GEODE-2386, which Kirk is looking into it. -Hitesh From: Bruce Schuchardt To: dev@geode.apache.org Sent: Monday, January 30, 2017 2:21 PM Subject: Re: [DISCUSS] Release branch for 1.1.0 I'm done merging these two changes to release/1.1.0 Le

[Spring CI] Spring Data GemFire > Nightly-ApacheGeode > #455 has FAILED (11 tests failed, no failures were new)

--- Spring Data GemFire > Nightly-ApacheGeode > #455 failed. --- Scheduled 11/1666 tests failed, no failures were new. https://build.spring.io/browse/SGF-NAG-455

Re: Review Request 56093: GEODE-2368 Need to fix log message in DirectChannel

> On Jan. 30, 2017, 9:52 p.m., Galen O'Sullivan wrote: > > geode-core/src/main/java/org/apache/geode/internal/tcp/TCPConduit.java, > > line 927 > > > > > > The `getLocalAddr` / `getLocalAddress` / (and now) `getAddr

Re: Review Request 56101: GEODE-2393: Adding a test for afterSecondary partitionListener callback

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/56101/#review163585 --- Ship it! Ship It! - Dan Smith On Jan. 30, 2017, 10:26 p.m.,

Review Request 56101: GEODE-2393: Adding a test for afterSecondary partitionListener callback

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/56101/ --- Review request for geode, nabarun nag and Dan Smith. Repository: geode Descri

Re: [DISCUSS] Release branch for 1.1.0

I'm done merging these two changes to release/1.1.0 Le 1/30/2017 à 10:58 AM, Hitesh Khamesra a écrit : Sure. Lets include GEODE-2368 (Need to fix log message in DirectChannel) this as well. Thanks.Hitesh From: Bruce Schuchardt To: dev@geode.apache.org Sent: Monday, January 30, 201

Re: Build failed in Jenkins: Geode-release #39

Check out my comments on the GEODE-2386. This looks like a gradle bug. Kirk said he was going to look at seeing if we can work around it. -Dan On Mon, Jan 30, 2017 at 1:50 PM, Bruce Schuchardt wrote: > Hitesh, your classpath isn't empty. This is a comma-separated list so the > classpath is jus

Re: Review Request 56093: GEODE-2368 Need to fix log message in DirectChannel

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/56093/#review163575 --- geode-core/src/main/java/org/apache/geode/internal/tcp/TCPConduit

Re: Build failed in Jenkins: Geode-release #39

Hitesh, your classpath isn't empty. This is a comma-separated list so the classpath is just after "-classpath," Le 1/30/2017 à 1:17 PM, Hitesh Khamesra a écrit : I just ran this test locally and see classpath empty but test passes.. [/export/java/users/java_share/jdk/1.8.0_66/x86_64.linux/j

Re: Build failed in Jenkins: Geode-release #39

I just ran this test locally and see classpath empty but test passes..  [/export/java/users/java_share/jdk/1.8.0_66/x86_64.linux/jre/bin/java, -classpath, /poland1/users/hiteshk/work/geode/release110/gemfire/open/geode-lucene/build/classes/test:/poland1/users/hiteshk/work/geode/release110/gemfir

Re: Build failed in Jenkins: Geode-release #39

Seems to always be from line 220: Caused by: java.lang.RuntimeException: VMs did not start up within 120 seconds at org.apache.geode.test.dunit.standalone.DUnitLauncher.launch(DUnitLauncher.java:220) at org.apache.geode.test.dunit.standalone.DUnitLauncher.launchIfNeeded(DUnitLauncher.java:142) ...

Re: Build failed in Jenkins: Geode-release #39

I created GEODE-2386 for these "Unable to launch dunit VMs" failures. It looks like this may actually be a gradle bug. I wonder if the some of the changes for the backwards compatibility test framework somehow made it more likely for us to hit this bug, because we're seeing it frequently now. -Dan

Re: Review Request 55742: [GEODE-2324] and what look like a few other bugs in the same method.

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/55742/ --- (Updated Jan. 30, 2017, 7:44 p.m.) Review request for geode, Bruce Schuchardt,

Re: Review Request 55742: [GEODE-2324] and what look like a few other bugs in the same method.

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/55742/ --- (Updated Jan. 30, 2017, 7:40 p.m.) Review request for geode, Bruce Schuchardt,

Re: Review Request 55742: [GEODE-2324] and what look like a few other bugs in the same method.

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/55742/ --- (Updated Jan. 30, 2017, 7:33 p.m.) Review request for geode, Bruce Schuchardt,

Re: Review Request 56093: GEODE-2368 Need to fix log message in DirectChannel

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/56093/#review163556 --- Ship it! Ship It! - Udo Kohlmeyer On Jan. 30, 2017, 7:20 p.m

Re: Review Request 56091: GEODE-1276: change to IntegrationTest and use caught exceptions

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/56091/#review163554 --- Ship it! Ship It! - Kevin Duling On Jan. 30, 2017, 10:55 a.m

Re: Review Request 56093: GEODE-2368 Need to fix log message in DirectChannel

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/56093/#review163553 --- Ship it! Ship It! - Hitesh Khamesra On Jan. 30, 2017, 7:20 p

Re: Review Request 56093: GEODE-2368 Need to fix log message in DirectChannel

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/56093/ --- (Updated Jan. 30, 2017, 7:20 p.m.) Review request for geode, Galen O'Sullivan,

Re: [DISCUSS] Release branch for 1.1.0

Okay - I'm working on that ticket now. Le 1/30/2017 à 10:58 AM, Hitesh Khamesra a écrit : Sure. Lets include GEODE-2368 (Need to fix log message in DirectChannel) this as well. Thanks.Hitesh From: Bruce Schuchardt To: dev@geode.apache.org Sent: Monday, January 30, 2017 10:37 AM

Review Request 56093: GEODE-2368 Need to fix log message in DirectChannel

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/56093/ --- Review request for geode, Galen O'Sullivan, Hitesh Khamesra, and Udo Kohlmeyer.

[GitHub] geode pull request #367: GEODE-2370: First pass at a CONTRIBUTING document.

Github user echobravopapa closed the pull request at: https://github.com/apache/geode/pull/367 --- 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 i

Re: [DISCUSS] Release branch for 1.1.0

Sure. Lets include GEODE-2368 (Need to fix log message in DirectChannel) this as well. Thanks.Hitesh From: Bruce Schuchardt To: dev@geode.apache.org Sent: Monday, January 30, 2017 10:37 AM Subject: Re: [DISCUSS] Release branch for 1.1.0 I'd like to merge into 1.1.0 the change to t

Review Request 56091: GEODE-1276: change to IntegrationTest and use caught exceptions

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/56091/ --- Review request for geode, Jared Stewart and Kevin Duling. Bugs: GEODE-1276

[GitHub] geode pull request #371: [GEODE-2308] Change library names to for Apache Geo...

Github user pivotal-jbarrett closed the pull request at: https://github.com/apache/geode/pull/371 --- 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 featur

Re: [DISCUSS] Release branch for 1.1.0

I'd like to merge into 1.1.0 the change to the Host test class that I checked into develop today. It's breaking things for some people, so it would be nice to have in the 1.1.0 branch. Le 1/27/2017 à 11:00 AM, Hitesh Khamesra a écrit : I have created the release branch "release/1.1.0". Please

[GitHub] geode issue #367: GEODE-2370: First pass at a CONTRIBUTING document.

Github user pivotal-jbarrett commented on the issue: https://github.com/apache/geode/pull/367 Merged, please close. --- 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 wi

[GitHub] geode pull request #361: GEODE-2325: Improve tests for JarDeployer

Github user asfgit closed the pull request at: https://github.com/apache/geode/pull/361 --- 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 issue #371: [GEODE-2308] Change library names to for Apache Geode bran...

Github user echobravopapa commented on the issue: https://github.com/apache/geode/pull/371 LGTM. Naming conventions make sense per platform and allow our library to fit into the given ecosystems. --- If your project is set up for it, you can reply to this email and have your reply a

[GitHub] geode pull request #369: Feature/geode 2373

Github user mmartell closed the pull request at: https://github.com/apache/geode/pull/369 --- 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 ena

[GitHub] geode issue #369: Feature/geode 2373

Github user mmartell commented on the issue: https://github.com/apache/geode/pull/369 This closes #369. --- 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

Re: Review Request 56088: GEODE-2367: ResultCollector was not being cleared on bucket not found exception

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/56088/#review163536 --- Ship it! Ship It! - nabarun nag On Jan. 30, 2017, 5:44 p.m.,

[GitHub] geode issue #370: Feature/geode 2351

Github user mmartell commented on the issue: https://github.com/apache/geode/pull/370 This closes #370. --- 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

[GitHub] geode issue #372: Feature/geode 2342

Github user mmartell commented on the issue: https://github.com/apache/geode/pull/372 This closes #372. --- 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

Re: Proposal to add new 'export artifacts' GFSH command

I think stats should always be included by default maybe a '--stats-only' or '--logs-only' flag... On 1/30/17 10:08, Kevin Duling wrote: +1 to the idea of '--include-stats' If --include-stats is offered, there should also be a '--stats-only' flag. That way you can get logs, logs and stat

[GitHub] geode pull request #372: Feature/geode 2342

Github user mmartell closed the pull request at: https://github.com/apache/geode/pull/372 --- 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 ena

[GitHub] geode issue #372: Feature/geode 2342

Github user pivotal-jbarrett commented on the issue: https://github.com/apache/geode/pull/372 Merged, please close. --- 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 wi

Re: Proposal to add new 'export artifacts' GFSH command

+1 to the idea of '--include-stats' If --include-stats is offered, there should also be a '--stats-only' flag. That way you can get logs, logs and stats, or just stats. On Fri, Jan 27, 2017 at 11:30 AM, Swapnil Bawaskar wrote: > > > > > > > > There are some inconsistencies in the dest

[GitHub] geode issue #370: Feature/geode 2351

Github user pivotal-jbarrett commented on the issue: https://github.com/apache/geode/pull/370 Merged, please close pull request. --- 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

[GitHub] geode issue #369: Feature/geode 2373

Github user pivotal-jbarrett commented on the issue: https://github.com/apache/geode/pull/369 Merged, please close pull request. --- 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 e

[GitHub] geode pull request #372: Feature/geode 2342

GitHub user mmartell opened a pull request: https://github.com/apache/geode/pull/372 Feature/geode 2342 Fix formatting of earlier PR. You can merge this pull request into a Git repository by running: $ git pull https://github.com/mmartell/geode feature/GEODE-2342 Alternatively

[GitHub] geode pull request #358: GEODE-2342: Rename GemfireTypeIds class to GeodeTyp...

Github user mmartell closed the pull request at: https://github.com/apache/geode/pull/358 --- 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 ena

Review Request 56088: GEODE-2367: ResultCollector was not being cleared on bucket not found exception

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/56088/ --- Review request for geode, nabarun nag, Dan Smith, and xiaojian zhou. Repository

[GitHub] geode pull request #371: [GEODE-2308] Change library names to for Apache Geo...

GitHub user pivotal-jbarrett opened a pull request: https://github.com/apache/geode/pull/371 [GEODE-2308] Change library names to for Apache Geode branding. You can merge this pull request into a Git repository by running: $ git pull https://github.com/pivotal-jbarrett/geode f

Re: Parallel Gateway Sender with Replicated Region

Mike, No, parallel senders are not supported for replicated regions. Thats mainly because replicated regions don't have a notion of primaries. Thanks, Barry Oglesby On Mon, Jan 30, 2017 at 8:45 AM, Michael Stolz wrote: > Can we use a Parallel Gateway Sender with Replicated Region? > Or are we

Parallel Gateway Sender with Replicated Region

Can we use a Parallel Gateway Sender with Replicated Region? Or are we limited to Serial Gateway? -- Mike Stolz Principal Engineer, GemFire Product Manager Mobile: 631-835-4771

[GitHub] geode issue #367: GEODE-2370: First pass at a CONTRIBUTING document.

Github user echobravopapa commented on the issue: https://github.com/apache/geode/pull/367 The latest doc in PR has instructions on running a single ctest... --- 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

Build failed in Jenkins: Geode-nightly #732

See -- [...truncated 534 lines...] :geode-common:flakyTest :geode-common:integrationTest :geode-core:assemble :geode-core:checkMissedTests :geode-core:spotlessJavaCheck :geode-core:spotlessCheck :geode-core: