June 2019 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (IPROTO-51) ProtoSchemaBuilder fails on required property of type bytes

by Nistor Adrian (Jira)

[ https://issues.jboss.org/browse/IPROTO-51?page=com.atlassian.jira.plugin.... ] Nistor Adrian updated IPROTO-51: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done Fixed in 4.3.0.Alpha7 > ProtoSchemaBuilder fails on required property of type bytes > ----------------------------------------------------------- > > Key: IPROTO-51 > URL: https://issues.jboss.org/browse/IPROTO-51 > Project: Infinispan ProtoStream > Issue Type: Bug > Affects Versions: 3.0.5.Final > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 4.3.0.Alpha7, 4.3.0.Final > > > {code} > @ProtoField(number = 10, required = true) > public byte[] getName() { > return name; > } > {code} > reults in > Failure: org.infinispan.protostream.annotations.ProtoSchemaBuilderException: Repeated field 'name' of class app.model.Train cannot be marked required. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8756) Implement Single Port

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-8756?page=com.atlassian.jira.plugin.... ] Tristan Tarrant reassigned ISPN-8756: ------------------------------------- Assignee: Tristan Tarrant > Implement Single Port > --------------------- > > Key: ISPN-8756 > URL: https://issues.jboss.org/browse/ISPN-8756 > Project: Infinispan > Issue Type: Feature Request > Components: Remote Protocols > Reporter: Sebastian Laskawiec > Assignee: Tristan Tarrant > Priority: Major > > Design document: https://github.com/infinispan/infinispan-designs/blob/master/Single_port.... -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10106) Fix thread leaks in JUnit modules

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10106?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10106: ----------------------------------- Status: Pull Request Sent (was: Reopened) > Fix thread leaks in JUnit modules > --------------------------------- > > Key: ISPN-10106 > URL: https://issues.jboss.org/browse/ISPN-10106 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Server > Affects Versions: 9.4.11.Final, 10.0.0.Beta3 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Labels: testsuite_stability > Fix For: 10.0.0.Beta4, 9.4.13.Final > > > ISPN-9863 added a thread leak checker, but even with all the recent improvements, leaks in JUnit modules are not reported as test failures. > Because Surefire ignores failures in JUnit configuration methods and listeners, the only sign of a leak is an error message in the console output: > {noformat} > [2019-03-28T17:33:54.119Z] org.apache.maven.surefire.booter.SurefireBooterForkException: ExecutionException There was an error in the forked process > [2019-03-28T17:33:54.119Z] Test mechanism :: Leaked threads: > [2019-03-28T17:33:54.119Z] {pool-7-thread-1: possible sources [UNKNOWN]}, > [2019-03-28T17:33:54.119Z] {management-client-thread 1-1: possible sources [UNKNOWN]} > {noformat} > And in a dump file: > {noformat} > [2019-03-28T18:23:39.501Z] ./integrationtests/security-it/target/failsafe-reports/2019-03-28T17-28-10_213-jvmRun1.dump > [2019-03-28T18:23:39.501Z] # Created at 2019-03-28T17:29:25.623 > [2019-03-28T18:23:39.501Z] org.apache.maven.surefire.testset.TestSetFailedException: Test mechanism :: Leaked threads: > [2019-03-28T18:23:39.501Z] {pool-7-thread-1: possible sources [UNKNOWN]}, > [2019-03-28T18:23:39.501Z] {management-client-thread 1-1: possible sources [UNKNOWN]} > [2019-03-28T18:23:39.501Z] at org.apache.maven.surefire.common.junit4.JUnit4RunListener.rethrowAnyTestMechanismFailures(JUnit4RunListener.java:223) > {noformat} -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10106) Fix thread leaks in JUnit modules

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10106?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10106: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Fix thread leaks in JUnit modules > --------------------------------- > > Key: ISPN-10106 > URL: https://issues.jboss.org/browse/ISPN-10106 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Server > Affects Versions: 9.4.11.Final, 10.0.0.Beta3 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Labels: testsuite_stability > Fix For: 10.0.0.Beta4, 9.4.13.Final > > > ISPN-9863 added a thread leak checker, but even with all the recent improvements, leaks in JUnit modules are not reported as test failures. > Because Surefire ignores failures in JUnit configuration methods and listeners, the only sign of a leak is an error message in the console output: > {noformat} > [2019-03-28T17:33:54.119Z] org.apache.maven.surefire.booter.SurefireBooterForkException: ExecutionException There was an error in the forked process > [2019-03-28T17:33:54.119Z] Test mechanism :: Leaked threads: > [2019-03-28T17:33:54.119Z] {pool-7-thread-1: possible sources [UNKNOWN]}, > [2019-03-28T17:33:54.119Z] {management-client-thread 1-1: possible sources [UNKNOWN]} > {noformat} > And in a dump file: > {noformat} > [2019-03-28T18:23:39.501Z] ./integrationtests/security-it/target/failsafe-reports/2019-03-28T17-28-10_213-jvmRun1.dump > [2019-03-28T18:23:39.501Z] # Created at 2019-03-28T17:29:25.623 > [2019-03-28T18:23:39.501Z] org.apache.maven.surefire.testset.TestSetFailedException: Test mechanism :: Leaked threads: > [2019-03-28T18:23:39.501Z] {pool-7-thread-1: possible sources [UNKNOWN]}, > [2019-03-28T18:23:39.501Z] {management-client-thread 1-1: possible sources [UNKNOWN]} > [2019-03-28T18:23:39.501Z] at org.apache.maven.surefire.common.junit4.JUnit4RunListener.rethrowAnyTestMechanismFailures(JUnit4RunListener.java:223) > {noformat} -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9715) Update internal embedded listeners to be non blocking

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9715?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9715: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Update internal embedded listeners to be non blocking > ----------------------------------------------------- > > Key: ISPN-9715 > URL: https://issues.jboss.org/browse/ISPN-9715 > Project: Infinispan > Issue Type: Sub-task > Components: Core, Listeners > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > Fix For: 10.0.0.Beta4 > > > With ISPN-9714 it will be possible to have a listener perform non blocking operations. Also any listener that doesn't return a CompletionStage is invoked in a different thread. We should convert all of our internal listeners to return a CompletionStage if they can, so that we don't have to incur the cost of switching threads to execute them. > We need to ensure that all embedded listeners return a CompletionStage and never block the current thread. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-80) Default value for bytes field is not working

