February 2021 - infinispan-issues

[Red Hat JIRA] (ISPN-12682) dependency-check-maven plugin fails CI builds

by Dan Berindei (Jira)

[ https://issues.redhat.com/browse/ISPN-12682?page=com.atlassian.jira.plugi... ] Dan Berindei updated ISPN-12682: -------------------------------- Status: Open (was: New) > dependency-check-maven plugin fails CI builds > --------------------------------------------- > > Key: ISPN-12682 > URL: https://issues.redhat.com/browse/ISPN-12682 > Project: Infinispan > Issue Type: Bug > Components: Build > Affects Versions: 12.0.0.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 12.1.0.Final > > > CI builds for master are randomly failing because of the OWASP {{dependency-check-maven}} plugin: > {noformat} > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.owasp:dependency-check-maven:6.0.2:check (default-cli) on project infinispan-cachestore-jdbc: One or more exceptions occurred during dependency-check analysis > Caused by: org.owasp.dependencycheck.exception.ExceptionCollection: One or more exceptions occurred during analysis: > Failed to request component-reports > at org.owasp.dependencycheck.Engine.analyzeDependencies (Engine.java:644) > at org.owasp.dependencycheck.maven.BaseDependencyCheckMojo.runCheck (BaseDependencyCheckMojo.java:1606) > at org.owasp.dependencycheck.maven.BaseDependencyCheckMojo.execute (BaseDependencyCheckMojo.java:883) > at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137) > {noformat} > I was not able to reproduce the failure locally, and the OWASP dependency check plugin does not log the actual errors. It uses a custom {{ExceptionCollection}} class to wrap multiple exceptions, instead of {{Throwable.addSuppressed()}} method added in Java 1.7, and the Maven logger bypasses {{ExceptionCollection.printStackTrace()}}. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 4 months

1
0
0 / 0

[Red Hat JIRA] (ISPN-12683) Add authz to Counters

by Katia Aresti (Jira)

Katia Aresti created ISPN-12683: ----------------------------------- Summary: Add authz to Counters Key: ISPN-12683 URL: https://issues.redhat.com/browse/ISPN-12683 Project: Infinispan Issue Type: Feature Request Components: Clustered Counter Affects Versions: 12.0.0.Final Reporter: Katia Aresti Assignee: Pedro Ruivo Unlike tasks, schemas or caches, counters are not protected by any authorisation mechanisms. Design and implementation needed -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 4 months

1
0
0 / 0

[Red Hat JIRA] (ISPN-12682) dependency-check-maven plugin fails CI builds

by Dan Berindei (Jira)

Dan Berindei created ISPN-12682: ----------------------------------- Summary: dependency-check-maven plugin fails CI builds Key: ISPN-12682 URL: https://issues.redhat.com/browse/ISPN-12682 Project: Infinispan Issue Type: Bug Components: Build Affects Versions: 12.0.0.Final Reporter: Dan Berindei Assignee: Dan Berindei Fix For: 12.1.0.Final CI builds for master are randomly failing because of the OWASP {{dependency-check-maven}} plugin: {noformat} org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.owasp:dependency-check-maven:6.0.2:check (default-cli) on project infinispan-cachestore-jdbc: One or more exceptions occurred during dependency-check analysis Caused by: org.owasp.dependencycheck.exception.ExceptionCollection: One or more exceptions occurred during analysis: Failed to request component-reports at org.owasp.dependencycheck.Engine.analyzeDependencies (Engine.java:644) at org.owasp.dependencycheck.maven.BaseDependencyCheckMojo.runCheck (BaseDependencyCheckMojo.java:1606) at org.owasp.dependencycheck.maven.BaseDependencyCheckMojo.execute (BaseDependencyCheckMojo.java:883) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137) {noformat} I was not able to reproduce the failure locally, and the OWASP dependency check plugin does not log the actual errors. It uses a custom {{ExceptionCollection}} class to wrap multiple exceptions, instead of {{Throwable.addSuppressed()}} method added in Java 1.7, and the Maven logger bypasses {{ExceptionCollection.printStackTrace()}}. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 4 months

1
0
0 / 0

[Red Hat JIRA] (ISPN-12657) Cross-Site automatic state transfer

by Pedro Ruivo (Jira)

[ https://issues.redhat.com/browse/ISPN-12657?page=com.atlassian.jira.plugi... ] Pedro Ruivo updated ISPN-12657: ------------------------------- Status: Open (was: New) > Cross-Site automatic state transfer > ----------------------------------- > > Key: ISPN-12657 > URL: https://issues.redhat.com/browse/ISPN-12657 > Project: Infinispan > Issue Type: Feature Request > Components: Cross-Site Replication > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Priority: Major > Fix For: 12.1.0.Final > > > With conflict resolution enable for IRAC state transfer, is now possible to achieve automatic state transfer for it. > It needs a new toggle in the configuration & a runtime toggle well. Users may want to disable at runtime while performing some maintenance (for example). > Events from JGroups (site up event) will be the trigger. > Note: it only affects asynchronous strategy. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 4 months

1
0
0 / 0

[Red Hat JIRA] (ISPN-12657) Cross-Site automatic state transfer

by Pedro Ruivo (Jira)

[ https://issues.redhat.com/browse/ISPN-12657?page=com.atlassian.jira.plugi... ] Work on ISPN-12657 started by Pedro Ruivo. ------------------------------------------ > Cross-Site automatic state transfer > ----------------------------------- > > Key: ISPN-12657 > URL: https://issues.redhat.com/browse/ISPN-12657 > Project: Infinispan > Issue Type: Feature Request > Components: Cross-Site Replication > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Priority: Major > Fix For: 12.1.0.Final > > > With conflict resolution enable for IRAC state transfer, is now possible to achieve automatic state transfer for it. > It needs a new toggle in the configuration & a runtime toggle well. Users may want to disable at runtime while performing some maintenance (for example). > Events from JGroups (site up event) will be the trigger. > Note: it only affects asynchronous strategy. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 4 months

1
0
0 / 0

[Red Hat JIRA] (IPROTO-181) WrappedMessage.wrappedInstantNanos cannot be part of the scalarOrMessage oneof

by Nistor Adrian (Jira)

[ https://issues.redhat.com/browse/IPROTO-181?page=com.atlassian.jira.plugi... ] Nistor Adrian updated IPROTO-181: --------------------------------- Sprint: DataGrid Sprint #56 > WrappedMessage.wrappedInstantNanos cannot be part of the scalarOrMessage oneof > ------------------------------------------------------------------------------ > > Key: IPROTO-181 > URL: https://issues.redhat.com/browse/IPROTO-181 > Project: Infinispan ProtoStream > Issue Type: Bug > Affects Versions: 4.2.2.Final, 4.3.0.Alpha1 > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 4.4.0.Final > > > Fields {color:#000000}wrappedInstantSeconds and {color}{color:#000000}wrappedInstantNanos {color}should be used together but it is illegal since it's a oneof. This definition is wrong and the error was not spotted in time because WrappedMessage is entirely handcoded. > To fix this, one of the fields must become an optional field outside the oneof and keep the same field number to ensure compatibility. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 4 months

1
0
0 / 0

[Red Hat JIRA] (IPROTO-181) WrappedMessage.wrappedInstantNanos cannot be part of the scalarOrMessage oneof

by Nistor Adrian (Jira)

[ https://issues.redhat.com/browse/IPROTO-181?page=com.atlassian.jira.plugi... ] Work on IPROTO-181 started by Nistor Adrian. -------------------------------------------- > WrappedMessage.wrappedInstantNanos cannot be part of the scalarOrMessage oneof > ------------------------------------------------------------------------------ > > Key: IPROTO-181 > URL: https://issues.redhat.com/browse/IPROTO-181 > Project: Infinispan ProtoStream > Issue Type: Bug > Affects Versions: 4.2.2.Final, 4.3.0.Alpha1 > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 4.4.0.Final > > > Fields {color:#000000}wrappedInstantSeconds and {color}{color:#000000}wrappedInstantNanos {color}should be used together but it is illegal since it's a oneof. This definition is wrong and the error was not spotted in time because WrappedMessage is entirely handcoded. > To fix this, one of the fields must become an optional field outside the oneof and keep the same field number to ensure compatibility. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 4 months

1
0
0 / 0

[Red Hat JIRA] (IPROTO-181) WrappedMessage.wrappedInstantNanos cannot be part of the scalarOrMessage oneof

by Nistor Adrian (Jira)

[ https://issues.redhat.com/browse/IPROTO-181?page=com.atlassian.jira.plugi... ] Nistor Adrian updated IPROTO-181: --------------------------------- Affects Version/s: 4.3.0.Alpha1 4.2.2.Final > WrappedMessage.wrappedInstantNanos cannot be part of the scalarOrMessage oneof > ------------------------------------------------------------------------------ > > Key: IPROTO-181 > URL: https://issues.redhat.com/browse/IPROTO-181 > Project: Infinispan ProtoStream > Issue Type: Bug > Affects Versions: 4.2.2.Final, 4.3.0.Alpha1 > Reporter: Nistor Adrian > Priority: Major > Fix For: 4.4.0.Final > > > Fields {color:#000000}wrappedInstantSeconds and {color}{color:#000000}wrappedInstantNanos {color}should be used together but it is illegal since it's a oneof. This definition is wrong and the error was not spotted in time because WrappedMessage is entirely handcoded. > To fix this, one of the fields must become an optional field outside the oneof and keep the same field number to ensure compatibility. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 4 months

1
0
0 / 0

[Red Hat JIRA] (IPROTO-181) WrappedMessage.wrappedInstantNanos cannot be part of the scalarOrMessage oneof

by Nistor Adrian (Jira)

[ https://issues.redhat.com/browse/IPROTO-181?page=com.atlassian.jira.plugi... ] Nistor Adrian updated IPROTO-181: --------------------------------- Fix Version/s: 4.4.0.Final > WrappedMessage.wrappedInstantNanos cannot be part of the scalarOrMessage oneof > ------------------------------------------------------------------------------ > > Key: IPROTO-181 > URL: https://issues.redhat.com/browse/IPROTO-181 > Project: Infinispan ProtoStream > Issue Type: Bug > Reporter: Nistor Adrian > Priority: Major > Fix For: 4.4.0.Final > > > Fields {color:#000000}wrappedInstantSeconds and {color}{color:#000000}wrappedInstantNanos {color}should be used together but it is illegal since it's a oneof. This definition is wrong and the error was not spotted in time because WrappedMessage is entirely handcoded. > To fix this, one of the fields must become an optional field outside the oneof and keep the same field number to ensure compatibility. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 4 months

1
0
0 / 0

[Red Hat JIRA] (IPROTO-181) WrappedMessage.wrappedInstantNanos cannot be part of the scalarOrMessage oneof

by Nistor Adrian (Jira)

[ https://issues.redhat.com/browse/IPROTO-181?page=com.atlassian.jira.plugi... ] Nistor Adrian updated IPROTO-181: --------------------------------- Status: Open (was: New) > WrappedMessage.wrappedInstantNanos cannot be part of the scalarOrMessage oneof > ------------------------------------------------------------------------------ > > Key: IPROTO-181 > URL: https://issues.redhat.com/browse/IPROTO-181 > Project: Infinispan ProtoStream > Issue Type: Bug > Reporter: Nistor Adrian > Priority: Major > > Fields {color:#000000}wrappedInstantSeconds and {color}{color:#000000}wrappedInstantNanos {color}should be used together but it is illegal since it's a oneof. This definition is wrong and the error was not spotted in time because WrappedMessage is entirely handcoded. > To fix this, one of the fields must become an optional field outside the oneof and keep the same field number to ensure compatibility. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 4 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 February 2021