[jira] [Created] (GEODE-10292) Upgrade boost to 1.79.0
Michael Oleske created GEODE-10292: -- Summary: Upgrade boost to 1.79.0 Key: GEODE-10292 URL: https://issues.apache.org/jira/browse/GEODE-10292 Project: Geode Issue Type: Task Reporter: Michael Oleske Upgrade boost to 1.79.0 as first step in supporting visual studio 2022 -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (GEODE-10291) Support Jammy (ubuntu 22.04)
Michael Oleske created GEODE-10291: -- Summary: Support Jammy (ubuntu 22.04) Key: GEODE-10291 URL: https://issues.apache.org/jira/browse/GEODE-10291 Project: Geode Issue Type: Task Components: native client Reporter: Michael Oleske Native client should compile on the latest (ubuntu 22.04) operating system. Consider including a new pipeline as part of this -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (GEODE-10131) Remove unused but set variable
Michael Oleske created GEODE-10131: -- Summary: Remove unused but set variable Key: GEODE-10131 URL: https://issues.apache.org/jira/browse/GEODE-10131 Project: Geode Issue Type: Task Components: native client Reporter: Michael Oleske When on AppleClang 13.1.6.13160021 on macOS 12.3, native client fails to compile due to warning as error -Wunused-but-set-variable Remove the offending lines to compile -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (GEODE-10120) Update Ruby Dependencies
Michael Oleske created GEODE-10120: -- Summary: Update Ruby Dependencies Key: GEODE-10120 URL: https://issues.apache.org/jira/browse/GEODE-10120 Project: Geode Issue Type: Task Components: native client Reporter: Michael Oleske We should update out of date ruby dependencies So that we keep on top of build process and security updates -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-9626) Field 'GeodeSessionStateCache._logger' is never assigned to, and will always have its default value null
[
https://issues.apache.org/jira/browse/GEODE-9626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17418784#comment-17418784
]
Michael Oleske commented on GEODE-9626:
---
This may be a duplicate of https://issues.apache.org/jira/browse/GEODE-9609 but
that issue has no description
> Field 'GeodeSessionStateCache._logger' is never assigned to, and will always
> have its default value null
>
>
> Key: GEODE-9626
> URL: https://issues.apache.org/jira/browse/GEODE-9626
> Project: Geode
> Issue Type: Task
> Components: native client
>Reporter: Michael Oleske
>Priority: Major
>
> When I run {{cmake --build}}
> Then I see no warnings in NetCoreBuilds
> Notes: When running {{cmake --build}}, there is a warning that pops up in
> NetCoreSessionState.cs
> {{NetCoreSessionState.cs(77,45): warning CS0649: Field
> 'GeodeSessionStateCache._logger' is never assigned to, and will always have
> its default value null
> [/Users/pivotal/workspace/geode-native/netcore/netcore-session/netcore-session.csproj]}}
> {{ 1 Warning(s)}}
> {{ 0 Error(s)}}
> It seems that {{_logger}} is used, but never initialized. I thought about
> deleting it but it looks like the logs would be useful. I'm not sure what to
> initialize it to since I'm outta practice on my c# skills
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (GEODE-9626) Field 'GeodeSessionStateCache._logger' is never assigned to, and will always have its default value null
Michael Oleske created GEODE-9626:
-
Summary: Field 'GeodeSessionStateCache._logger' is never assigned
to, and will always have its default value null
Key: GEODE-9626
URL: https://issues.apache.org/jira/browse/GEODE-9626
Project: Geode
Issue Type: Task
Components: native client
Reporter: Michael Oleske
When I run {{cmake --build}}
Then I see no warnings in NetCoreBuilds
Notes: When running {{cmake --build}}, there is a warning that pops up in
NetCoreSessionState.cs
{{NetCoreSessionState.cs(77,45): warning CS0649: Field
'GeodeSessionStateCache._logger' is never assigned to, and will always have its
default value null
[/Users/pivotal/workspace/geode-native/netcore/netcore-session/netcore-session.csproj]}}
{{ 1 Warning(s)}}
{{ 0 Error(s)}}
It seems that {{_logger}} is used, but never initialized. I thought about
deleting it but it looks like the logs would be useful. I'm not sure what to
initialize it to since I'm outta practice on my c# skills
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (GEODE-9161) No gradle 7 deprecation warnings
Michael Oleske created GEODE-9161: - Summary: No gradle 7 deprecation warnings Key: GEODE-9161 URL: https://issues.apache.org/jira/browse/GEODE-9161 Project: Geode Issue Type: Improvement Components: build Reporter: Michael Oleske Why this is important: At some point this project will update to gradle 7, and it is better to stay on top of things then behind Given I have cloned the geode repository When I run ./gradlew build --warning-mode=all Then I see no output about "This will fail in gradle 7.0" or "This is scheduled to be removed in Gradle 7.0" Notes: Not all warnings appear at first, you'll likely have to run with several times as you clean up There are some gradle 8.0 warnings. If you happen to clean those up nice! Otherwise ok to skip for now. There's some oddities with properties being hardcoded in other places to their deprecated name which probably requires real work. The following types of errors are in the project The testRuntime configuration has been deprecated for dependency declaration. This will fail with an error in Gradle 7.0. Please use the testRuntimeOnly configuration instead. Consult the upgrading guide for further information: https://docs.gradle.org/6.8.3/userguide/upgrading_version_5.html#dependencies_should_no_longer_be_declared_using_the_compile_and_runtime_configurations The compile configuration has been deprecated for dependency declaration. This will fail with an error in Gradle 7.0. Please use the implementation or api configuration instead. Consult the upgrading guide for further information: https://docs.gradle.org/6.8.3/userguide/upgrading_version_5.html#dependencies_should_no_longer_be_declared_using_the_compile_and_runtime_configurations The AbstractArchiveTask.baseName property has been deprecated. This is scheduled to be removed in Gradle 7.0. Please use the archiveBaseName property instead. See https://docs.gradle.org/6.8.3/dsl/org.gradle.api.tasks.bundling.AbstractArchiveTask.html#org.gradle.api.tasks.bundling.AbstractArchiveTask:baseName for more details. The configuration :extensions:geode-modules:compileOnly was resolved without accessing the project in a safe manner. This may happen when a configuration is resolved from a different project. This behaviour has been deprecated and is scheduled to be removed in Gradle 7.0. See https://docs.gradle.org/6.8.3/userguide/viewing_debugging_dependencies.html#sub:resolving-unsafe-configuration-resolution-errors for more details. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-8900) Bump sqlite and sqlite-netfx to latest
Michael Oleske created GEODE-8900: - Summary: Bump sqlite and sqlite-netfx to latest Key: GEODE-8900 URL: https://issues.apache.org/jira/browse/GEODE-8900 Project: Geode Issue Type: Improvement Components: native client Reporter: Michael Oleske Keep dependencies up to date, so bump these to latest https://system.data.sqlite.org/index.html/doc/trunk/www/downloads.wiki https://www.sqlite.org/download.html -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-8884) Update ACE to 7.0.0
Michael Oleske created GEODE-8884: - Summary: Update ACE to 7.0.0 Key: GEODE-8884 URL: https://issues.apache.org/jira/browse/GEODE-8884 Project: Geode Issue Type: Improvement Components: native client Reporter: Michael Oleske This is to track keeping our ACE dependency up to date. [ACE 7.0.0|https://github.com/DOCGroup/ACE_TAO/releases/tag/ACE%2BTAO-7_0_0] was released on January 25th -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-8842) Enforce no-used-but-marked-unused
Michael Oleske created GEODE-8842: - Summary: Enforce no-used-but-marked-unused Key: GEODE-8842 URL: https://issues.apache.org/jira/browse/GEODE-8842 Project: Geode Issue Type: Improvement Components: native client Reporter: Michael Oleske Given I compile the code without exempting no-used-but-marked-unused Then it should compile Note - was marked as a todo - gtest SCOPED_TRACE causes this so try only using this on the new integration tests -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-8676) Update bookbindery to latest
Michael Oleske created GEODE-8676: - Summary: Update bookbindery to latest Key: GEODE-8676 URL: https://issues.apache.org/jira/browse/GEODE-8676 Project: Geode Issue Type: Improvement Components: docs, native client Reporter: Michael Oleske [Bookbinder|https://github.com/pivotal-cf/bookbinder/releases] has a new release and we should keep the tools we use to build our docs up to date -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-8666) Enforce warning no-non-virtual-dtor
Michael Oleske created GEODE-8666: - Summary: Enforce warning no-non-virtual-dtor Key: GEODE-8666 URL: https://issues.apache.org/jira/browse/GEODE-8666 Project: Geode Issue Type: Improvement Components: native client Reporter: Michael Oleske Given I compile the code without exempting no-non-virtual-dtor Then it should compile Note - was marked as a todo -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-8596) Enforce No Old Style Cast as Error
Michael Oleske created GEODE-8596: - Summary: Enforce No Old Style Cast as Error Key: GEODE-8596 URL: https://issues.apache.org/jira/browse/GEODE-8596 Project: Geode Issue Type: Improvement Components: native client Reporter: Michael Oleske Given I compile the code without exempting no-old-style-cast Then it should compile Note - was marked as a todo -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-8571) Enforce no documentation
Michael Oleske created GEODE-8571: - Summary: Enforce no documentation Key: GEODE-8571 URL: https://issues.apache.org/jira/browse/GEODE-8571 Project: Geode Issue Type: Improvement Components: native client Reporter: Michael Oleske Given I compile the code without exempting no-documentation Then it should compile Note - was marked as a todo -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-8470) Clean up running containers and network after SNI Tests
Michael Oleske created GEODE-8470:
-
Summary: Clean up running containers and network after SNI Tests
Key: GEODE-8470
URL: https://issues.apache.org/jira/browse/GEODE-8470
Project: Geode
Issue Type: Improvement
Components: native client
Reporter: Michael Oleske
As a Geode Native developer
When I run the SNI Tests
Then I see no running containers or networks when {{docker ps -a}} and {{docker
network ls}}
Notes: The existing clean does not work as the {{docker-compose stop}} is
missing the file to use for stopping. {{docker container prune -f}} only
cleans up the containers created, not the network created
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (GEODE-8469) Enforce no-missing-variable-declarations
Michael Oleske created GEODE-8469: - Summary: Enforce no-missing-variable-declarations Key: GEODE-8469 URL: https://issues.apache.org/jira/browse/GEODE-8469 Project: Geode Issue Type: Improvement Components: native client Reporter: Michael Oleske Given I compile the code without exempting no-missing-variable-declarations Then it should compile Note - was marked as a todo -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-8468) Review use of switch statements with enums
[ https://issues.apache.org/jira/browse/GEODE-8468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Oleske updated GEODE-8468: -- Labels: GoodForNewContributors (was: ) > Review use of switch statements with enums > -- > > Key: GEODE-8468 > URL: https://issues.apache.org/jira/browse/GEODE-8468 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Michael Oleske >Priority: Major > Labels: GoodForNewContributors > > We should check our usage of switch statements with enums > Before we add more enums > Because readability is important > Notes: While working on GEODE-8340, it was determined that some of the > places where a switch statement over enums was used were cases where a switch > statement was not the best control structure. The goal here is prevent a > long unwieldy list of switch statements. There are a lot of places to > review, so it will probably be easiest to do this over several PRs, which may > require several stories. The places listed below does not mean all of them > need to be fixed, but they should all be reviewed for improvement. For > further context, check out the comments on the [pr for > 8340|https://github.com/apache/geode-native/pull/625] > cppcache/integration-test/testThinClientCq.cpp at line 156ish > cppcache/integration-test/testThinClientCq.cpp at line 220ish > cppcache/integration-test/testThinClientCqDurable.cpp at line 125ish > cppcache/integration-test/testThinClientSecurityCQAuthorizationMU.cppline > 119ish > cppcache/integration-test/testThinClientSecurityDurableCQAuthorizationMU.cpp > at line 1229ish > cppcache/integration/test/SimpleCqListener.cpp at line 43ish > cppcache/src/CqQueryImpl.cpp at line 548ish > cppcache/src/CqService.cpp at line 71ish > cppcache/src/LRUAction.cpp at line 47ish > cppcache/src/LocalRegion.cpp at line 2586ish > cppcache/src/LocalRegion.cpp at line 2639ish > cppcache/src/LocalRegion.cpp at line 2696ish > cppcache/src/LocalRegion.cpp at line 2715ish > cppcache/src/LocalRegion.cpp at line 2781ish > cppcache/src/PdxInstanceImpl.cpp at line 247ish > cppcache/src/PdxInstanceImpl.cpp at line 485ish > cppcache/src/PdxInstanceImpl.cpp at line 667ish > cppcache/src/PdxInstanceImpl.cpp at line 1136ish > cppcache/src/SerializationRegistry.cpp at line 182ish > cppcache/src/SerializationRegistry.cpp at line 259ish > cppcache/src/SerializationRegistry.cpp at line 626ish > cppcache/src/SerializationRegistry.cpp at line 703ish > cppcache/src/TcrConnection.cpp at line 1194ish > cppcache/src/TcrMessage.cpp at line 1015ish > tests/cpp/fwklib/IpcHandler.cpp at line 231ish > tests/cpp/security/XmlAuthzCredentialGenerator.hpp at line 107ish > tests/cpp/security/XmlAuthzCredentialGenerator.hpp at line 162ish -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-8468) Review use of switch statements with enums
Michael Oleske created GEODE-8468: - Summary: Review use of switch statements with enums Key: GEODE-8468 URL: https://issues.apache.org/jira/browse/GEODE-8468 Project: Geode Issue Type: Improvement Components: native client Reporter: Michael Oleske We should check our usage of switch statements with enums Before we add more enums Because readability is important Notes: While working on GEODE-8340, it was determined that some of the places where a switch statement over enums was used were cases where a switch statement was not the best control structure. The goal here is prevent a long unwieldy list of switch statements. There are a lot of places to review, so it will probably be easiest to do this over several PRs, which may require several stories. The places listed below does not mean all of them need to be fixed, but they should all be reviewed for improvement. For further context, check out the comments on the [pr for 8340|https://github.com/apache/geode-native/pull/625] cppcache/integration-test/testThinClientCq.cpp at line 156ish cppcache/integration-test/testThinClientCq.cpp at line 220ish cppcache/integration-test/testThinClientCqDurable.cpp at line 125ish cppcache/integration-test/testThinClientSecurityCQAuthorizationMU.cppline 119ish cppcache/integration-test/testThinClientSecurityDurableCQAuthorizationMU.cpp at line 1229ish cppcache/integration/test/SimpleCqListener.cpp at line 43ish cppcache/src/CqQueryImpl.cpp at line 548ish cppcache/src/CqService.cpp at line 71ish cppcache/src/LRUAction.cpp at line 47ish cppcache/src/LocalRegion.cpp at line 2586ish cppcache/src/LocalRegion.cpp at line 2639ish cppcache/src/LocalRegion.cpp at line 2696ish cppcache/src/LocalRegion.cpp at line 2715ish cppcache/src/LocalRegion.cpp at line 2781ish cppcache/src/PdxInstanceImpl.cpp at line 247ish cppcache/src/PdxInstanceImpl.cpp at line 485ish cppcache/src/PdxInstanceImpl.cpp at line 667ish cppcache/src/PdxInstanceImpl.cpp at line 1136ish cppcache/src/SerializationRegistry.cpp at line 182ish cppcache/src/SerializationRegistry.cpp at line 259ish cppcache/src/SerializationRegistry.cpp at line 626ish cppcache/src/SerializationRegistry.cpp at line 703ish cppcache/src/TcrConnection.cpp at line 1194ish cppcache/src/TcrMessage.cpp at line 1015ish tests/cpp/fwklib/IpcHandler.cpp at line 231ish tests/cpp/security/XmlAuthzCredentialGenerator.hpp at line 107ish tests/cpp/security/XmlAuthzCredentialGenerator.hpp at line 162ish -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-8426) Enforce warning no-shorten-64-to-32
[
https://issues.apache.org/jira/browse/GEODE-8426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Oleske reassigned GEODE-8426:
-
Assignee: Michael Oleske
> Enforce warning no-shorten-64-to-32
> ---
>
> Key: GEODE-8426
> URL: https://issues.apache.org/jira/browse/GEODE-8426
> Project: Geode
> Issue Type: Improvement
> Components: native client
>Reporter: Michael Oleske
>Assignee: Michael Oleske
>Priority: Major
>
> remove {{-Wno-shorten-64-to-32}} since it looks like it was already fixed by
> others
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (GEODE-8426) Enforce warning no-shorten-64-to-32
Michael Oleske created GEODE-8426:
-
Summary: Enforce warning no-shorten-64-to-32
Key: GEODE-8426
URL: https://issues.apache.org/jira/browse/GEODE-8426
Project: Geode
Issue Type: Improvement
Components: native client
Reporter: Michael Oleske
remove {{-Wno-shorten-64-to-32}} since it looks like it was already fixed by
others
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (GEODE-8340) Enforce Switch compiler warnings as errors
Michael Oleske created GEODE-8340: - Summary: Enforce Switch compiler warnings as errors Key: GEODE-8340 URL: https://issues.apache.org/jira/browse/GEODE-8340 Project: Geode Issue Type: Improvement Components: native client Reporter: Michael Oleske Given I compile the code without exempting no-switch-enum and no-implicit-fallthrough and no-covered-switch-default Then it should compile Note - was marked as a todo, seems reasonable to tackle all these at once -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-8307) Enforce No Shadow Field in Constructor as Error
Michael Oleske created GEODE-8307: - Summary: Enforce No Shadow Field in Constructor as Error Key: GEODE-8307 URL: https://issues.apache.org/jira/browse/GEODE-8307 Project: Geode Issue Type: Improvement Components: native client Reporter: Michael Oleske Given I compile the code without exempting no-shadow-field-in-constructor Then it should compile Note - was marked as a todo -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-8246) Enforce No Shadow as Error
Michael Oleske created GEODE-8246: - Summary: Enforce No Shadow as Error Key: GEODE-8246 URL: https://issues.apache.org/jira/browse/GEODE-8246 Project: Geode Issue Type: Improvement Components: native client Reporter: Michael Oleske Given I compile the code without exempting no-shadow Then it should compile Note - was marked as a todo -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-8207) Enforce No Unknown Pragmas as Error
[ https://issues.apache.org/jira/browse/GEODE-8207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Oleske updated GEODE-8207: -- Summary: Enforce No Unknown Pragmas as Error (was: Enforce No Unused Pragmas as Error) > Enforce No Unknown Pragmas as Error > --- > > Key: GEODE-8207 > URL: https://issues.apache.org/jira/browse/GEODE-8207 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Michael Oleske >Priority: Major > > Given I compile the code without exempting no-unused-pragmas > Then it should compile > Note - was marked as a todo -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-8207) Enforce No Unknown Pragmas as Error
[ https://issues.apache.org/jira/browse/GEODE-8207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Oleske updated GEODE-8207: -- Description: Given I compile the code without exempting no-unknown-pragmas Then it should compile Note - was marked as a todo was: Given I compile the code without exempting no-unused-pragmas Then it should compile Note - was marked as a todo > Enforce No Unknown Pragmas as Error > --- > > Key: GEODE-8207 > URL: https://issues.apache.org/jira/browse/GEODE-8207 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Michael Oleske >Priority: Major > > Given I compile the code without exempting no-unknown-pragmas > Then it should compile > Note - was marked as a todo -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-8207) Enforce No Unused Pragmas as Error
Michael Oleske created GEODE-8207: - Summary: Enforce No Unused Pragmas as Error Key: GEODE-8207 URL: https://issues.apache.org/jira/browse/GEODE-8207 Project: Geode Issue Type: Improvement Components: native client Reporter: Michael Oleske Given I compile the code without exempting no-unused-pragmas Then it should compile Note - was marked as a todo -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-8184) Enforece no-extra-semi
Michael Oleske created GEODE-8184:
-
Summary: Enforece no-extra-semi
Key: GEODE-8184
URL: https://issues.apache.org/jira/browse/GEODE-8184
Project: Geode
Issue Type: Improvement
Components: native client
Reporter: Michael Oleske
{{no-extra-semi}} was added as an exception to warnings as errors. This has a
todo and should be enforced.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (GEODE-8183) Travis Dockerfile doesn't match committed Dockerfile
Michael Oleske created GEODE-8183: - Summary: Travis Dockerfile doesn't match committed Dockerfile Key: GEODE-8183 URL: https://issues.apache.org/jira/browse/GEODE-8183 Project: Geode Issue Type: Bug Components: native client Reporter: Michael Oleske I'm not sure how geode-native keeps the Travis Dockerfile up to date, but it is not with the committed one. The docker image currently used by Travis has geode 1.12 while the committed one uses 1.9. It also fails to build because tzdata is interactive. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-7782) libACE 6.5.5 won't compile on Ubuntu>=19.10
[ https://issues.apache.org/jira/browse/GEODE-7782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Oleske resolved GEODE-7782. --- Resolution: Fixed > libACE 6.5.5 won't compile on Ubuntu>=19.10 > --- > > Key: GEODE-7782 > URL: https://issues.apache.org/jira/browse/GEODE-7782 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Michael Oleske >Priority: Major > > Since Ubuntu 19.10 removes XSI STREAMS declarations (see > https://sourceware.org/git/?p=glibc.git;a=commit;h=a0a0dc83173ce11ff45105fd32e5d14356cdfb9c), > ACE complains that `stropts.h` is missing. > This is resolved in ACE 6.5.7 (sha256 > b966eaa82281c17a9c869609e6a1cdc617aa13e1123a8fce5bde93cb266d1fea) > https://github.com/DOCGroup/ACE_TAO/releases/tag/ACE%2BTAO-6_5_7 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (GEODE-7782) libACE 6.5.5 won't compile on Ubuntu>=19.10
[ https://issues.apache.org/jira/browse/GEODE-7782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Oleske closed GEODE-7782. - > libACE 6.5.5 won't compile on Ubuntu>=19.10 > --- > > Key: GEODE-7782 > URL: https://issues.apache.org/jira/browse/GEODE-7782 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Michael Oleske >Priority: Major > > Since Ubuntu 19.10 removes XSI STREAMS declarations (see > https://sourceware.org/git/?p=glibc.git;a=commit;h=a0a0dc83173ce11ff45105fd32e5d14356cdfb9c), > ACE complains that `stropts.h` is missing. > This is resolved in ACE 6.5.7 (sha256 > b966eaa82281c17a9c869609e6a1cdc617aa13e1123a8fce5bde93cb266d1fea) > https://github.com/DOCGroup/ACE_TAO/releases/tag/ACE%2BTAO-6_5_7 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-7782) libACE 6.5.5 won't compile on Ubuntu>=19.10
[ https://issues.apache.org/jira/browse/GEODE-7782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Oleske updated GEODE-7782: -- Description: Since Ubuntu 19.10 removes XSI STREAMS declarations (see https://sourceware.org/git/?p=glibc.git;a=commit;h=a0a0dc83173ce11ff45105fd32e5d14356cdfb9c), ACE complains that `stropts.h` is missing. This is resolved in ACE 6.5.7 (sha256 b966eaa82281c17a9c869609e6a1cdc617aa13e1123a8fce5bde93cb266d1fea) https://github.com/DOCGroup/ACE_TAO/releases/tag/ACE%2BTAO-6_5_7 was: Since Ubuntu 19.10 removes XSI STREAMS declarations (see https://sourceware.org/git/?p=glibc.git;a=commit;h=a0a0dc83173ce11ff45105fd32e5d14356cdfb9c), ACE complains that `stropts.h` is missing. This is resolved in ACE 6.5.7 https://github.com/DOCGroup/ACE_TAO/releases/tag/ACE%2BTAO-6_5_7 > libACE 6.5.5 won't compile on Ubuntu>=19.10 > --- > > Key: GEODE-7782 > URL: https://issues.apache.org/jira/browse/GEODE-7782 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Michael Oleske >Priority: Major > > Since Ubuntu 19.10 removes XSI STREAMS declarations (see > https://sourceware.org/git/?p=glibc.git;a=commit;h=a0a0dc83173ce11ff45105fd32e5d14356cdfb9c), > ACE complains that `stropts.h` is missing. > This is resolved in ACE 6.5.7 (sha256 > b966eaa82281c17a9c869609e6a1cdc617aa13e1123a8fce5bde93cb266d1fea) > https://github.com/DOCGroup/ACE_TAO/releases/tag/ACE%2BTAO-6_5_7 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-7782) libACE 6.5.5 won't compile on Ubuntu>=19.10
Michael Oleske created GEODE-7782: - Summary: libACE 6.5.5 won't compile on Ubuntu>=19.10 Key: GEODE-7782 URL: https://issues.apache.org/jira/browse/GEODE-7782 Project: Geode Issue Type: Bug Components: native client Reporter: Michael Oleske Since Ubuntu 19.10 removes XSI STREAMS declarations (see https://sourceware.org/git/?p=glibc.git;a=commit;h=a0a0dc83173ce11ff45105fd32e5d14356cdfb9c), ACE complains that `stropts.h` is missing. This is resolved in ACE 6.5.7 https://github.com/DOCGroup/ACE_TAO/releases/tag/ACE%2BTAO-6_5_7 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7708) Cluster Management Service Doc Missing how to turn off and on
[ https://issues.apache.org/jira/browse/GEODE-7708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17016444#comment-17016444 ] Michael Oleske commented on GEODE-7708: --- I actually was not trying to disable it, I just was trying to explicitly tell Geode to have it on (even if it was redundant) to prove out a scenario. Turned out to be unrelated, but I had to search the github repository to find that flag name which didn't seem right. > Cluster Management Service Doc Missing how to turn off and on > - > > Key: GEODE-7708 > URL: https://issues.apache.org/jira/browse/GEODE-7708 > Project: Geode > Issue Type: Task > Components: docs, management >Reporter: Michael Oleske >Priority: Major > > Expected Result > To see `enable-management-rest-service` as a flag to turn on and off > Actual Result > No information on turning this on and off > Steps to reproduce > Visit the page > docs/guide/111/configuring/running/cluster-management-service.html" -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-7708) Cluster Management Service Doc Missing how to turn off and on
Michael Oleske created GEODE-7708: - Summary: Cluster Management Service Doc Missing how to turn off and on Key: GEODE-7708 URL: https://issues.apache.org/jira/browse/GEODE-7708 Project: Geode Issue Type: Task Components: docs, management Reporter: Michael Oleske Expected Result To see `enable-management-rest-service` as a flag to turn on and off Actual Result No information on turning this on and off Steps to reproduce Visit the page docs/guide/111/configuring/running/cluster-management-service.html" -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-7707) Tab completing `--url` on `connect` gives two default values
Michael Oleske created GEODE-7707: - Summary: Tab completing `--url` on `connect` gives two default values Key: GEODE-7707 URL: https://issues.apache.org/jira/browse/GEODE-7707 Project: Geode Issue Type: Bug Components: management Reporter: Michael Oleske Expected result To see a string indicating one default value such as "Default is 'http://localhost:7070/geode-mgmt/v1'" Actual result This string "optional --url: Indicates the base URL to the Manager's HTTP service. For example: 'http://:/gemfire/v1' Default is 'http://localhost:7070/geode-mgmt/v1'; no default value" Note the `Default is` and the `no default value` steps to reproduce execute `gfsh` execute `start locator` execute `disconnect` type `connect --url` press tab -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-7559) LGTM Container Contents never accessed TXOriginatorRecoveryProcessor.java
[ https://issues.apache.org/jira/browse/GEODE-7559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Oleske resolved GEODE-7559. --- Resolution: Duplicate duplicate of GEODE-7689 > LGTM Container Contents never accessed TXOriginatorRecoveryProcessor.java > - > > Key: GEODE-7559 > URL: https://issues.apache.org/jira/browse/GEODE-7559 > Project: Geode > Issue Type: Improvement >Reporter: Michael Oleske >Priority: Major > Time Spent: 1.5h > Remaining Estimate: 0h > > https://lgtm.com/projects/g/apache/geode/snapshot/34f63b2c4d9c643a4c099ce7e1bf544d3f51e719/files/geode-core/src/main/java/org/apache/geode/internal/cache/locks/TXOriginatorRecoveryProcessor.java?sort=name&dir=ASC&mode=heatmap#V61 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-7559) LGTM Container Contents never accessed TXOriginatorRecoveryProcessor.java
[ https://issues.apache.org/jira/browse/GEODE-7559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Oleske reassigned GEODE-7559: - Assignee: Michael Oleske > LGTM Container Contents never accessed TXOriginatorRecoveryProcessor.java > - > > Key: GEODE-7559 > URL: https://issues.apache.org/jira/browse/GEODE-7559 > Project: Geode > Issue Type: Improvement >Reporter: Michael Oleske >Assignee: Michael Oleske >Priority: Major > Time Spent: 1.5h > Remaining Estimate: 0h > > https://lgtm.com/projects/g/apache/geode/snapshot/34f63b2c4d9c643a4c099ce7e1bf544d3f51e719/files/geode-core/src/main/java/org/apache/geode/internal/cache/locks/TXOriginatorRecoveryProcessor.java?sort=name&dir=ASC&mode=heatmap#V61 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-7651) Provide docker target for geode-assembly
[
https://issues.apache.org/jira/browse/GEODE-7651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Oleske resolved GEODE-7651.
---
Resolution: Fixed
> Provide docker target for geode-assembly
>
>
> Key: GEODE-7651
> URL: https://issues.apache.org/jira/browse/GEODE-7651
> Project: Geode
> Issue Type: Improvement
> Components: build
>Reporter: Michael Oleske
>Assignee: Michael Oleske
>Priority: Major
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> It would be nice to provide a gradle target to build a docker image using the
> output of a {{./gradlew build}}. This would allow people who consume the
> Geode docker image to be able to use snapshots. And maybe a future story can
> be about hosting those snapshots on Geode's Google Cloud Repository
> Given {{./gradlew build}} has run successfully
> When I run {{./gradlew geode-assembly:docker}}
> Then I see {{geode:develop}} listed as an image in the command {{docker
> images}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-7651) Provide docker target for geode-assembly
[
https://issues.apache.org/jira/browse/GEODE-7651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Oleske updated GEODE-7651:
--
Fix Version/s: 1.12.0
> Provide docker target for geode-assembly
>
>
> Key: GEODE-7651
> URL: https://issues.apache.org/jira/browse/GEODE-7651
> Project: Geode
> Issue Type: Improvement
> Components: build
>Reporter: Michael Oleske
>Assignee: Michael Oleske
>Priority: Major
> Fix For: 1.12.0
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> It would be nice to provide a gradle target to build a docker image using the
> output of a {{./gradlew build}}. This would allow people who consume the
> Geode docker image to be able to use snapshots. And maybe a future story can
> be about hosting those snapshots on Geode's Google Cloud Repository
> Given {{./gradlew build}} has run successfully
> When I run {{./gradlew geode-assembly:docker}}
> Then I see {{geode:develop}} listed as an image in the command {{docker
> images}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-7651) Provide docker target for geode-assembly
[
https://issues.apache.org/jira/browse/GEODE-7651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17010216#comment-17010216
]
Michael Oleske commented on GEODE-7651:
---
To be clear, the outcome of this story *is not* to publish snapshots. It is
intended to give developers an easy way to get an image with the Geode bits
they have just built on their machine. Publishing was just an example of a fun
thing to do with this feature. Another story should be written up in jira for
publishing.
That said, can you link existing ASF Legal comments so I can see what the
current thoughts are?
> Provide docker target for geode-assembly
>
>
> Key: GEODE-7651
> URL: https://issues.apache.org/jira/browse/GEODE-7651
> Project: Geode
> Issue Type: Improvement
> Components: build
>Reporter: Michael Oleske
>Assignee: Michael Oleske
>Priority: Major
>
> It would be nice to provide a gradle target to build a docker image using the
> output of a {{./gradlew build}}. This would allow people who consume the
> Geode docker image to be able to use snapshots. And maybe a future story can
> be about hosting those snapshots on Geode's Google Cloud Repository
> Given {{./gradlew build}} has run successfully
> When I run {{./gradlew geode-assembly:docker}}
> Then I see {{geode:develop}} listed as an image in the command {{docker
> images}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (GEODE-7651) Provide docker target for geode-assembly
[
https://issues.apache.org/jira/browse/GEODE-7651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Oleske reassigned GEODE-7651:
-
Assignee: Michael Oleske
> Provide docker target for geode-assembly
>
>
> Key: GEODE-7651
> URL: https://issues.apache.org/jira/browse/GEODE-7651
> Project: Geode
> Issue Type: Improvement
> Components: build
>Reporter: Michael Oleske
>Assignee: Michael Oleske
>Priority: Major
>
> It would be nice to provide a gradle target to build a docker image using the
> output of a {{./gradlew build}}. This would allow people who consume the
> Geode docker image to be able to use snapshots. And maybe a future story can
> be about hosting those snapshots on Geode's Google Cloud Repository
> Given {{./gradlew build}} has run successfully
> When I run {{./gradlew geode-assembly:docker}}
> Then I see {{geode:develop}} listed as an image in the command {{docker
> images}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (GEODE-7651) Provide docker target for geode-assembly
Michael Oleske created GEODE-7651:
-
Summary: Provide docker target for geode-assembly
Key: GEODE-7651
URL: https://issues.apache.org/jira/browse/GEODE-7651
Project: Geode
Issue Type: Improvement
Components: build
Reporter: Michael Oleske
It would be nice to provide a gradle target to build a docker image using the
output of a {{./gradlew build}}. This would allow people who consume the Geode
docker image to be able to use snapshots. And maybe a future story can be
about hosting those snapshots on Geode's Google Cloud Repository
Given {{./gradlew build}} has run successfully
When I run {{./gradlew geode-assembly:docker}}
Then I see {{geode:develop}} listed as an image in the command {{docker images}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (GEODE-7560) LGTM Issues with JTAUtils.java
[ https://issues.apache.org/jira/browse/GEODE-7560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Oleske resolved GEODE-7560. --- Fix Version/s: 1.12.0 Resolution: Done > LGTM Issues with JTAUtils.java > -- > > Key: GEODE-7560 > URL: https://issues.apache.org/jira/browse/GEODE-7560 > Project: Geode > Issue Type: Improvement >Reporter: Michael Oleske >Assignee: Michael Oleske >Priority: Major > Fix For: 1.12.0 > > Time Spent: 20m > Remaining Estimate: 0h > > https://lgtm.com/projects/g/apache/geode/snapshot/34f63b2c4d9c643a4c099ce7e1bf544d3f51e719/files/geode-junit/src/main/java/org/apache/geode/internal/jta/JTAUtils.java?sort=name&dir=ASC&mode=heatmap -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-7560) LGTM Issues with JTAUtils.java
[ https://issues.apache.org/jira/browse/GEODE-7560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Oleske reassigned GEODE-7560: - Assignee: Michael Oleske > LGTM Issues with JTAUtils.java > -- > > Key: GEODE-7560 > URL: https://issues.apache.org/jira/browse/GEODE-7560 > Project: Geode > Issue Type: Improvement >Reporter: Michael Oleske >Assignee: Michael Oleske >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > https://lgtm.com/projects/g/apache/geode/snapshot/34f63b2c4d9c643a4c099ce7e1bf544d3f51e719/files/geode-junit/src/main/java/org/apache/geode/internal/jta/JTAUtils.java?sort=name&dir=ASC&mode=heatmap -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-7560) LGTM Issues with JTAUtils.java
Michael Oleske created GEODE-7560: - Summary: LGTM Issues with JTAUtils.java Key: GEODE-7560 URL: https://issues.apache.org/jira/browse/GEODE-7560 Project: Geode Issue Type: Improvement Reporter: Michael Oleske https://lgtm.com/projects/g/apache/geode/snapshot/34f63b2c4d9c643a4c099ce7e1bf544d3f51e719/files/geode-junit/src/main/java/org/apache/geode/internal/jta/JTAUtils.java?sort=name&dir=ASC&mode=heatmap -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-7559) LGTM Container Contents never accessed TXOriginatorRecoveryProcessor.java
Michael Oleske created GEODE-7559: - Summary: LGTM Container Contents never accessed TXOriginatorRecoveryProcessor.java Key: GEODE-7559 URL: https://issues.apache.org/jira/browse/GEODE-7559 Project: Geode Issue Type: Improvement Reporter: Michael Oleske https://lgtm.com/projects/g/apache/geode/snapshot/34f63b2c4d9c643a4c099ce7e1bf544d3f51e719/files/geode-core/src/main/java/org/apache/geode/internal/cache/locks/TXOriginatorRecoveryProcessor.java?sort=name&dir=ASC&mode=heatmap#V61 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-7558) LGTM Container Contents never accessed InternalLocator.java
Michael Oleske created GEODE-7558: - Summary: LGTM Container Contents never accessed InternalLocator.java Key: GEODE-7558 URL: https://issues.apache.org/jira/browse/GEODE-7558 Project: Geode Issue Type: Improvement Reporter: Michael Oleske https://lgtm.com/projects/g/apache/geode/snapshot/34f63b2c4d9c643a4c099ce7e1bf544d3f51e719/files/geode-core/src/main/java/org/apache/geode/distributed/internal/InternalLocator.java?sort=name&dir=ASC&mode=heatmap#V166 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-7549) LGTM Remove empty conditional in ClientProxyMembershipID.cpp
[ https://issues.apache.org/jira/browse/GEODE-7549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Oleske resolved GEODE-7549. --- Fix Version/s: 1.12.0 Resolution: Done > LGTM Remove empty conditional in ClientProxyMembershipID.cpp > - > > Key: GEODE-7549 > URL: https://issues.apache.org/jira/browse/GEODE-7549 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Michael Oleske >Assignee: Michael Oleske >Priority: Major > Fix For: 1.12.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > https://lgtm.com/projects/g/apache/geode-native/snapshot/4e74bfdd2b6d3483ec00dd764aeaf6ad2f6b2eee/files/cppcache/src/ClientProxyMembershipID.cpp?sort=name&dir=ASC&mode=heatmap#V364 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-7549) LGTM Remove empty conditional in ClientProxyMembershipID.cpp
[ https://issues.apache.org/jira/browse/GEODE-7549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Oleske reassigned GEODE-7549: - Assignee: Michael Oleske > LGTM Remove empty conditional in ClientProxyMembershipID.cpp > - > > Key: GEODE-7549 > URL: https://issues.apache.org/jira/browse/GEODE-7549 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Michael Oleske >Assignee: Michael Oleske >Priority: Major > Time Spent: 0.5h > Remaining Estimate: 0h > > https://lgtm.com/projects/g/apache/geode-native/snapshot/4e74bfdd2b6d3483ec00dd764aeaf6ad2f6b2eee/files/cppcache/src/ClientProxyMembershipID.cpp?sort=name&dir=ASC&mode=heatmap#V364 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-7549) LGTM Remove empty conditional in ClientProxyMembershipID.cpp
Michael Oleske created GEODE-7549: - Summary: LGTM Remove empty conditional in ClientProxyMembershipID.cpp Key: GEODE-7549 URL: https://issues.apache.org/jira/browse/GEODE-7549 Project: Geode Issue Type: Improvement Components: native client Reporter: Michael Oleske https://lgtm.com/projects/g/apache/geode-native/snapshot/4e74bfdd2b6d3483ec00dd764aeaf6ad2f6b2eee/files/cppcache/src/ClientProxyMembershipID.cpp?sort=name&dir=ASC&mode=heatmap#V364 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-7429) Chocolatey install of active Perl times out
Michael Oleske created GEODE-7429: - Summary: Chocolatey install of active Perl times out Key: GEODE-7429 URL: https://issues.apache.org/jira/browse/GEODE-7429 Project: Geode Issue Type: Task Components: native client Reporter: Michael Oleske It is timing out when using packer buuld-windows.json -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-7359) Update devtoolset-4-gcc-c++ for rhel image
[ https://issues.apache.org/jira/browse/GEODE-7359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Oleske updated GEODE-7359: -- Description: When installing devtoolset-4-gcc-c++ through our packer scripts, it fails as yum cannot find it (was: Currently we have a build-linux.json which is odd when we have both ubuntu and red hat) Summary: Update devtoolset-4-gcc-c++ for rhel image (was: Use consistent RHEL7 Naming for Packer scripts) > Update devtoolset-4-gcc-c++ for rhel image > -- > > Key: GEODE-7359 > URL: https://issues.apache.org/jira/browse/GEODE-7359 > Project: Geode > Issue Type: Task > Components: native client >Reporter: Michael Oleske >Assignee: Blake Bender >Priority: Major > > When installing devtoolset-4-gcc-c++ through our packer scripts, it fails as > yum cannot find it -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-7359) Use consistent RHEL7 Naming for Packer scripts
[ https://issues.apache.org/jira/browse/GEODE-7359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Oleske reassigned GEODE-7359: - Assignee: Blake Bender (was: Michael Oleske) > Use consistent RHEL7 Naming for Packer scripts > -- > > Key: GEODE-7359 > URL: https://issues.apache.org/jira/browse/GEODE-7359 > Project: Geode > Issue Type: Task > Components: native client >Reporter: Michael Oleske >Assignee: Blake Bender >Priority: Major > > Currently we have a build-linux.json which is odd when we have both ubuntu > and red hat -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-7359) Use consistent RHEL7 Naming for Packer scripts
[ https://issues.apache.org/jira/browse/GEODE-7359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Oleske reassigned GEODE-7359: - Assignee: Michael Oleske > Use consistent RHEL7 Naming for Packer scripts > -- > > Key: GEODE-7359 > URL: https://issues.apache.org/jira/browse/GEODE-7359 > Project: Geode > Issue Type: Task > Components: native client >Reporter: Michael Oleske >Assignee: Michael Oleske >Priority: Major > > Currently we have a build-linux.json which is odd when we have both ubuntu > and red hat -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-7359) Use consistent RHEL7 Naming for Packer scripts
Michael Oleske created GEODE-7359: - Summary: Use consistent RHEL7 Naming for Packer scripts Key: GEODE-7359 URL: https://issues.apache.org/jira/browse/GEODE-7359 Project: Geode Issue Type: Task Components: native client Reporter: Michael Oleske Currently we have a build-linux.json which is odd when we have both ubuntu and red hat -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-7347) Race condition between Cache and ClientMetadataService
[ https://issues.apache.org/jira/browse/GEODE-7347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Oleske resolved GEODE-7347. --- Resolution: Fixed > Race condition between Cache and ClientMetadataService > -- > > Key: GEODE-7347 > URL: https://issues.apache.org/jira/browse/GEODE-7347 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Matthew Reddington >Assignee: Michael Oleske >Priority: Major > Time Spent: 40m > Remaining Estimate: 0h > > It was discovered that the ClientMetadataService would call into CacheImpl, > which contains a backreference to Cache, and this could occur in the middle > of a Cache move, where the pimpl pointer was updated, but not the > backreference. > The solution will be to guard the pimpl during the move, so the Cache can > update it's pimpl and the backreference. There exists > CacheImpl::doIfDestroyNotPending that locks the pimpl while executing a > function to facilitate this. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-7347) Race condition between Cache and ClientMetadataService
[ https://issues.apache.org/jira/browse/GEODE-7347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Oleske reassigned GEODE-7347: - Assignee: Michael Oleske > Race condition between Cache and ClientMetadataService > -- > > Key: GEODE-7347 > URL: https://issues.apache.org/jira/browse/GEODE-7347 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Matthew Reddington >Assignee: Michael Oleske >Priority: Major > > It was discovered that the ClientMetadataService would call into CacheImpl, > which contains a backreference to Cache, and this could occur in the middle > of a Cache move, where the pimpl pointer was updated, but not the > backreference. > The solution will be to guard the pimpl during the move, so the Cache can > update it's pimpl and the backreference. There exists > CacheImpl::doIfDestroyNotPending that locks the pimpl while executing a > function to facilitate this. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-7347) Race condition between Cache and ClientMetadataService
[ https://issues.apache.org/jira/browse/GEODE-7347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Oleske reassigned GEODE-7347: - Assignee: (was: Michael Oleske) > Race condition between Cache and ClientMetadataService > -- > > Key: GEODE-7347 > URL: https://issues.apache.org/jira/browse/GEODE-7347 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Matthew Reddington >Priority: Major > > It was discovered that the ClientMetadataService would call into CacheImpl, > which contains a backreference to Cache, and this could occur in the middle > of a Cache move, where the pimpl pointer was updated, but not the > backreference. > The solution will be to guard the pimpl during the move, so the Cache can > update it's pimpl and the backreference. There exists > CacheImpl::doIfDestroyNotPending that locks the pimpl while executing a > function to facilitate this. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-7347) Race condition between Cache and ClientMetadataService
[ https://issues.apache.org/jira/browse/GEODE-7347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Oleske reassigned GEODE-7347: - Assignee: Michael Oleske > Race condition between Cache and ClientMetadataService > -- > > Key: GEODE-7347 > URL: https://issues.apache.org/jira/browse/GEODE-7347 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Matthew Reddington >Assignee: Michael Oleske >Priority: Major > > It was discovered that the ClientMetadataService would call into CacheImpl, > which contains a backreference to Cache, and this could occur in the middle > of a Cache move, where the pimpl pointer was updated, but not the > backreference. > The solution will be to guard the pimpl during the move, so the Cache can > update it's pimpl and the backreference. There exists > CacheImpl::doIfDestroyNotPending that locks the pimpl while executing a > function to facilitate this. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-7302) security-client-kspath should not be a property a user can set
Michael Oleske created GEODE-7302: - Summary: security-client-kspath should not be a property a user can set Key: GEODE-7302 URL: https://issues.apache.org/jira/browse/GEODE-7302 Project: Geode Issue Type: Task Components: native client Reporter: Michael Oleske h3. Why With the usage of `ssl-truststore`, users should not use `security-client-kspath`. `security-client-kspath` is not actually used by our code. *As a C++ developer* *I want * to not have properties that don't do anything *So that * I don't get confused h3. Acceptance Criteria *Given* that I have a C++ application *When* I set `security-client-kspath` *Then* I get an error saying that's not a property -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-7302) security-client-kspath should not be a property a user can set
[ https://issues.apache.org/jira/browse/GEODE-7302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Oleske updated GEODE-7302: -- Description: h3. Why With the usage of `ssl-truststore`, users should not use `security-client-kspath`. `security-client-kspath` is not actually used by our code. *As a C++ developer* *I want* to not have properties that don't do anything *So that* I don't get confused h3. Acceptance Criteria *Given* that I have a C++ application *When* I set `security-client-kspath` *Then* I get an error saying that's not a property was: h3. Why With the usage of `ssl-truststore`, users should not use `security-client-kspath`. `security-client-kspath` is not actually used by our code. *As a C++ developer* *I want * to not have properties that don't do anything *So that * I don't get confused h3. Acceptance Criteria *Given* that I have a C++ application *When* I set `security-client-kspath` *Then* I get an error saying that's not a property > security-client-kspath should not be a property a user can set > -- > > Key: GEODE-7302 > URL: https://issues.apache.org/jira/browse/GEODE-7302 > Project: Geode > Issue Type: Task > Components: native client >Reporter: Michael Oleske >Priority: Major > > h3. Why > With the usage of `ssl-truststore`, users should not use > `security-client-kspath`. `security-client-kspath` is not actually used by > our code. > *As a C++ developer* > *I want* to not have properties that don't do anything > *So that* I don't get confused > h3. Acceptance Criteria > *Given* that I have a C++ application > *When* I set `security-client-kspath` > *Then* I get an error saying that's not a property -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-7178) Older versions of Native Client broken in 1.9+ due to missing compatibility code
[
https://issues.apache.org/jira/browse/GEODE-7178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Oleske resolved GEODE-7178.
---
Fix Version/s: 1.11.0
Assignee: Michael Oleske
Resolution: Fixed
> Older versions of Native Client broken in 1.9+ due to missing compatibility
> code
>
>
> Key: GEODE-7178
> URL: https://issues.apache.org/jira/browse/GEODE-7178
> Project: Geode
> Issue Type: Bug
> Components: messaging
>Reporter: Blake Bender
>Assignee: Michael Oleske
>Priority: Major
> Fix For: 1.11.0
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> When getting a request to perform an operation, the code does not check for
> instance of Byte. Native client sends the operation as a Byte, which
> currently cause Geode to throws a
> {{java.lang.ClassCastException: class java.lang.Byte cannot be cast to class
> org.apache.geode.cache.Operation}}
>
> Server versions prior to 1.9.0 had a compatibility check for this Byte
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (GEODE-7190) Native Client should use latest protocol ordinal
Michael Oleske created GEODE-7190: - Summary: Native Client should use latest protocol ordinal Key: GEODE-7190 URL: https://issues.apache.org/jira/browse/GEODE-7190 Project: Geode Issue Type: Improvement Components: native client Reporter: Michael Oleske **We should** update the protocol ordinal version **Before we** make more communication changes **Because** working on an old version makes it difficult to communicate with the server. **Notes**: The current ordinal is 45, we should move to Geode 1.9.x version, which is 100 -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (GEODE-6626) Add new cache.gatewayreceiver.events.received micrometer counter
[ https://issues.apache.org/jira/browse/GEODE-6626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Oleske updated GEODE-6626: -- Fix Version/s: 1.10.0 > Add new cache.gatewayreceiver.events.received micrometer counter > > > Key: GEODE-6626 > URL: https://issues.apache.org/jira/browse/GEODE-6626 > Project: Geode > Issue Type: New Feature > Components: statistics >Reporter: Kirk Lund >Assignee: Michael Oleske >Priority: Major > Fix For: 1.10.0 > > Time Spent: 6.5h > Remaining Estimate: 0h > > Users of Geode need to understand better what the WAN communication > performance for their connected clusters looks like. > *As an Operator* when I am monitoring a cluster > *I want to* see the traffic flow of information between all my different > clusters > *So that* I can identify slowdowns or bottlenecks in my distributed system. > The count of 'gatewayQueueEvents' received from any sender by this receiver > that will be applied to this region on this gateway receivers site. > Type: Counter > Name: cache.gatewayreceiver.events.received > Tags: > * cluster.id > * member.name > * host.name > * region.name > * gateway.receiver.id -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (GEODE-6626) Add new cache.gatewayreceiver.events.received micrometer counter
[ https://issues.apache.org/jira/browse/GEODE-6626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Oleske closed GEODE-6626. - > Add new cache.gatewayreceiver.events.received micrometer counter > > > Key: GEODE-6626 > URL: https://issues.apache.org/jira/browse/GEODE-6626 > Project: Geode > Issue Type: New Feature > Components: statistics >Reporter: Kirk Lund >Assignee: Michael Oleske >Priority: Major > Time Spent: 6.5h > Remaining Estimate: 0h > > Users of Geode need to understand better what the WAN communication > performance for their connected clusters looks like. > *As an Operator* when I am monitoring a cluster > *I want to* see the traffic flow of information between all my different > clusters > *So that* I can identify slowdowns or bottlenecks in my distributed system. > The count of 'gatewayQueueEvents' received from any sender by this receiver > that will be applied to this region on this gateway receivers site. > Type: Counter > Name: cache.gatewayreceiver.events.received > Tags: > * cluster.id > * member.name > * host.name > * region.name > * gateway.receiver.id -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-6626) Add new cache.gatewayreceiver.events.received micrometer counter
[ https://issues.apache.org/jira/browse/GEODE-6626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Oleske resolved GEODE-6626. --- Resolution: Done > Add new cache.gatewayreceiver.events.received micrometer counter > > > Key: GEODE-6626 > URL: https://issues.apache.org/jira/browse/GEODE-6626 > Project: Geode > Issue Type: New Feature > Components: statistics >Reporter: Kirk Lund >Assignee: Michael Oleske >Priority: Major > Time Spent: 6.5h > Remaining Estimate: 0h > > Users of Geode need to understand better what the WAN communication > performance for their connected clusters looks like. > *As an Operator* when I am monitoring a cluster > *I want to* see the traffic flow of information between all my different > clusters > *So that* I can identify slowdowns or bottlenecks in my distributed system. > The count of 'gatewayQueueEvents' received from any sender by this receiver > that will be applied to this region on this gateway receivers site. > Type: Counter > Name: cache.gatewayreceiver.events.received > Tags: > * cluster.id > * member.name > * host.name > * region.name > * gateway.receiver.id -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-6600) Composite Meter Registry takes a lot of heap when regions created and destroyed
[ https://issues.apache.org/jira/browse/GEODE-6600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Oleske resolved GEODE-6600. --- Resolution: Fixed > Composite Meter Registry takes a lot of heap when regions created and > destroyed > --- > > Key: GEODE-6600 > URL: https://issues.apache.org/jira/browse/GEODE-6600 > Project: Geode > Issue Type: Bug > Components: statistics >Reporter: Michael Oleske >Assignee: Michael Oleske >Priority: Major > Time Spent: 40m > Remaining Estimate: 0h > > When creating and destroying lots of regions, we never remove region related > meters. This causes heap size to keep growing. > Please remove the meters -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-6600) Composite Meter Registry takes a lot of heap when regions created and destroyed
[ https://issues.apache.org/jira/browse/GEODE-6600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Oleske reassigned GEODE-6600: - Assignee: Michael Oleske > Composite Meter Registry takes a lot of heap when regions created and > destroyed > --- > > Key: GEODE-6600 > URL: https://issues.apache.org/jira/browse/GEODE-6600 > Project: Geode > Issue Type: Bug > Components: statistics >Reporter: Michael Oleske >Assignee: Michael Oleske >Priority: Major > Time Spent: 0.5h > Remaining Estimate: 0h > > When creating and destroying lots of regions, we never remove region related > meters. This causes heap size to keep growing. > Please remove the meters -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-6600) Composite Meter Registry takes a lot of heap when regions created and destroyed
Michael Oleske created GEODE-6600: - Summary: Composite Meter Registry takes a lot of heap when regions created and destroyed Key: GEODE-6600 URL: https://issues.apache.org/jira/browse/GEODE-6600 Project: Geode Issue Type: Bug Components: statistics Reporter: Michael Oleske When creating and destroying lots of regions, we never remove region related meters. This causes heap size to keep growing. Please remove the meters -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-6529) Generate metrics output for member get operations
[ https://issues.apache.org/jira/browse/GEODE-6529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Oleske updated GEODE-6529: -- Summary: Generate metrics output for member get operations (was: Generate metrics output for member get opterations) > Generate metrics output for member get operations > - > > Key: GEODE-6529 > URL: https://issues.apache.org/jira/browse/GEODE-6529 > Project: Geode > Issue Type: New Feature > Components: statistics >Reporter: Michael Oleske >Assignee: Kirk Lund >Priority: Major > Time Spent: 2h 20m > Remaining Estimate: 0h > > As an operator or developer > I want to be able to actively monitor my puts/gets for a region > So that I can establish a baseline and track performance over time. > GIVEN we have a Micrometer supported time series database > AND a data visualization tool attached to that database > WHEN the user asks the cache.region.operations to the data visualization tool > THEN they are able to view the count > AND they are able to use the tags/dimensions to differentiate between > Cluster (Distributed System ID), Host (by hostname), CacheServer (by Server > name), and Region (by region name) > cache.region.operations.puts: > * create > * put > * putIfAbsent > * replace -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-6529) Generate metrics output for member Operations Put and Get
Michael Oleske created GEODE-6529: - Summary: Generate metrics output for member Operations Put and Get Key: GEODE-6529 URL: https://issues.apache.org/jira/browse/GEODE-6529 Project: Geode Issue Type: New Feature Components: statistics Reporter: Michael Oleske As an operator or developer I want to be able to actively monitor my puts/gets for a region So that I can establish a baseline and track performance over time. GIVEN we have a Micrometer supported time series database AND a data visualization tool attached to that database WHEN the user asks the cache.region.operations to the data visualization tool THEN they are able to view the count AND they are able to use the tags/dimensions to differentiate between Cluster (Distributed System ID), Host (by hostname), CacheServer (by Server name), and Region (by region name) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-6528) Generate Metrics for Memory Usage
Michael Oleske created GEODE-6528: - Summary: Generate Metrics for Memory Usage Key: GEODE-6528 URL: https://issues.apache.org/jira/browse/GEODE-6528 Project: Geode Issue Type: New Feature Components: statistics Reporter: Michael Oleske As an operator or developer I want to have the ability to actively monitor my memory used for a JVM on a host So that I can establish a baseline and track performance over time. GIVEN we have a Micrometer supported time series database AND a data visualization tool attached to that database WHEN the cache.opeartions to the data visualization tool THEN they are able to view the sampled values of the average time it takes to do a put OR get operation in Geode AND they are able to use the tags/dimensions to differentiate between Cluster (Distributed System ID), Host (by hostname), and a member (by Member name for Server or Locator JVM). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-6416) CI failure: org.apache.geode.distributed.internal.InternalDistributedSystemTest > createsStatisticsManagerViaFactory
[ https://issues.apache.org/jira/browse/GEODE-6416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Oleske updated GEODE-6416: -- Component/s: statistics > CI failure: > org.apache.geode.distributed.internal.InternalDistributedSystemTest > > createsStatisticsManagerViaFactory > > > Key: GEODE-6416 > URL: https://issues.apache.org/jira/browse/GEODE-6416 > Project: Geode > Issue Type: Bug > Components: statistics >Reporter: Lynn Gallinat >Assignee: Kirk Lund >Priority: Major > Labels: pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > org.apache.geode.distributed.internal.InternalDistributedSystemTest > > createsStatisticsManagerViaFactory FAILED > java.lang.AssertionError: > Expecting: > > and actual: > > to refer to the same object > at > org.apache.geode.distributed.internal.InternalDistributedSystemTest.createsStatisticsManagerViaFactory(InternalDistributedSystemTest.java:79) > https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/UnitTestOpenJDK11/builds/399 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-6356) CI failure: PersistentPartitionedRegionRegressionTest.doesNotWaitForPreviousInstanceOfOnlineServer fails with suspect string
[
https://issues.apache.org/jira/browse/GEODE-6356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Oleske updated GEODE-6356:
--
Labels: observability (was: )
> CI failure:
> PersistentPartitionedRegionRegressionTest.doesNotWaitForPreviousInstanceOfOnlineServer
> fails with suspect string
>
>
> Key: GEODE-6356
> URL: https://issues.apache.org/jira/browse/GEODE-6356
> Project: Geode
> Issue Type: Bug
> Components: persistence, tests
>Reporter: Barry Oglesby
>Assignee: Kirk Lund
>Priority: Major
> Labels: observability
>
> PersistentPartitionedRegionRegressionTest.doesNotWaitForPreviousInstanceOfOnlineServer
> failed in DistributedTestOpenJDK8 CI run
> [361|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/361]
> with this suspect string:
> {noformat}
> org.apache.geode.internal.cache.partitioned.PersistentPartitionedRegionRegressionTest
> > doesNotWaitForPreviousInstanceOfOnlineServer FAILED
> java.lang.AssertionError: Suspicious strings were written to the log
> during this run.
> Fix the strings or use IgnoredException.addIgnoredException to ignore.
> ---
> Found suspect string in log4j at line 2052
> [error 2019/02/04 18:49:32.561 UTC
> tid=32] org.apache.geode.distributed.DistributedSystemDisconnectedException:
> This connection to a distributed system has been disconnected.
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-6394) Analyzed and pinpoint the issue with the latency degradation
[
https://issues.apache.org/jira/browse/GEODE-6394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Oleske updated GEODE-6394:
--
Description:
The benchmarks are failing with latency degradation of more than 5% when
comparing 1.8.0 to current develop (1.9.0).
This failure needs to be analyzed and pinpoint the issue why there is the
performance degradation in these benchmarks.
https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/Benchmark/builds/66
{{BENCHMARK FAILED:
org.apache.geode.benchmark.tests.PartitionedFunctionExecutionBenchmark average
latency is 5% worse than baseline.}}
https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/Benchmark/builds/67
{{BENCHMARK FAILED:
org.apache.geode.benchmark.tests.PartitionedFunctionExecutionBenchmark average
latency is 5% worse than baseline.}}
{{BENCHMARK FAILED:
org.apache.geode.benchmark.tests.PartitionedFunctionExecutionWithArgumentsBenchmark
average latency is 5% worse than baseline.}}
{{BENCHMARK FAILED:
org.apache.geode.benchmark.tests.ReplicatedFunctionExecutionBenchmark average
latency is 5% worse than baseline.}}
{{BENCHMARK FAILED:
org.apache.geode.benchmark.tests.ReplicatedFunctionExecutionWithArgumentsBenchmark
average latency is 5% worse than baseline.}}
{{BENCHMARK FAILED:
org.apache.geode.benchmark.tests.ReplicatedFunctionExecutionWithFiltersBenchmark
average latency is 5% worse than baseline.}}
was:
The benchmarks are failing with latency degradation of more than 5% when
comparing 1.8.0 to current develop (1.9.0).
This failure needs to be analyzed and pinpoint the issue why there is the
performance degradation in these benchmarks.
> Analyzed and pinpoint the issue with the latency degradation
>
>
> Key: GEODE-6394
> URL: https://issues.apache.org/jira/browse/GEODE-6394
> Project: Geode
> Issue Type: Bug
> Components: benchmarks
>Reporter: nabarun
>Assignee: Helena Bales
>Priority: Major
>
> The benchmarks are failing with latency degradation of more than 5% when
> comparing 1.8.0 to current develop (1.9.0).
> This failure needs to be analyzed and pinpoint the issue why there is the
> performance degradation in these benchmarks.
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/Benchmark/builds/66
> {{BENCHMARK FAILED:
> org.apache.geode.benchmark.tests.PartitionedFunctionExecutionBenchmark
> average latency is 5% worse than baseline.}}
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/Benchmark/builds/67
> {{BENCHMARK FAILED:
> org.apache.geode.benchmark.tests.PartitionedFunctionExecutionBenchmark
> average latency is 5% worse than baseline.}}
> {{BENCHMARK FAILED:
> org.apache.geode.benchmark.tests.PartitionedFunctionExecutionWithArgumentsBenchmark
> average latency is 5% worse than baseline.}}
> {{BENCHMARK FAILED:
> org.apache.geode.benchmark.tests.ReplicatedFunctionExecutionBenchmark average
> latency is 5% worse than baseline.}}
> {{BENCHMARK FAILED:
> org.apache.geode.benchmark.tests.ReplicatedFunctionExecutionWithArgumentsBenchmark
> average latency is 5% worse than baseline.}}
> {{BENCHMARK FAILED:
> org.apache.geode.benchmark.tests.ReplicatedFunctionExecutionWithFiltersBenchmark
> average latency is 5% worse than baseline.}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (GEODE-6345) StatSamplerStats jvmPauses stat may wrap to negative value
[ https://issues.apache.org/jira/browse/GEODE-6345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Oleske resolved GEODE-6345. --- Resolution: Resolved Fix Version/s: 1.9.0 > StatSamplerStats jvmPauses stat may wrap to negative value > -- > > Key: GEODE-6345 > URL: https://issues.apache.org/jira/browse/GEODE-6345 > Project: Geode > Issue Type: Bug > Components: statistics >Reporter: Michael Oleske >Assignee: Michael Oleske >Priority: Major > Labels: pull-request-available > Fix For: 1.9.0 > > Time Spent: 50m > Remaining Estimate: 0h > > StatSamplerStats jvmPauses stat may wrap to negative value. It will wrap to > negative values when incremented beyond Integer.MAX_VALUE. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-6335) StatSamplerStats jvmPauses may wrap to negative value
[ https://issues.apache.org/jira/browse/GEODE-6335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Oleske resolved GEODE-6335. --- Resolution: Duplicate > StatSamplerStats jvmPauses may wrap to negative value > - > > Key: GEODE-6335 > URL: https://issues.apache.org/jira/browse/GEODE-6335 > Project: Geode > Issue Type: Bug > Components: statistics >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > > StatSamplerStats jvmPauses is implemented as IntCounter. It will wrap to > negative value when incremented beyond Integer.MAX_VALUE. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-6345) StatSamplerStats jvmPauses stat may wrap to negative value
Michael Oleske created GEODE-6345: - Summary: StatSamplerStats jvmPauses stat may wrap to negative value Key: GEODE-6345 URL: https://issues.apache.org/jira/browse/GEODE-6345 Project: Geode Issue Type: Bug Components: statistics Reporter: Michael Oleske StatSamplerStats jvmPauses stat may wrap to negative value. It will wrap to negative values when incremented beyond Integer.MAX_VALUE. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-6345) StatSamplerStats jvmPauses stat may wrap to negative value
[ https://issues.apache.org/jira/browse/GEODE-6345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Oleske reassigned GEODE-6345: - Assignee: Michael Oleske > StatSamplerStats jvmPauses stat may wrap to negative value > -- > > Key: GEODE-6345 > URL: https://issues.apache.org/jira/browse/GEODE-6345 > Project: Geode > Issue Type: Bug > Components: statistics >Reporter: Michael Oleske >Assignee: Michael Oleske >Priority: Major > > StatSamplerStats jvmPauses stat may wrap to negative value. It will wrap to > negative values when incremented beyond Integer.MAX_VALUE. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (GEODE-4267) PersistentRecoveryOrderOldConfigDUnitTest.testCrashDuringPreparePersistentId fails intermittently due to DistributedSystemDisconnectedException suspect string
[
https://issues.apache.org/jira/browse/GEODE-4267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16756533#comment-16756533
]
Michael Oleske edited comment on GEODE-4267 at 1/30/19 8:23 PM:
Happened again on this PR [https://github.com/apache/geode/pull/3137] (which is
this build [https://concourse.apachegeode-ci.info/builds/33931])
http://files.apachegeode-ci.info/builds/apache-develop-pr/geode-pr-3137/test-results/distributedTest/1548875823/
Test report artifacts from this job are available at:
http://files.apachegeode-ci.info/builds/apache-develop-pr/geode-pr-3137/test-artifacts/1548875823/distributedtestfiles-geode-pr-3137.tgz
was (Author: mole...@pivotal.io):
Happened again on this PR [https://github.com/apache/geode/pull/3137] (which is
this build [https://concourse.apachegeode-ci.info/builds/33931])
> PersistentRecoveryOrderOldConfigDUnitTest.testCrashDuringPreparePersistentId
> fails intermittently due to DistributedSystemDisconnectedException suspect
> string
> --
>
> Key: GEODE-4267
> URL: https://issues.apache.org/jira/browse/GEODE-4267
> Project: Geode
> Issue Type: Bug
> Components: persistence, tests
>Reporter: Kirk Lund
>Assignee: Mark Hanson
>Priority: Minor
> Labels: Flaky
> Attachments: GEODE-4267-standard-output.txt,
> lynn-findfailures-11-26-2018-15-25-48-logs.tgz
>
>
> {noformat}
> org.apache.geode.internal.cache.persistence.PersistentRecoveryOrderOldConfigDUnitTest
> > testCrashDuringPreparePersistentId FAILED
> java.lang.RuntimeException:
> org.apache.geode.distributed.DistributedSystemDisconnectedException: This
> connection to a distributed system has been disconnected.
> Caused by:
> org.apache.geode.distributed.DistributedSystemDisconnectedException:
> This connection to a distributed system has been disconnected.
> java.lang.AssertionError: Suspicious strings were written to the log
> during this run.
> Fix the strings or use IgnoredException.addIgnoredException to ignore.
> ---
> Found suspect string in log4j at line 1443
> [error 2017/12/16 00:50:26.778 UTC
> tid=0x1b]
> org.apache.geode.distributed.DistributedSystemDisconnectedException: This
> connection to a distributed system has been disconnected.
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-4267) PersistentRecoveryOrderOldConfigDUnitTest.testCrashDuringPreparePersistentId fails intermittently due to DistributedSystemDisconnectedException suspect string
[
https://issues.apache.org/jira/browse/GEODE-4267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16756533#comment-16756533
]
Michael Oleske commented on GEODE-4267:
---
Happened again on this PR [https://github.com/apache/geode/pull/3137] (which is
this build [https://concourse.apachegeode-ci.info/builds/33931])
> PersistentRecoveryOrderOldConfigDUnitTest.testCrashDuringPreparePersistentId
> fails intermittently due to DistributedSystemDisconnectedException suspect
> string
> --
>
> Key: GEODE-4267
> URL: https://issues.apache.org/jira/browse/GEODE-4267
> Project: Geode
> Issue Type: Bug
> Components: persistence, tests
>Reporter: Kirk Lund
>Assignee: Mark Hanson
>Priority: Minor
> Labels: Flaky
> Attachments: GEODE-4267-standard-output.txt,
> lynn-findfailures-11-26-2018-15-25-48-logs.tgz
>
>
> {noformat}
> org.apache.geode.internal.cache.persistence.PersistentRecoveryOrderOldConfigDUnitTest
> > testCrashDuringPreparePersistentId FAILED
> java.lang.RuntimeException:
> org.apache.geode.distributed.DistributedSystemDisconnectedException: This
> connection to a distributed system has been disconnected.
> Caused by:
> org.apache.geode.distributed.DistributedSystemDisconnectedException:
> This connection to a distributed system has been disconnected.
> java.lang.AssertionError: Suspicious strings were written to the log
> during this run.
> Fix the strings or use IgnoredException.addIgnoredException to ignore.
> ---
> Found suspect string in log4j at line 1443
> [error 2017/12/16 00:50:26.778 UTC
> tid=0x1b]
> org.apache.geode.distributed.DistributedSystemDisconnectedException: This
> connection to a distributed system has been disconnected.
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (GEODE-6341) "evictorJobsStarted" and "evictorJobsCompleted" should be counters
Michael Oleske created GEODE-6341: - Summary: "evictorJobsStarted" and "evictorJobsCompleted" should be counters Key: GEODE-6341 URL: https://issues.apache.org/jira/browse/GEODE-6341 Project: Geode Issue Type: Bug Components: statistics Reporter: Michael Oleske Inside of CachePerfStats there are Guages for "evictorJobsStarted" and "evictorJobsCompleted" Expected That "evictorJobsStarted" and "evictorJobsCompleted" are counters since they count things Actual "evictorJobsStarted" and "evictorJobsCompleted" are Guages -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-6341) "evictorJobsStarted" and "evictorJobsCompleted" should be counters
[ https://issues.apache.org/jira/browse/GEODE-6341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Oleske reassigned GEODE-6341: - Assignee: Michael Oleske > "evictorJobsStarted" and "evictorJobsCompleted" should be counters > -- > > Key: GEODE-6341 > URL: https://issues.apache.org/jira/browse/GEODE-6341 > Project: Geode > Issue Type: Bug > Components: statistics >Reporter: Michael Oleske >Assignee: Michael Oleske >Priority: Major > > Inside of CachePerfStats there are Guages for "evictorJobsStarted" and > "evictorJobsCompleted" > Expected > That "evictorJobsStarted" and "evictorJobsCompleted" are counters since they > count things > Actual > "evictorJobsStarted" and "evictorJobsCompleted" are Guages -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-6341) "evictorJobsStarted" and "evictorJobsCompleted" should be counters
[ https://issues.apache.org/jira/browse/GEODE-6341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Oleske reassigned GEODE-6341: - Assignee: Kirk Lund (was: Michael Oleske) > "evictorJobsStarted" and "evictorJobsCompleted" should be counters > -- > > Key: GEODE-6341 > URL: https://issues.apache.org/jira/browse/GEODE-6341 > Project: Geode > Issue Type: Bug > Components: statistics >Reporter: Michael Oleske >Assignee: Kirk Lund >Priority: Major > > Inside of CachePerfStats there are Guages for "evictorJobsStarted" and > "evictorJobsCompleted" > Expected > That "evictorJobsStarted" and "evictorJobsCompleted" are counters since they > count things > Actual > "evictorJobsStarted" and "evictorJobsCompleted" are Guages -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-6073) Spotless Check should not fail on Windows
[
https://issues.apache.org/jira/browse/GEODE-6073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Oleske resolved GEODE-6073.
---
Resolution: Workaround
> Spotless Check should not fail on Windows
> -
>
> Key: GEODE-6073
> URL: https://issues.apache.org/jira/browse/GEODE-6073
> Project: Geode
> Issue Type: Task
> Components: build
>Affects Versions: 1.9.0
>Reporter: Michael Oleske
>Assignee: Michael Oleske
>Priority: Major
> Labels: pull-request-available
> Time Spent: 40m
> Remaining Estimate: 0h
>
> _As a_ Engineer building on Windows
> _I want_ spotless to pass
> _So that_ I feel confident in changes I'm going to make
> *Given* I have freshly cloned Geode
> *When* I run {{.\gradlew.bat build}}
> *Then* I see a successful build with no Spotless errors
> Notes: This was based on the following conversation in the [dev
> list|https://markmail.org/message/2jippxjsl6a6r6ae]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-6073) Spotless Check should not fail on Windows
[
https://issues.apache.org/jira/browse/GEODE-6073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16747550#comment-16747550
]
Michael Oleske commented on GEODE-6073:
---
closing cause it seems I was able to fix this locally without a PR (at least
for now) by doing
{{C:\Projects\geode [develop ≡]> .\gradlew.bat spotlessApply}}
{{C:\Projects\geode [develop ≡]> git add .}}
And there were no changes to push. So ¯\_(ツ)_/¯
> Spotless Check should not fail on Windows
> -
>
> Key: GEODE-6073
> URL: https://issues.apache.org/jira/browse/GEODE-6073
> Project: Geode
> Issue Type: Task
> Components: build
>Affects Versions: 1.9.0
>Reporter: Michael Oleske
>Assignee: Michael Oleske
>Priority: Major
> Labels: pull-request-available
> Time Spent: 40m
> Remaining Estimate: 0h
>
> _As a_ Engineer building on Windows
> _I want_ spotless to pass
> _So that_ I feel confident in changes I'm going to make
> *Given* I have freshly cloned Geode
> *When* I run {{.\gradlew.bat build}}
> *Then* I see a successful build with no Spotless errors
> Notes: This was based on the following conversation in the [dev
> list|https://markmail.org/message/2jippxjsl6a6r6ae]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (GEODE-6213) http://geode.apache.org doesn't redirect to https://geode.apache.org
[ https://issues.apache.org/jira/browse/GEODE-6213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Oleske closed GEODE-6213. - > http://geode.apache.org doesn't redirect to https://geode.apache.org > > > Key: GEODE-6213 > URL: https://issues.apache.org/jira/browse/GEODE-6213 > Project: Geode > Issue Type: Improvement > Components: website >Reporter: Michael Oleske >Assignee: Dave Barnes >Priority: Major > Fix For: 1.9.0 > > > *As a* user of Geode > *I would like* to see https > *So that* I feel secure > _Given_ I open a browser > _When_ I visit http://geode.apache.org > _Then_ I get redirected to https://geode.apache.org > *Notes:* It also will help search engine ranking since using https is now a > consideration -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (GEODE-6240) Fix rat complaints
[
https://issues.apache.org/jira/browse/GEODE-6240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Oleske closed GEODE-6240.
-
> Fix rat complaints
> --
>
> Key: GEODE-6240
> URL: https://issues.apache.org/jira/browse/GEODE-6240
> Project: Geode
> Issue Type: Task
> Components: native client
>Reporter: Michael Oleske
>Assignee: Michael Oleske
>Priority: Major
> Labels: pull-request-available
> Time Spent: 40m
> Remaining Estimate: 0h
>
> {{packer/ubuntu/files/etc/systemd/system/update-hosts.service}} and
> {{packer/ubuntu/files/usr/local/bin/update-hosts.sh}} are missing licenses
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (GEODE-6240) Fix rat complaints
[
https://issues.apache.org/jira/browse/GEODE-6240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Oleske resolved GEODE-6240.
---
Resolution: Fixed
> Fix rat complaints
> --
>
> Key: GEODE-6240
> URL: https://issues.apache.org/jira/browse/GEODE-6240
> Project: Geode
> Issue Type: Task
> Components: native client
>Reporter: Michael Oleske
>Assignee: Michael Oleske
>Priority: Major
> Labels: pull-request-available
> Time Spent: 40m
> Remaining Estimate: 0h
>
> {{packer/ubuntu/files/etc/systemd/system/update-hosts.service}} and
> {{packer/ubuntu/files/usr/local/bin/update-hosts.sh}} are missing licenses
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (GEODE-6240) Fix rat complaints
[
https://issues.apache.org/jira/browse/GEODE-6240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Oleske reassigned GEODE-6240:
-
Assignee: Michael Oleske
> Fix rat complaints
> --
>
> Key: GEODE-6240
> URL: https://issues.apache.org/jira/browse/GEODE-6240
> Project: Geode
> Issue Type: Task
> Components: native client
>Reporter: Michael Oleske
>Assignee: Michael Oleske
>Priority: Major
>
> {{packer/ubuntu/files/etc/systemd/system/update-hosts.service}} and
> {{packer/ubuntu/files/usr/local/bin/update-hosts.sh}} are missing licenses
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (GEODE-6240) Fix rat complaints
Michael Oleske created GEODE-6240:
-
Summary: Fix rat complaints
Key: GEODE-6240
URL: https://issues.apache.org/jira/browse/GEODE-6240
Project: Geode
Issue Type: Task
Components: native client
Reporter: Michael Oleske
{{packer/ubuntu/files/etc/systemd/system/update-hosts.service}} and
{{packer/ubuntu/files/usr/local/bin/update-hosts.sh}} are missing licenses
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (GEODE-6229) Need an Ubuntu Packer image
[ https://issues.apache.org/jira/browse/GEODE-6229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Oleske reassigned GEODE-6229: - Assignee: Blake Bender > Need an Ubuntu Packer image > --- > > Key: GEODE-6229 > URL: https://issues.apache.org/jira/browse/GEODE-6229 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Blake Bender >Assignee: Blake Bender >Priority: Major > Labels: pull-request-available > Time Spent: 1h > Remaining Estimate: 0h > > As a user of NC, I need to be able to build/run on Ubuntu in addition to > RedHat. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-6213) http://geode.apache.org doesn't redirect to https://geode.apache.org
Michael Oleske created GEODE-6213: - Summary: http://geode.apache.org doesn't redirect to https://geode.apache.org Key: GEODE-6213 URL: https://issues.apache.org/jira/browse/GEODE-6213 Project: Geode Issue Type: Improvement Components: website Reporter: Michael Oleske *As a* user of Geode *I would like* to see https *So that* I feel secure _Given_ I open a browser _When_ I visit http://geode.apache.org _Then_ I get redirected to https://geode.apache.org *Notes:* It also will help search engine ranking since using https is now a consideration -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-6073) Spotless Check should not fail on Windows
[
https://issues.apache.org/jira/browse/GEODE-6073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Oleske resolved GEODE-6073.
---
Resolution: Fixed
Fix Version/s: 1.9.0
> Spotless Check should not fail on Windows
> -
>
> Key: GEODE-6073
> URL: https://issues.apache.org/jira/browse/GEODE-6073
> Project: Geode
> Issue Type: Task
> Components: build
>Reporter: Michael Oleske
>Assignee: Michael Oleske
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.9.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> _As a_ Engineer building on Windows
> _I want_ spotless to pass
> _So that_ I feel confident in changes I'm going to make
> *Given* I have freshly cloned Geode
> *When* I run {{.\gradlew.bat build}}
> *Then* I see a successful build with no Spotless errors
> Notes: This was based on the following conversation in the [dev
> list|https://markmail.org/message/2jippxjsl6a6r6ae]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (GEODE-6073) Spotless Check should not fail on Windows
[
https://issues.apache.org/jira/browse/GEODE-6073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Oleske reassigned GEODE-6073:
-
Assignee: Michael Oleske
> Spotless Check should not fail on Windows
> -
>
> Key: GEODE-6073
> URL: https://issues.apache.org/jira/browse/GEODE-6073
> Project: Geode
> Issue Type: Task
> Components: build
>Reporter: Michael Oleske
>Assignee: Michael Oleske
>Priority: Major
>
> _As a_ Engineer building on Windows
> _I want_ spotless to pass
> _So that_ I feel confident in changes I'm going to make
> *Given* I have freshly cloned Geode
> *When* I run {{.\gradlew.bat build}}
> *Then* I see a successful build with no Spotless errors
> Notes: This was based on the following conversation in the [dev
> list|https://markmail.org/message/2jippxjsl6a6r6ae]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (GEODE-6073) Spotless Check should not fail on Windows
Michael Oleske created GEODE-6073:
-
Summary: Spotless Check should not fail on Windows
Key: GEODE-6073
URL: https://issues.apache.org/jira/browse/GEODE-6073
Project: Geode
Issue Type: Task
Components: build
Reporter: Michael Oleske
_As a_ Engineer building on Windows
_I want_ spotless to pass
_So that_ I feel confident in changes I'm going to make
*Given* I have freshly cloned Geode
*When* I run {{.\gradlew.bat build}}
*Then* I see a successful build with no Spotless errors
Notes: This was based on the following conversation in the [dev
list|https://markmail.org/message/2jippxjsl6a6r6ae]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (GEODE-3) Support JDK 9 on Geode
[ https://issues.apache.org/jira/browse/GEODE-3?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16630996#comment-16630996 ] Michael Oleske edited comment on GEODE-3 at 9/28/18 1:52 AM: - [~amb] Does this title still make sense? Java 9 is no longer supported and Java 11 came out on the 25th. And I think Java 10 is also no longer supported? was (Author: mole...@pivotal.io): Does this title still make sense? Java 9 is no longer supported and Java 11 came out on the 25th. And I think Java 10 is also no longer supported? > Support JDK 9 on Geode > -- > > Key: GEODE-3 > URL: https://issues.apache.org/jira/browse/GEODE-3 > Project: Geode > Issue Type: Improvement > Components: docs, general >Reporter: Pid >Priority: Major > Labels: pull-request-available > Time Spent: 7h 10m > Remaining Estimate: 0h > > JDK 9 Schedule: http://openjdk.java.net/projects/jdk9/ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-3) Support JDK 9 on Geode
[ https://issues.apache.org/jira/browse/GEODE-3?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16630996#comment-16630996 ] Michael Oleske commented on GEODE-3: Does this title still make sense? Java 9 is no longer supported and Java 11 came out on the 25th. And I think Java 10 is also no longer supported? > Support JDK 9 on Geode > -- > > Key: GEODE-3 > URL: https://issues.apache.org/jira/browse/GEODE-3 > Project: Geode > Issue Type: Improvement > Components: docs, general >Reporter: Pid >Priority: Major > Labels: pull-request-available > Time Spent: 7h 10m > Remaining Estimate: 0h > > JDK 9 Schedule: http://openjdk.java.net/projects/jdk9/ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-3200) ServerConnection.authzRequest is no longer used
[ https://issues.apache.org/jira/browse/GEODE-3200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Oleske resolved GEODE-3200. --- Resolution: Delivered > ServerConnection.authzRequest is no longer used > --- > > Key: GEODE-3200 > URL: https://issues.apache.org/jira/browse/GEODE-3200 > Project: Geode > Issue Type: Improvement > Components: client/server, security >Reporter: Galen O'Sullivan >Assignee: Michael Oleske >Priority: Major > Labels: pull-request-available, starter++ > Time Spent: 1h 20m > Remaining Estimate: 0h > > ServerConnection has a private member called authzRequest that is no longer > used. > ServerConnection.getAuthzRequest() is used in a few places, but may not be > relevant anymore. > authzRequest should be removed or used to cache the value if it can be > cached, and we should probably have a look at getAuthzRequest to make sure > it's still used. > This class is expected to undergo significant refactoring due to GEODE-3074, > you might want to have a chat with whoever is working on that to avoid merge > conflicts. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-3200) ServerConnection.authzRequest is no longer used
[ https://issues.apache.org/jira/browse/GEODE-3200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Oleske reassigned GEODE-3200: - Assignee: Michael Oleske > ServerConnection.authzRequest is no longer used > --- > > Key: GEODE-3200 > URL: https://issues.apache.org/jira/browse/GEODE-3200 > Project: Geode > Issue Type: Improvement > Components: client/server, security >Reporter: Galen O'Sullivan >Assignee: Michael Oleske >Priority: Major > Labels: pull-request-available, starter++ > Time Spent: 1h 20m > Remaining Estimate: 0h > > ServerConnection has a private member called authzRequest that is no longer > used. > ServerConnection.getAuthzRequest() is used in a few places, but may not be > relevant anymore. > authzRequest should be removed or used to cache the value if it can be > cached, and we should probably have a look at getAuthzRequest to make sure > it's still used. > This class is expected to undergo significant refactoring due to GEODE-3074, > you might want to have a chat with whoever is working on that to avoid merge > conflicts. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
