[GitHub] geode issue #397: Add junit to try parsing of simple XML file w pool ...

Github user oshvarts commented on the issue: https://github.com/apache/geode/pull/397 @metatype @kirklund could you move this forward please? --- 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

Re: One class loader vs multiple class loaders for deployed jars

There are certainly many projects in the OS community that have solved this same problem. Perhaps we can find a class loader from a project that would suite this need. Quick search of standalone frameworks comes up with a few popular hits: https://github.com/kamranzafar/JCL

[jira] [Created] (GEODE-2770) When using the REST API it is possible for the API to be accepting requests after the system has shutdown

Charlie Black created GEODE-2770: Summary: When using the REST API it is possible for the API to be accepting requests after the system has shutdown Key: GEODE-2770 URL:

[jira] [Commented] (GEODE-2217) Add generic type parameter to FunctionContext interface

[ https://issues.apache.org/jira/browse/GEODE-2217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15963756#comment-15963756 ] ASF GitHub Bot commented on GEODE-2217: --- GitHub user dalyssakim opened a pull request:

[GitHub] geode pull request #447: Feature/geode 2217

GitHub user dalyssakim opened a pull request: https://github.com/apache/geode/pull/447 Feature/geode 2217 JIRA : https://issues.apache.org/jira/browse/GEODE-2217 Let me know if we want to change the parameter descriptions. You can merge this pull request into a Git

[jira] [Created] (GEODE-2769) Document how to remove all cache listeners

Joey McAllister created GEODE-2769: -- Summary: Document how to remove all cache listeners Key: GEODE-2769 URL: https://issues.apache.org/jira/browse/GEODE-2769 Project: Geode Issue Type:

[jira] [Commented] (GEODE-2746) Investigate and Evaluate Existing RPC frameworks.

[ https://issues.apache.org/jira/browse/GEODE-2746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15963667#comment-15963667 ] Galen O'Sullivan commented on GEODE-2746: - Because Thrift doesn't support server push, I think it

[jira] [Updated] (GEODE-2746) Investigate and Evaluate Existing RPC frameworks.

[ https://issues.apache.org/jira/browse/GEODE-2746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Galen O'Sullivan updated GEODE-2746: Description: There are several existing RPC frameworks for which you can define the

[GitHub] geode issue #441: Fix a repetition in the README.

Github user galen-pivotal commented on the issue: https://github.com/apache/geode/pull/441 I'm not a committer, so someone else will have to push this for me. @kohlmu-pivotal ? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as

[jira] [Updated] (GEODE-288) Remove deprecated Admin API

[ https://issues.apache.org/jira/browse/GEODE-288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joey McAllister updated GEODE-288: -- Component/s: (was: docs) > Remove deprecated Admin API > --- > >

Broken: apache/geode#2318 (develop - 344f93d)

Build Update for apache/geode - Build: #2318 Status: Broken Duration: 21 minutes and 36 seconds Commit: 344f93d (develop) Author: Darrel Schneider Message: GEODE-2485: fix leak in tx suspend/resume The CCPTimer is now purged for every 1000 cancels done. So we

[jira] [Assigned] (GEODE-2768) Lucene Queries executed before index is fully created should be retried

[ https://issues.apache.org/jira/browse/GEODE-2768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Huynh reassigned GEODE-2768: -- Assignee: Jason Huynh > Lucene Queries executed before index is fully created should be

[jira] [Created] (GEODE-2768) Lucene Queries executed before index is fully created should be retried

Jason Huynh created GEODE-2768: -- Summary: Lucene Queries executed before index is fully created should be retried Key: GEODE-2768 URL: https://issues.apache.org/jira/browse/GEODE-2768 Project: Geode

[GitHub] geode pull request #446: GEODE-1274: Migration from PulseLogWriter to Log4j ...

GitHub user PurelyApplied opened a pull request: https://github.com/apache/geode/pull/446 GEODE-1274: Migration from PulseLogWriter to Log4j standard and removal of associated classes. * To avoid dependency on geode-core, the pulse loggers are instantiated directly from

Re: Shareable Filter Permission

There are no settings specific to Filters under Geode administration. I think you have to change this in the settings for Filters and Dashboard Sharing on your own Profile Preferences. You should also be able to hit "Share" while viewing a private Filter and then share it with specific people

Re: Review Request 58325: GEODE-2737: Change Pulse UI tests to use random port for JMX connections

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/58325/#review171502 --- Ship it! Ship It! - Jinmei Liao On April 10, 2017, 9:52

Re: Review Request 58325: GEODE-2737: Change Pulse UI tests to use random port for JMX connections

> On April 10, 2017, 10:05 p.m., Kirk Lund wrote: > > geode-pulse/src/test/java/org/apache/geode/tools/pulse/tests/rules/ServerRule.java > > Lines 47 (patched) > > > > > > Is there no other way to configure this

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

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

Re: Review Request 58325: GEODE-2737: Change Pulse UI tests to use random port for JMX connections

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/58325/#review171499 --- Ship it! Ship It! - Jared Stewart On April 10, 2017, 9:52

Shareable Filter Permission

Hi, Could I get the sharable filter permission in Geode? Right now my filters are all private. I'm fkrone Thanks, -Fred

[jira] [Commented] (GEODE-2647) ClientHealthStatsDUnitTest.testClientHealthStats_SubscriptionEnabled fails with NullPointerException

[ https://issues.apache.org/jira/browse/GEODE-2647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15963594#comment-15963594 ] Kirk Lund commented on GEODE-2647: -- >From Darrel Schneider , Mar 15, to dev: The

[jira] [Resolved] (GEODE-2485) CacheTransactionManager suspend/resume can leak memory for 30 minutes

[ https://issues.apache.org/jira/browse/GEODE-2485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider resolved GEODE-2485. - Resolution: Fixed Fix Version/s: 1.2.0 > CacheTransactionManager suspend/resume

[jira] [Commented] (GEODE-2485) CacheTransactionManager suspend/resume can leak memory for 30 minutes

[ https://issues.apache.org/jira/browse/GEODE-2485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15963579#comment-15963579 ] ASF subversion and git services commented on GEODE-2485: Commit

Re: Review Request 58325: GEODE-2737: Change Pulse UI tests to use random port for JMX connections

> On April 10, 2017, 10:05 p.m., Kirk Lund wrote: > > geode-pulse/src/test/java/org/apache/geode/tools/pulse/tests/rules/ServerRule.java > > Lines 47 (patched) > > > > > > Is there no other way to configure this

[GitHub] geode pull request #445: GEODE-2767: Added DUnitTests to validate export log...

GitHub user PurelyApplied opened a pull request: https://github.com/apache/geode/pull/445 GEODE-2767: Added DUnitTests to validate export log options --group and --member. Only affects test code. precheckin running. You can merge this pull request into a Git repository by

[jira] [Commented] (GEODE-2767) Extend testing coverage of export logs

[ https://issues.apache.org/jira/browse/GEODE-2767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15963563#comment-15963563 ] ASF GitHub Bot commented on GEODE-2767: --- GitHub user PurelyApplied opened a pull request:

Re: Review Request 58325: GEODE-2737: Change Pulse UI tests to use random port for JMX connections

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/58325/#review171495 ---

[jira] [Created] (GEODE-2767) Extend testing coverage of export logs

Patrick Rhomberg created GEODE-2767: --- Summary: Extend testing coverage of export logs Key: GEODE-2767 URL: https://issues.apache.org/jira/browse/GEODE-2767 Project: Geode Issue Type: Test

[jira] [Assigned] (GEODE-2767) Extend testing coverage of export logs

[ https://issues.apache.org/jira/browse/GEODE-2767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Rhomberg reassigned GEODE-2767: --- Assignee: Patrick Rhomberg > Extend testing coverage of export logs >

Review Request 58325: GEODE-2737: Change Pulse UI tests to use random port for JMX connections

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

[jira] [Commented] (GEODE-2737) PulseAuthTest failures

[ https://issues.apache.org/jira/browse/GEODE-2737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15963525#comment-15963525 ] ASF subversion and git services commented on GEODE-2737: Commit

[jira] [Commented] (GEODE-2766) Only apply patches for dependencies on relevant architectures

[ https://issues.apache.org/jira/browse/GEODE-2766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15963520#comment-15963520 ] ASF GitHub Bot commented on GEODE-2766: --- GitHub user jdeppe-pivotal opened a pull request:

[GitHub] geode-native pull request #89: GEODE-2766: Only apply patches on Solaris

GitHub user jdeppe-pivotal opened a pull request: https://github.com/apache/geode-native/pull/89 GEODE-2766: Only apply patches on Solaris - This avoids trying to apply patches on Windows which can break if the source wasn't actually checked out by a Windows git. You can

Re: Review Request 58319: GEODE-2765: change gfsh help to use log4j levels

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/58319/#review171491 --- Ship it! Ship It! - Ken Howe On April 10, 2017, 9:06 p.m.,

[jira] [Assigned] (GEODE-2766) Only apply patches for dependencies on relevant architectures

[ https://issues.apache.org/jira/browse/GEODE-2766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jens Deppe reassigned GEODE-2766: - Assignee: Jens Deppe > Only apply patches for dependencies on relevant architectures >

Re: Why we shouldn't use RPC Frameworks for the New Geode Protocol

I don't like the idea of using someone else's messaging software for several reasons: * we may have needs that are beyond its capabilities * it may impose something like a broker or endpoint IDs that we have to deal with * it introduces more overhead per message and we will have no control

Re: Review Request 58319: GEODE-2765: change gfsh help to use log4j levels

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/58319/#review171486 --- Ship it! Ship It! - Jared Stewart On April 10, 2017, 9:06

Re: Jenkins karma (was Re: Blacklist asf904 for Geode nightly job)

Yea, thanks Mark! Anthony > On Apr 10, 2017, at 2:11 PM, Mark Bretl wrote: > > Hi Anthony, > > Look at that I do have karma for adding people to Jenkins. I have added you > to Jenkins. > > Please let me know if you have any issues. > > --Mark > > On Mon, Apr 10, 2017 at

Re: Review Request 58319: GEODE-2765: change gfsh help to use log4j levels

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/58319/#review171485 --- Ship it! Ship It! - Jinmei Liao On April 10, 2017, 9:06

Re: Review Request 58319: GEODE-2765: change gfsh help to use log4j levels

> On April 10, 2017, 7:48 p.m., Jared Stewart wrote: > > geode-core/src/main/java/org/apache/geode/management/internal/cli/i18n/CliStrings.java > > Line 2374 (original), 2377 (patched) > > > > > > One small oddity

[jira] [Commented] (GEODE-1274) Pulse logging does not appear in Geode log file.

[ https://issues.apache.org/jira/browse/GEODE-1274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15963488#comment-15963488 ] ASF GitHub Bot commented on GEODE-1274: --- Github user PurelyApplied closed the pull request at:

[GitHub] geode pull request #432: GEODE-1274: Migration from PulseLogWriter to Log4j ...

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

Re: Jenkins karma (was Re: Blacklist asf904 for Geode nightly job)

Hi Anthony, Look at that I do have karma for adding people to Jenkins. I have added you to Jenkins. Please let me know if you have any issues. --Mark On Mon, Apr 10, 2017 at 9:59 AM, William Markito Oliveira < william.mark...@gmail.com> wrote: > Hi Anthony, > > My karma is also limited,

Re: Review Request 58319: GEODE-2765: change gfsh help to use log4j levels

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/58319/ --- (Updated April 10, 2017, 9:06 p.m.) Review request for geode, Jinmei Liao,

Re: Review Request 58319: GEODE-2765: change gfsh help to use log4j levels

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/58319/ --- (Updated April 10, 2017, 9:04 p.m.) Review request for geode, Jinmei Liao,

Re: Review Request 58319: GEODE-2765: change gfsh help to use log4j levels

> On April 10, 2017, 7:48 p.m., Jared Stewart wrote: > > geode-core/src/main/java/org/apache/geode/management/internal/cli/i18n/CliStrings.java > > Line 2374 (original), 2377 (patched) > > > > > > One small oddity

Re: Review Request 58319: GEODE-2765: change gfsh help to use log4j levels

> On April 10, 2017, 7:48 p.m., Jared Stewart wrote: > > geode-core/src/main/java/org/apache/geode/management/internal/cli/i18n/CliStrings.java > > Line 2374 (original), 2377 (patched) > > > > > > One small oddity

Re: Review Request 58319: GEODE-2765: change gfsh help to use log4j levels

> On April 10, 2017, 7:48 p.m., Jared Stewart wrote: > > geode-core/src/main/java/org/apache/geode/management/internal/cli/i18n/CliStrings.java > > Line 2374 (original), 2377 (patched) > > > > > > One small oddity

Re: One class loader vs multiple class loaders for deployed jars

I think Jared started down this path because we had a custom classloader implementation that he was trying to get rid of -- that impl was pretty limited and forced loading of all classes up-front. Now the code uses fast classpath scanner and that old custom classloader can't be used. The old

Re: Why we shouldn't use RPC Frameworks for the New Geode Protocol

MQTT is an interesting idea but from the wiki page it sounds like it depends on a broker. In that architecture, would the server be the broker as well as a publisher and subscriber? Would the locator be the broker? Or would we introduce a separate broker, either third-party or bespoke? Sarge

Re: Why we shouldn't use RPC Frameworks for the New Geode Protocol

I am wondering why we are leaning so heavily toward RPC IDL rather than messaging standards. One of the big features of the client-server discussion around Geode is the ability to register interest and run Continuous Queries. Both of these behave more like messaging than RPCs. Beyond that all

Re: Review Request 58319: GEODE-2765: change gfsh help to use log4j levels

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/58319/#review171465 ---

Re: Review Request 58315: fix memory leak in transaction suspend/resume

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/58315/#review171463 --- Ship it! Ship It! - anilkumar gingade On April 10, 2017,

Re: Review Request 58319: GEODE-2765: change gfsh help to use log4j levels

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/58319/ --- (Updated April 10, 2017, 7:15 p.m.) Review request for geode, Jinmei Liao,

[jira] [Updated] (GEODE-2765) gfsh help should consistently use log4j log levels

[ https://issues.apache.org/jira/browse/GEODE-2765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-2765: - Summary: gfsh help should consistently use log4j log levels (was: gfsh help should reference log4j2 log

Review Request 58315: fix memory leak in transaction suspend/resume

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/58315/ --- Review request for geode, anilkumar gingade, Eric Shu, and Lynn Gallinat.

Review Request 58319: GEODE-2267: change gfsh help to use log4j levels

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/58319/ --- Review request for geode, Jinmei Liao, Jared Stewart, Ken Howe, and Patrick

[jira] [Updated] (GEODE-2764) Index entry not entered into cluster config xml if region name contains a function call like entrySet()

[ https://issues.apache.org/jira/browse/GEODE-2764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nabarun updated GEODE-2764: --- Summary: Index entry not entered into cluster config xml if region name contains a function call like

[jira] [Created] (GEODE-2765) gfsh help should reference log4j2 log levels

Kirk Lund created GEODE-2765: Summary: gfsh help should reference log4j2 log levels Key: GEODE-2765 URL: https://issues.apache.org/jira/browse/GEODE-2765 Project: Geode Issue Type: Bug

[jira] [Assigned] (GEODE-2765) gfsh help should reference log4j2 log levels

[ https://issues.apache.org/jira/browse/GEODE-2765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund reassigned GEODE-2765: Assignee: Kirk Lund > gfsh help should reference log4j2 log levels >

[jira] [Created] (GEODE-2764) Index entry not entered into cluster config xml if region name contains a function call like entry set

nabarun created GEODE-2764: -- Summary: Index entry not entered into cluster config xml if region name contains a function call like entry set Key: GEODE-2764 URL: https://issues.apache.org/jira/browse/GEODE-2764

Re: Why we shouldn't use RPC Frameworks for the New Geode Protocol

On Mon, Apr 10, 2017 at 10:47 AM, Bruce Schuchardt wrote: > I agree that key/value serialization is a separate issue and more related > to storage than communications. The thing I'm struggling with is how to > specify message metadata in an RPC IDL. I'm thinking of

[jira] [Resolved] (GEODE-2761) Docs: un-brand client cache plugin diagram

[ https://issues.apache.org/jira/browse/GEODE-2761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes resolved GEODE-2761. Resolution: Fixed > Docs: un-brand client cache plugin diagram >

[GitHub] geode-native issue #87: Docs: un-brand client cache plugin diagram

Github user davebarnes97 commented on the issue: https://github.com/apache/geode-native/pull/87 Approved and merged. --- 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

[GitHub] geode-native pull request #87: Docs: un-brand client cache plugin diagram

Github user davebarnes97 closed the pull request at: https://github.com/apache/geode-native/pull/87 --- 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

[jira] [Resolved] (GEODE-2537) Docs: redraw image to remove GemFire label

[ https://issues.apache.org/jira/browse/GEODE-2537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes resolved GEODE-2537. Resolution: Fixed > Docs: redraw image to remove GemFire label >

[GitHub] geode-native pull request #88: Feature/geode 2537 Docs: redraw delta propaga...

Github user davebarnes97 closed the pull request at: https://github.com/apache/geode-native/pull/88 --- 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

[GitHub] geode-native issue #88: Feature/geode 2537 Docs: redraw delta propagation im...

Github user davebarnes97 commented on the issue: https://github.com/apache/geode-native/pull/88 Change accepted & merged. --- 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

[jira] [Assigned] (GEODE-2662) Gfsh displays field value on wrong line!

[ https://issues.apache.org/jira/browse/GEODE-2662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Rhomberg reassigned GEODE-2662: --- Assignee: Patrick Rhomberg > Gfsh displays field value on wrong line! >

[GitHub] geode pull request #444: Feature/gem 1353

Github user jhuynh1 commented on a diff in the pull request: https://github.com/apache/geode/pull/444#discussion_r110718931 --- Diff: geode-core/src/main/java/org/apache/geode/internal/cache/BucketRegion.java --- @@ -1261,7 +1333,14 @@ void basicUpdateEntryVersion(EntryEventImpl

Re: Why we shouldn't use RPC Frameworks for the New Geode Protocol

I agree that key/value serialization is a separate issue and more related to storage than communications. The thing I'm struggling with is how to specify message metadata in an RPC IDL. I'm thinking of things like an eventID, transaction info, security principal, etc. The basic

Re: Why we shouldn't use RPC Frameworks for the New Geode Protocol

I have used plenty of RPC protocols that pass raw binary as input/output values because the types are not pre defined. All the frameworks mentioned support byte arrays. -Jake On Mon, Apr 10, 2017 at 10:36 AM Galen M O'Sullivan wrote: > Hi Jacob, > > The message protocol

Re: One class loader vs multiple class loaders for deployed jars

I think this would be a viable approach in principle, but it would require us to write a custom classloader implementation for what you have described as the application classloader, rather than simply using an implementation from the jdk. On Apr 10, 2017 10:30 AM, "Anthony Baker"

Re: Why we shouldn't use RPC Frameworks for the New Geode Protocol

Hi Jacob, The message protocol is conflated with user data serialization in pretty much all of these frameworks I've seen. If we define some RPC in Thrift, we have to specify the type of data that gets passed to the call. The type of that data is specified using the Thrift IDL, meaning it's a

Re: One class loader vs multiple class loaders for deployed jars

What about this: 1) Each jar is deployed into it’s own classloader. 2) If the classloader for jar1 is unable to load a class, it delegates to its parent which can load classes from siblings to jar1. The classloader hierarchy would be: bootstrap << system << application << (deploy jar)* where

One class loader vs multiple class loaders for deployed jars

There is last one implementation decision for GEODE-2290 that I'm torn about, namely having one classloader for all deployed jars vs having separate classloaders for each deployed jar. If we have one class loader, e.g. new UrlClassLoader(jar1, jar2), then: - Jar1 will be able to load

[GitHub] geode pull request #444: Feature/gem 1353

Github user bschuchardt commented on a diff in the pull request: https://github.com/apache/geode/pull/444#discussion_r110697384 --- Diff: geode-core/src/main/java/org/apache/geode/internal/cache/DistributedCacheOperation.java --- @@ -240,12 +240,37 @@ public boolean

[GitHub] geode pull request #444: Feature/gem 1353

Github user bschuchardt commented on a diff in the pull request: https://github.com/apache/geode/pull/444#discussion_r110699099 --- Diff: geode-core/src/main/java/org/apache/geode/internal/cache/DistributedCacheOperation.java --- @@ -240,12 +240,37 @@ public boolean

[GitHub] geode pull request #444: Feature/gem 1353

Github user bschuchardt commented on a diff in the pull request: https://github.com/apache/geode/pull/444#discussion_r110708948 --- Diff: geode-core/src/main/java/org/apache/geode/internal/cache/BucketRegion.java --- @@ -1261,7 +1333,14 @@ void

[GitHub] geode issue #404: Geode 2469

Github user ggreen commented on the issue: https://github.com/apache/geode/pull/404 @galen-pivotal and @metatype, are there any suggestions on how to move this pull request forward? --- If your project is set up for it, you can reply to this email and have your reply appear on

[GitHub] geode issue #404: Geode 2469

Github user ggreen commented on the issue: https://github.com/apache/geode/pull/404 @galen-pivotal and @metatype, are there any suggestions on how to move this pull request forward? --- If your project is set up for it, you can reply to this email and have your reply appear on

Re: Jenkins karma (was Re: Blacklist asf904 for Geode nightly job)

Hi Anthony, My karma is also limited, sorry. I believe only Roman (or infra) can change that... On Mon, Apr 10, 2017 at 11:46 AM, Anthony Baker wrote: > Anyone? > > > On Apr 7, 2017, at 11:32 AM, Anthony Baker wrote: > > > > I would like Jenkins karma so

Re: Jenkins karma (was Re: Blacklist asf904 for Geode nightly job)

On Mon, Apr 10, 2017 at 9:46 AM, Anthony Baker wrote: > Anyone? This should be done by Mark (current Chair). Mark, can you add Anthony to the Jenkins LDAP group? Thanks, Roman.

Jenkins karma (was Re: Blacklist asf904 for Geode nightly job)

Anyone? > On Apr 7, 2017, at 11:32 AM, Anthony Baker wrote: > > I would like Jenkins karma so I can explore running our tests from within a > docker container. William / Mark / Roman can you help me out? > > Thanks, > Anthony > > >> On Mar 21, 2017, at 3:14 PM, Anthony