June 2018 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-9331) Cluster node page flickers angular ctrl variables

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-9331?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-9331: -------------------------------------- Status: Open (was: New) > Cluster node page flickers angular ctrl variables > -------------------------------------------------- > > Key: ISPN-9331 > URL: https://issues.jboss.org/browse/ISPN-9331 > Project: Infinispan > Issue Type: Bug > Components: Console > Affects Versions: 9.3.0.Final > Reporter: Vladimir Blagojevic > Assignee: Vladimir Blagojevic > Fix For: 9.4.0.Alpha1 > > > For more details see https://youtu.be/TmPQu4VFx68 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9331) Cluster node page flickers angular ctrl variables

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-9331?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-9331: -------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan-management-console/pull/253 > Cluster node page flickers angular ctrl variables > -------------------------------------------------- > > Key: ISPN-9331 > URL: https://issues.jboss.org/browse/ISPN-9331 > Project: Infinispan > Issue Type: Bug > Components: Console > Affects Versions: 9.3.0.Final > Reporter: Vladimir Blagojevic > Assignee: Vladimir Blagojevic > Fix For: 9.4.0.Alpha1 > > > For more details see https://youtu.be/TmPQu4VFx68 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9327) Test failures in MemcachedFunctionalTest

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-9327?page=com.atlassian.jira.plugin.... ] Dan Berindei commented on ISPN-9327: ------------------------------------ The test is failing because both the test and the server assume the platform encoding is UTF-8. E.g. the server uses UTF-8 when reading the key, and the platform encoding when writing it back. On this machine the platform encoding is US-ASCII, and that breaks the test and the server. BTW, the reason for the {{MalformedInputException}} is the character {{®}}, encoded as as 2 characters ({{C2AE}}) out of the US-ASCII range ({{0..7F}}). > Test failures in MemcachedFunctionalTest > ---------------------------------------- > > Key: ISPN-9327 > URL: https://issues.jboss.org/browse/ISPN-9327 > Project: Infinispan > Issue Type: Bug > Reporter: Diego Lovison > Assignee: Dan Berindei > > From master the build is working but the tests are failing. > {noformat} > [ERROR] testBufferOverflowCausesUnknownException(org.infinispan.server.memcached.MemcachedFunctionalTest) Time elapsed: 0.008 s <<< FAILURE! > java.nio.charset.MalformedInputException: Input length = 1 > at java.nio.charset.CoderResult.throwException(CoderResult.java:281) > at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:339) > at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:178) > at java.io.InputStreamReader.read(InputStreamReader.java:184) > at java.io.BufferedReader.fill(BufferedReader.java:161) > at java.io.BufferedReader.readLine(BufferedReader.java:324) > at java.io.BufferedReader.readLine(BufferedReader.java:389) > at java.nio.file.Files.readAllLines(Files.java:3205) > at org.infinispan.server.memcached.MemcachedFunctionalTest.testBufferOverflowCausesUnknownException(MemcachedFunctionalTest.java:607) > [ERROR] testSetWithUTF8Key(org.infinispan.server.memcached.MemcachedFunctionalTest) Time elapsed: 60.013 s <<< FAILURE! > net.spy.memcached.OperationTimeoutException: Timeout waiting for value: waited 60,000 ms. Node status: Connection Status { /127.0.0.1:16311 active: true, authed: true, last read: 60,004 ms ago } > at net.spy.memcached.MemcachedClient.get(MemcachedClient.java:1240) > at net.spy.memcached.MemcachedClient.get(MemcachedClient.java:1256) > at org.infinispan.server.memcached.MemcachedFunctionalTest.testSetWithUTF8Key(MemcachedFunctionalTest.java:89) > Caused by: net.spy.memcached.internal.CheckedOperationTimeoutException: Timed out waiting for operation - failing node: /127.0.0.1:16311 > at net.spy.memcached.internal.OperationFuture.get(OperationFuture.java:167) > at net.spy.memcached.internal.GetFuture.get(GetFuture.java:69) > at net.spy.memcached.MemcachedClient.get(MemcachedClient.java:1229) > ... 25 more > [ERROR] testVersion(org.infinispan.server.memcached.MemcachedFunctionalTest) Time elapsed: 60.008 s <<< FAILURE! > java.lang.AssertionError: expected:<0> but was:<1> > at org.testng.AssertJUnit.fail(AssertJUnit.java:59) > at org.testng.AssertJUnit.failNotEquals(AssertJUnit.java:364) > at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:80) > at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:245) > at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:252) > at org.infinispan.server.memcached.MemcachedFunctionalTest.testVersion(MemcachedFunctionalTest.java:470) > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9327) Test failures in MemcachedFunctionalTest

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-9327?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-9327: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/6102 > Test failures in MemcachedFunctionalTest > ---------------------------------------- > > Key: ISPN-9327 > URL: https://issues.jboss.org/browse/ISPN-9327 > Project: Infinispan > Issue Type: Bug > Reporter: Diego Lovison > Assignee: Dan Berindei > > From master the build is working but the tests are failing. > {noformat} > [ERROR] testBufferOverflowCausesUnknownException(org.infinispan.server.memcached.MemcachedFunctionalTest) Time elapsed: 0.008 s <<< FAILURE! > java.nio.charset.MalformedInputException: Input length = 1 > at java.nio.charset.CoderResult.throwException(CoderResult.java:281) > at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:339) > at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:178) > at java.io.InputStreamReader.read(InputStreamReader.java:184) > at java.io.BufferedReader.fill(BufferedReader.java:161) > at java.io.BufferedReader.readLine(BufferedReader.java:324) > at java.io.BufferedReader.readLine(BufferedReader.java:389) > at java.nio.file.Files.readAllLines(Files.java:3205) > at org.infinispan.server.memcached.MemcachedFunctionalTest.testBufferOverflowCausesUnknownException(MemcachedFunctionalTest.java:607) > [ERROR] testSetWithUTF8Key(org.infinispan.server.memcached.MemcachedFunctionalTest) Time elapsed: 60.013 s <<< FAILURE! > net.spy.memcached.OperationTimeoutException: Timeout waiting for value: waited 60,000 ms. Node status: Connection Status { /127.0.0.1:16311 active: true, authed: true, last read: 60,004 ms ago } > at net.spy.memcached.MemcachedClient.get(MemcachedClient.java:1240) > at net.spy.memcached.MemcachedClient.get(MemcachedClient.java:1256) > at org.infinispan.server.memcached.MemcachedFunctionalTest.testSetWithUTF8Key(MemcachedFunctionalTest.java:89) > Caused by: net.spy.memcached.internal.CheckedOperationTimeoutException: Timed out waiting for operation - failing node: /127.0.0.1:16311 > at net.spy.memcached.internal.OperationFuture.get(OperationFuture.java:167) > at net.spy.memcached.internal.GetFuture.get(GetFuture.java:69) > at net.spy.memcached.MemcachedClient.get(MemcachedClient.java:1229) > ... 25 more > [ERROR] testVersion(org.infinispan.server.memcached.MemcachedFunctionalTest) Time elapsed: 60.008 s <<< FAILURE! > java.lang.AssertionError: expected:<0> but was:<1> > at org.testng.AssertJUnit.fail(AssertJUnit.java:59) > at org.testng.AssertJUnit.failNotEquals(AssertJUnit.java:364) > at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:80) > at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:245) > at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:252) > at org.infinispan.server.memcached.MemcachedFunctionalTest.testVersion(MemcachedFunctionalTest.java:470) > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9331) Cluster node page flickers angular ctrl variables