by Nistor Adrian (Jira)

[ https://issues.jboss.org/browse/IPROTO-80?page=com.atlassian.jira.plugin.... ] Nistor Adrian updated IPROTO-80: -------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/protostream/pull/67 > Default value for bytes field is not working > -------------------------------------------- > > Key: IPROTO-80 > URL: https://issues.jboss.org/browse/IPROTO-80 > Project: Infinispan ProtoStream > Issue Type: Bug > Affects Versions: 4.2.0.Final > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 4.3.0.Alpha7, 4.3.0.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-80) Default value for bytes field is not working

by Nistor Adrian (Jira)

[ https://issues.jboss.org/browse/IPROTO-80?page=com.atlassian.jira.plugin.... ] Nistor Adrian updated IPROTO-80: -------------------------------- Fix Version/s: 4.3.0.Alpha7 4.3.0.Final > Default value for bytes field is not working > -------------------------------------------- > > Key: IPROTO-80 > URL: https://issues.jboss.org/browse/IPROTO-80 > Project: Infinispan ProtoStream > Issue Type: Bug > Affects Versions: 4.2.0.Final > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 4.3.0.Alpha7, 4.3.0.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-95) Add range checks for default value of numeric fields in protobuf schema

by Nistor Adrian (Jira)

[ https://issues.jboss.org/browse/IPROTO-95?page=com.atlassian.jira.plugin.... ] Nistor Adrian updated IPROTO-95: -------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/protostream/pull/67 > Add range checks for default value of numeric fields in protobuf schema > ----------------------------------------------------------------------- > > Key: IPROTO-95 > URL: https://issues.jboss.org/browse/IPROTO-95 > Project: Infinispan ProtoStream > Issue Type: Bug > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 4.3.0.Alpha7, 4.3.0.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-51) ProtoSchemaBuilder fails on required property of type bytes

by Nistor Adrian (Jira)

[ https://issues.jboss.org/browse/IPROTO-51?page=com.atlassian.jira.plugin.... ] Nistor Adrian updated IPROTO-51: -------------------------------- Fix Version/s: 4.3.0.Alpha7 (was: 4.2.0.Alpha4) (was: 4.1.5.Final) > ProtoSchemaBuilder fails on required property of type bytes > ----------------------------------------------------------- > > Key: IPROTO-51 > URL: https://issues.jboss.org/browse/IPROTO-51 > Project: Infinispan ProtoStream > Issue Type: Bug > Affects Versions: 3.0.5.Final > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 4.3.0.Alpha7, 4.3.0.Final > > > {code} > @ProtoField(number = 10, required = true) > public byte[] getName() { > return name; > } > {code} > reults in > Failure: org.infinispan.protostream.annotations.ProtoSchemaBuilderException: Repeated field 'name' of class app.model.Train cannot be marked required. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-51) ProtoSchemaBuilder fails on required property of type bytes

by Nistor Adrian (Jira)

[ https://issues.jboss.org/browse/IPROTO-51?page=com.atlassian.jira.plugin.... ] Nistor Adrian updated IPROTO-51: -------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/protostream/pull/67 > ProtoSchemaBuilder fails on required property of type bytes > ----------------------------------------------------------- > > Key: IPROTO-51 > URL: https://issues.jboss.org/browse/IPROTO-51 > Project: Infinispan ProtoStream > Issue Type: Bug > Affects Versions: 3.0.5.Final > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 4.1.5.Final, 4.2.0.Alpha4, 4.3.0.Final > > > {code} > @ProtoField(number = 10, required = true) > public byte[] getName() { > return name; > } > {code} > reults in > Failure: org.infinispan.protostream.annotations.ProtoSchemaBuilderException: Repeated field 'name' of class app.model.Train cannot be marked required. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues June 2019