October 2019 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-10800) Checkstyle isn't looking for supplyAsync methods with no executor

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10800?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10800: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Checkstyle isn't looking for supplyAsync methods with no executor > ----------------------------------------------------------------- > > Key: ISPN-10800 > URL: https://issues.jboss.org/browse/ISPN-10800 > Project: Infinispan > Issue Type: Bug > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > Fix For: 10.0.0.Final > > > ISPN-10372 introduced a check to ensure we were only using the CompletionStage methods that supplied an executor. Unfortunately this missed the static `CompletableFuture` methods such as `supplyAsync` and `runAsync`. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10804) JCache tck-runner does not run interception tests

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-10804?page=com.atlassian.jira.plugin... ] Dan Berindei updated ISPN-10804: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/7466 > JCache tck-runner does not run interception tests > ------------------------------------------------- > > Key: ISPN-10804 > URL: https://issues.jboss.org/browse/ISPN-10804 > Project: Infinispan > Issue Type: Bug > Components: JCache, Test Suite - Core, Test Suite - Server > Affects Versions: 9.4.16.Final, 10.0.0.CR3 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 10.0.0.Final > > > Initially I thought the only way to make the interception TCK tests run was to add a {{@Priority}} annotation, which is not a good idea because even our tests expect to be able to switch between the managed or the managed interceptors. > But it turns out if we revert ISPN-10721 and unpack the TCK tests in our build output directory, we can override {{beans.xml}} and make the interception tests run. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10745) infinispan-jcache-remote does not support CDI caching annotations

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-10745?page=com.atlassian.jira.plugin... ] Dan Berindei updated ISPN-10745: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/7466 (was: https://github.com/infinispan/infinispan/pull/7420) > infinispan-jcache-remote does not support CDI caching annotations > ----------------------------------------------------------------- > > Key: ISPN-10745 > URL: https://issues.jboss.org/browse/ISPN-10745 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.4.16.Final, 10.0.0.CR3 > Reporter: Dan Berindei > Priority: Major > > {{infinispan-jcache-remote}} does not have CDI interceptors for the JCache annotations like {{@CacheResult}}, so the annotations are ignored. > The JCache TCK has tests for the annotations (e.g. {{InterceptionCacheNameOnEachMethodTest}}), but those tests used to pass by accident: a Weld dependency ({{slf4j-api}}) was missing in the {{tck-remote}} maven-failsafe-plugin execution, and {{AbstractInterceptionTest}} was automatically excluding them. > Weld 2.3.4.Final removed the {{slf4j-api}} dependency and the {{tck-remote}} interception tests started failing after the upgrade, but we did not notice because of ISPN-10379. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10798) JCache annotations attribute cacheResolverFactory is ignored

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-10798?page=com.atlassian.jira.plugin... ] Dan Berindei updated ISPN-10798: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/7466 > JCache annotations attribute cacheResolverFactory is ignored > ------------------------------------------------------------ > > Key: ISPN-10798 > URL: https://issues.jboss.org/browse/ISPN-10798 > Project: Infinispan > Issue Type: Bug > Components: JCache > Affects Versions: 9.4.16.Final, 10.0.0.CR3 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 10.0.0.Final > > > The JCache TCK doesn't seem to require support for {{cacheResolverFactory}}, but having it would allow us to have an alternative to the managed interceptors {{InjectedCache*Interceptor}} and to deprecate them. > We can then move the default interceptors to the jcache-commons module, so they support both embedded and remote caches. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10804) JCache tck-runner does not run interception tests

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-10804?page=com.atlassian.jira.plugin... ] Dan Berindei updated ISPN-10804: -------------------------------- Status: Open (was: New) > JCache tck-runner does not run interception tests > ------------------------------------------------- > > Key: ISPN-10804 > URL: https://issues.jboss.org/browse/ISPN-10804 > Project: Infinispan > Issue Type: Bug > Components: JCache, Test Suite - Core, Test Suite - Server > Affects Versions: 9.4.16.Final, 10.0.0.CR3 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 10.0.0.Final > > > Initially I thought the only way to make the interception TCK tests run was to add a {{@Priority}} annotation, which is not a good idea because even our tests expect to be able to switch between the managed or the managed interceptors. > But it turns out if we revert ISPN-10721 and unpack the TCK tests in our build output directory, we can override {{beans.xml}} and make the interception tests run. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10804) JCache tck-runner does not run interception tests

by Dan Berindei (Jira)