by Vladimir Blagojevic (JIRA)

Vladimir Blagojevic created ISPN-9331: ----------------------------------------- Summary: Cluster node page flickers angular ctrl variables Key: ISPN-9331 URL: https://issues.jboss.org/browse/ISPN-9331 Project: Infinispan Issue Type: Bug Components: Console Affects Versions: 9.3.0.Final Reporter: Vladimir Blagojevic Assignee: Vladimir Blagojevic Fix For: 9.4.0.Alpha1 For more details see https://youtu.be/TmPQu4VFx68 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9256) Upgrade npm dependencies

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-9256?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-9256: -------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan-management-console/pull/252 > Upgrade npm dependencies > ------------------------ > > Key: ISPN-9256 > URL: https://issues.jboss.org/browse/ISPN-9256 > Project: Infinispan > Issue Type: Task > Components: Console > Affects Versions: 9.3.0.CR1 > Reporter: Vladimir Blagojevic > Assignee: Vladimir Blagojevic > > Our project dependencies are getting very much out of date. We have not updated them since we started the project. Recently, we had an issue where a minor npm component upgrade in npm repo that our project uses caused an issue that took us hours to track down. After we upgrade all components, remove ever-increasing warnings, these issues should not happen anymore and we should have a much more resilient dependency tree. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9256) Upgrade npm dependencies

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-9256?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-9256: -------------------------------------- Status: Open (was: New) > Upgrade npm dependencies > ------------------------ > > Key: ISPN-9256 > URL: https://issues.jboss.org/browse/ISPN-9256 > Project: Infinispan > Issue Type: Task > Components: Console > Affects Versions: 9.3.0.CR1 > Reporter: Vladimir Blagojevic > Assignee: Vladimir Blagojevic > > Our project dependencies are getting very much out of date. We have not updated them since we started the project. Recently, we had an issue where a minor npm component upgrade in npm repo that our project uses caused an issue that took us hours to track down. After we upgrade all components, remove ever-increasing warnings, these issues should not happen anymore and we should have a much more resilient dependency tree. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3460) Refactor the CacheEntry hierarchy

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3460?page=com.atlassian.jira.plugin.... ] Dan Berindei commented on ISPN-3460: ------------------------------------ I would also like to create a separate interface for context entries, one that is not implemented by entries in the data container. It would require an extra instance to wrap the internal entry into the context, but I think we can avoid that for non-tx/implicit tx reads if we replace the repl read optimization we have now with a new "interceptor" chain that handles reads without a context (each interceptor would take in a key+flags and return an entry). > Refactor the CacheEntry hierarchy > --------------------------------- > > Key: ISPN-3460 > URL: https://issues.jboss.org/browse/ISPN-3460 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Reporter: Mircea Markus > Assignee: William Burns > Priority: Minor > > ATM we keep the metadata information in 3 places: CacheValues, CacheEntries and Metadata. We should move everything in the Metadata and make the CacheValues and the CacheEntries reference it. > Also look at MimeMetadataHelper in REST cache store... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3460) Refactor the CacheEntry hierarchy

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3460?page=com.atlassian.jira.plugin.... ] Dan Berindei commented on ISPN-3460: ------------------------------------ I'm not convinced we should have a {{Metadata}} instance every time. Personally I'd rather remove the custom metadata option, e.g. {{cache.put(key, value, new CustomMetadata()}}, and fit everything in the {{CacheEntry}} :) > Refactor the CacheEntry hierarchy > --------------------------------- > > Key: ISPN-3460 > URL: https://issues.jboss.org/browse/ISPN-3460 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Reporter: Mircea Markus > Assignee: William Burns > Priority: Minor > > ATM we keep the metadata information in 3 places: CacheValues, CacheEntries and Metadata. We should move everything in the Metadata and make the CacheValues and the CacheEntries reference it. > Also look at MimeMetadataHelper in REST cache store... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9330) Rewrite Embedded/Remote Compatibility documentation section

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-9330?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-9330: ------------------------------------ Description: The section is outdated and compat mode should not be recommended to users. Accessing data from multiple endpoints is possible without having to resort to store data as java objects. was: The section is outdated and compat mode should not be recommended to users. Accessing data from multiple endpoints is possible without having to resort to store data as java objects > Rewrite Embedded/Remote Compatibility documentation section > ----------------------------------------------------------- > > Key: ISPN-9330 > URL: https://issues.jboss.org/browse/ISPN-9330 > Project: Infinispan > Issue Type: Enhancement > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > > The section is outdated and compat mode should not be recommended to users. > Accessing data from multiple endpoints is possible without having to resort to store data as java objects. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues June 2018