[jira] [Updated] (GEODE-10261) VMProvider.invokeAsync does not consistently use Generic types
[ https://issues.apache.org/jira/browse/GEODE-10261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker updated GEODE-10261: -- Labels: pull-request-available (was: needsTriage pull-request-available) > VMProvider.invokeAsync does not consistently use Generic types > -- > > Key: GEODE-10261 > URL: https://issues.apache.org/jira/browse/GEODE-10261 > Project: Geode > Issue Type: Improvement > Components: tests >Affects Versions: 1.14.4 >Reporter: Joris Melchior >Assignee: Patrick Johnsn >Priority: Minor > Labels: pull-request-available > > In the VMProvider class there are several invokeAsync methods with various > signatures and in some cases they come with Generic type parameters and in > some cases they don't. > It's possible that some of this is influenced by the use of > SerializableCallableIF vs. SerializableRunnableIF so we need to dig a little > deeper to find out to what degree we need to or can make changes here. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (GEODE-10261) VMProvider.invokeAsync does not consistently use Generic types
[ https://issues.apache.org/jira/browse/GEODE-10261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-10261: --- Labels: needsTriage pull-request-available (was: needsTriage) > VMProvider.invokeAsync does not consistently use Generic types > -- > > Key: GEODE-10261 > URL: https://issues.apache.org/jira/browse/GEODE-10261 > Project: Geode > Issue Type: Improvement > Components: tests >Affects Versions: 1.14.4 >Reporter: Joris Melchior >Assignee: Patrick Johnsn >Priority: Minor > Labels: needsTriage, pull-request-available > > In the VMProvider class there are several invokeAsync methods with various > signatures and in some cases they come with Generic type parameters and in > some cases they don't. > It's possible that some of this is influenced by the use of > SerializableCallableIF vs. SerializableRunnableIF so we need to dig a little > deeper to find out to what degree we need to or can make changes here. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (GEODE-10261) VMProvider.invokeAsync does not consistently use Generic types
[ https://issues.apache.org/jira/browse/GEODE-10261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joris Melchior updated GEODE-10261: --- Description: In the VMProvider class there are several invokeAsync methods with various signatures and in some cases they come with Generic type parameters and in some cases they don't. It's possible that some of this is influenced by the use of SerializableCallableIF vs. SerializableRunnableIF so we need to dig a little deeper to find out to what degree we need to or can make changes here. was: In the VMProvider class there are several invokeAsync methods with various signatures and in some cases they come with Generic type parameters and in some cases they don't. It's possible that some of this is influenced by the use of SerializableCallableIF vs. SerializableRunnableIF so we need to dig a little deeper to find out to what degree we need to make changes here. > VMProvider.invokeAsync does not consistently use Generic types > -- > > Key: GEODE-10261 > URL: https://issues.apache.org/jira/browse/GEODE-10261 > Project: Geode > Issue Type: Improvement > Components: tests >Affects Versions: 1.14.4 >Reporter: Joris Melchior >Priority: Minor > Labels: needsTriage > > In the VMProvider class there are several invokeAsync methods with various > signatures and in some cases they come with Generic type parameters and in > some cases they don't. > It's possible that some of this is influenced by the use of > SerializableCallableIF vs. SerializableRunnableIF so we need to dig a little > deeper to find out to what degree we need to or can make changes here. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (GEODE-10261) VMProvider.invokeAsync does not consistently use Generic types
[ https://issues.apache.org/jira/browse/GEODE-10261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joris Melchior updated GEODE-10261: --- Labels: needsTriage (was: ) > VMProvider.invokeAsync does not consistently use Generic types > -- > > Key: GEODE-10261 > URL: https://issues.apache.org/jira/browse/GEODE-10261 > Project: Geode > Issue Type: Improvement > Components: tests >Affects Versions: 1.14.4 >Reporter: Joris Melchior >Priority: Minor > Labels: needsTriage > > In the VMProvider class there are several invokeAsync methods with various > signatures and in some cases they come with Generic type parameters and in > some cases they don't. > It's possible that some of this is influenced by the use of > SerializableCallableIF vs. SerializableRunnableIF so we need to dig a little > deeper to find out to what degree we need to make changes here. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (GEODE-10261) VMProvider.invokeAsync does not consistently use Generic types
[ https://issues.apache.org/jira/browse/GEODE-10261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joris Melchior updated GEODE-10261: --- Priority: Minor (was: Major) > VMProvider.invokeAsync does not consistently use Generic types > -- > > Key: GEODE-10261 > URL: https://issues.apache.org/jira/browse/GEODE-10261 > Project: Geode > Issue Type: Improvement > Components: tests >Affects Versions: 1.14.4 >Reporter: Joris Melchior >Priority: Minor > > In the VMProvider class there are several invokeAsync methods with various > signatures and in some cases they come with Generic type parameters and in > some cases they don't. > It's possible that some of this is influenced by the use of > SerializableCallableIF vs. SerializableRunnableIF so we need to dig a little > deeper to find out to what degree we need to make changes here. -- This message was sent by Atlassian Jira (v8.20.7#820007)