Dan Berindei created ISPN-10804: ----------------------------------- Summary: JCache tck-runner does not run interception tests Key: ISPN-10804 URL: https://issues.jboss.org/browse/ISPN-10804 Project: Infinispan Issue Type: Bug Components: JCache, Test Suite - Core, Test Suite - Server Affects Versions: 10.0.0.CR3, 9.4.16.Final Reporter: Dan Berindei Assignee: Dan Berindei Fix For: 10.0.0.Final Initially I thought the only way to make the interception TCK tests run was to add a {{@Priority}} annotation, which is not a good idea because even our tests expect to be able to switch between the managed or the managed interceptors. But it turns out if we revert ISPN-10721 and unpack the TCK tests in our build output directory, we can override {{beans.xml}} and make the interception tests run. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10802) Add sizeAsync method

by Will Burns (Jira)

[ https://issues.jboss.org/browse/ISPN-10802?page=com.atlassian.jira.plugin... ] Will Burns updated ISPN-10802: ------------------------------ Fix Version/s: 10.0.0.Final > Add sizeAsync method > -------------------- > > Key: ISPN-10802 > URL: https://issues.jboss.org/browse/ISPN-10802 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > Fix For: 10.0.0.Final > > > We have non blocking single response operations already. We should utilize this to add a new sizeAsync method. Currently users have to spawn a thread to do this. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10802) Add sizeAsync method

by Will Burns (Jira)

[ https://issues.jboss.org/browse/ISPN-10802?page=com.atlassian.jira.plugin... ] Will Burns updated ISPN-10802: ------------------------------ Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/7470 > Add sizeAsync method > -------------------- > > Key: ISPN-10802 > URL: https://issues.jboss.org/browse/ISPN-10802 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > > We have non blocking single response operations already. We should utilize this to add a new sizeAsync method. Currently users have to spawn a thread to do this. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10018) Observability: clean up logging categories

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10018?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10018: ----------------------------------- Description: For logs with level INFO, WARN, ERROR, FATAL we want to use specific categories instead of the fully-qualified class name. The following is a list of categories: * org.infinispan.CLUSTER: messages related to clustering (state transfer, rebalancing, partitioning, etc) * org.infinispan.CONFIG: messages related to configuration * org.infinispan.CONTAINER: messages related to the data container (e.g. expiration, eviction, listeners, transactions, etc) * org.infinispan.PERSISTENCE: messages related to loaders/stores * org.infinispan.SECURITY: messages related to security * org.infinispan.SERVER: messages related to server was: For logs with level INFO, WARN, ERROR, FATAL we want to use specific categories instead of the fully-qualified class name. The following is a list of categories: * org.infinispan.CLUSTER: messages related to clustering (state transfer, rebalancing, partitioning, etc) * org.infinispan.CONFIG: messages related to configuration * org.infinispan.PERSISTENCE: messages related to loaders/stores * org.infinispan.SECURITY: messages related to security * org.infinispan.CONTAINER: messages related to the data container (e.g. expiration, eviction, listeners, transactions, etc) > Observability: clean up logging categories > ------------------------------------------ > > Key: ISPN-10018 > URL: https://issues.jboss.org/browse/ISPN-10018 > Project: Infinispan > Issue Type: Sub-task > Components: JMX, reporting and management > Affects Versions: 10.0.0.Beta2 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.0.0.Final > > > For logs with level INFO, WARN, ERROR, FATAL we want to use specific categories instead of the fully-qualified class name. > The following is a list of categories: > * org.infinispan.CLUSTER: messages related to clustering (state transfer, rebalancing, partitioning, etc) > * org.infinispan.CONFIG: messages related to configuration > * org.infinispan.CONTAINER: messages related to the data container (e.g. expiration, eviction, listeners, transactions, etc) > * org.infinispan.PERSISTENCE: messages related to loaders/stores > * org.infinispan.SECURITY: messages related to security > * org.infinispan.SERVER: messages related to server -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10695) Standardize the transport stack for the test suite

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10695?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10695: ----------------------------------- Fix Version/s: 10.0.0.Final (was: 10.0.0.CR2) > Standardize the transport stack for the test suite > -------------------------------------------------- > > Key: ISPN-10695 > URL: https://issues.jboss.org/browse/ISPN-10695 > Project: Infinispan > Issue Type: Bug > Reporter: Diego Lovison > Assignee: Diego Lovison > Priority: Critical > Fix For: 10.0.0.Final > > > By default the current stack is UDP but serverNG is using a different property name. > In this case, the QA will believe that all test suite is running under UDP when it is not. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues October 2019