July 2019 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-10390) Docs: Remove Non-working Examples from Getting Started

by Donald Naro (Jira)

Donald Naro created ISPN-10390: ---------------------------------- Summary: Docs: Remove Non-working Examples from Getting Started Key: ISPN-10390 URL: https://issues.jboss.org/browse/ISPN-10390 Project: Infinispan Issue Type: Enhancement Components: Documentation-Core Affects Versions: 10.0.0.Beta3 Reporter: Donald Naro Assignee: Donald Naro https://infinispan.org/docs/10.0.x/getting_started/getting_started.html#s... uses uberjars https://infinispan.org/docs/10.0.x/getting_started/getting_started.html#s... references a missing infinispantest.groovy -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10223) As a developer, I need docs for using Maven, Gradle, and Ivy

by Donald Naro (Jira)

[ https://issues.jboss.org/browse/ISPN-10223?page=com.atlassian.jira.plugin... ] Donald Naro commented on ISPN-10223: ------------------------------------ [~NadirX] I think the way to do it is extract all the maven dependency examples to separate files. When we have that we can convert them in batches to ivy and gradle. I've also explored the use of rendering the examples in tabbed format on the upstream site. That might be more of a stretch, especially given the product docs won't play nicely. But I think we can get there over time. If you were thinking of another approach to this, let me know. Cheers. > As a developer, I need docs for using Maven, Gradle, and Ivy > ------------------------------------------------------------ > > Key: ISPN-10223 > URL: https://issues.jboss.org/browse/ISPN-10223 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation-Core > Affects Versions: 10.0.0.Final > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > > Provide instructions for managing dependencies with maven, gradle, and ivy. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10389) Refactor the test HTTP client

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10389?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10389: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/7123 > Refactor the test HTTP client > ----------------------------- > > Key: ISPN-10389 > URL: https://issues.jboss.org/browse/ISPN-10389 > Project: Infinispan > Issue Type: Enhancement > Components: Remote Protocols, REST, Test Suite - Server > Affects Versions: 10.0.0.Beta3 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.0.0.Beta4 > > > The REST server testsuite includes an HTTP client which could eventually be reused in many places (CLI, Rest Cache Store, Server testsuite). > Before promoting it to a public module (i.e. non-test) we can improve its usability by making it configurable, automatically selecting configuration modes, etc. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10389) Refactor the test HTTP client

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10389?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10389: ----------------------------------- Status: Open (was: New) > Refactor the test HTTP client > ----------------------------- > > Key: ISPN-10389 > URL: https://issues.jboss.org/browse/ISPN-10389 > Project: Infinispan > Issue Type: Enhancement > Components: Remote Protocols, REST, Test Suite - Server > Affects Versions: 10.0.0.Beta3 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.0.0.Beta4 > > > The REST server testsuite includes an HTTP client which could eventually be reused in many places (CLI, Rest Cache Store, Server testsuite). > Before promoting it to a public module (i.e. non-test) we can improve its usability by making it configurable, automatically selecting configuration modes, etc. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (HRJS-79) Registering listener with undefined listenerId does nothing

by Galder Zamarreño (Jira)

[ https://issues.jboss.org/browse/HRJS-79?page=com.atlassian.jira.plugin.sy... ] Galder Zamarreño updated HRJS-79: --------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 0.7.0 Resolution: Done > Registering listener with undefined listenerId does nothing > ----------------------------------------------------------- > > Key: HRJS-79 > URL: https://issues.jboss.org/browse/HRJS-79 > Project: Infinispan Javascript client > Issue Type: Bug > Reporter: Anna Manukyan > Assignee: Anna Manukyan > Priority: Major > Fix For: 0.7.0 > > > I was trying the following scenario: the case when the listenerId is passed while adding new listeners. > I was creating 3 listeners for create,modify and remove events. While adding listeners for modify and remove events I was passing the listenerId, but for modify event the listenerId was some nonexistent string. > I was curious what will happen. From the functional side nothing happened, so the modify event is not fired and from the logs I can see the following: > {code} > [2018-09-25T22:24:55.845] [DEBUG] client - Invoke addListener(msgId=464,event=create,listenerId=listener_465,opts=undefined) remotely > [2018-09-25T22:24:55.845] [TRACE] encoder - Encode operation with topology id 0 > [2018-09-25T22:24:55.846] [TRACE] listener - Create listener emitter for connection 127.0.0.1:11222@conn_15 and listener with listenerId=listener_465 > [2018-09-25T22:24:55.846] [TRACE] io_7 - Write buffer(msgId=464) to 127.0.0.1:11222@conn_15: A0D0031D2500000300010D00010D000C6C697374656E65725F343635000000000F > [2018-09-25T22:24:55.847] [TRACE] decoder - Read header(msgId=464): opCode=38, status=0, hasNewTopology=0 > [2018-09-25T22:24:55.847] [TRACE] decoder - Call decode for request(msgId=464) > [2018-09-25T22:24:55.847] [TRACE] io_7_conn_15 - Complete success for request(msgId=464) with true > [2018-09-25T22:24:55.847] [TRACE] io_7_conn_15 - After decoding request(msgId=464), buffer size is 6, and offset 6 > [2018-09-25T22:24:55.847] [DEBUG] client - Invoke addListener(msgId=466,event=modify,opts={"listenerId":"blblbl"}) locally > {color:red}[2018-09-25T22:24:55.848] [TRACE] listener - Create listener emitter for connection undefined and listener with listenerId=blblbl{color} > [2018-09-25T22:24:55.848] [DEBUG] client - Invoke addListener(msgId=467,event=remove,opts={"listenerId":"listener_465"}) locally > {code} > So the first line creates "create" event listener remotely. For the "modify" and "delete" events the "addLocalListener()" function is called. I am worried about the line marked in red, there the connection is passed as {color:red}undefined{color}. > I have found out that the connection parameter is not passed to protocol's addListener function when it is called from addLocalListener() function, but couldn't find a way to fix that. > Should it be that way? > I know that this kind of scenario is hardly possible but just in case the developer did some mistake, perhaps he/she may spend much time on finding why the event is not fired. > The code for generating this log is given here: > {code} > ...code in the test... > it('fails when trying to attach to non-existent listener', function(done) { > client.then(function (client) { > var clientAddListenerCreate = client.addListener( > 'create', function(key) { console.log('[Event] Created key: ' + key); }); > var clientAddListeners = clientAddListenerCreate.then( > function(listenerId) { > // Multiple callbacks can be associated with a single client-side listener. > // This is achieved by registering listeners with the same listener id > // as shown in the example below. > var clientAddListenerModify = client.addListener( > 'modify', function(key) { console.log('[Event] Modified key: ' + key); }, > {listenerId: 'blblbl'}); > var clientAddListenerRemove = client.addListener( > 'remove', function(key) { console.log('[Event] Removed key: ' + key); }, > {listenerId: listenerId}); > return Promise.all([clientAddListenerModify, clientAddListenerRemove]); > }); > var clientCreate = clientAddListeners.then( > function() { return client.putIfAbsent('eventful', 'v0'); }); > var clientModify = clientCreate.then( > function() { return client.replace('eventful', 'v1'); }); > var clientRemove = clientModify.then( > function() { return client.remove('eventful'); }); > var clientRemoveListener = > Promise.all([clientAddListenerCreate, clientRemove]).then( > function(values) { > var listenerId = values[0]; > return client.removeListener(listenerId); > }); > }).catch(t.failed(done)).finally(done); > }); > ........ > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10389) Refactor the test HTTP client

by Tristan Tarrant (Jira)

Tristan Tarrant created ISPN-10389: -------------------------------------- Summary: Refactor the test HTTP client Key: ISPN-10389 URL: https://issues.jboss.org/browse/ISPN-10389 Project: Infinispan Issue Type: Enhancement Components: Remote Protocols, REST, Test Suite - Server Affects Versions: 10.0.0.Beta3 Reporter: Tristan Tarrant Assignee: Tristan Tarrant Fix For: 10.0.0.Beta4 The REST server testsuite includes an HTTP client which could eventually be reused in many places (CLI, Rest Cache Store, Server testsuite). Before promoting it to a public module (i.e. non-test) we can improve its usability by making it configurable, automatically selecting configuration modes, etc. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10384) Create dedicated maven-plugins repository

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-10384?page=com.atlassian.jira.plugin... ] Ryan Emerson updated ISPN-10384: -------------------------------- Git Pull Request: https://github.com/infinispan/maven-plugins/pull/1, https://github.com/infinispan/infinispan/pull/7122 (was: https://github.com/infinispan/maven-plugins/pull/1) > Create dedicated maven-plugins repository > ----------------------------------------- > > Key: ISPN-10384 > URL: https://issues.jboss.org/browse/ISPN-10384 > Project: Infinispan > Issue Type: Enhancement > Components: Build > Affects Versions: 10.0.0.Beta3 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.0.0.Beta4 > > > In the main ISPN repo we have a plugins dir that contains our custom maven plugins used throughout our builds. Currently this dir contains the infinispan-defaults-maven-plugin for extracting code defaults to xsd and the protocol-parser-generator-maven-plugin for generating the hotrod parser. > We should create a new repository under the infinispan org, e.g. github.com/infinispan/maven-plugins, to contain all of our maven plugins that do not depend on ISPN code. > The infinispan-defaults-maven-plugin can't be moved as it depends on infinispan-commons. > https://github.com/infinispan/maven-plugins -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10246) Add build step to check protobuf schema changes are backwards compatible

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-10246?page=com.atlassian.jira.plugin... ] Ryan Emerson updated ISPN-10246: -------------------------------- Status: Pull Request Sent (was: Coding In Progress) > Add build step to check protobuf schema changes are backwards compatible > ------------------------------------------------------------------------ > > Key: ISPN-10246 > URL: https://issues.jboss.org/browse/ISPN-10246 > Project: Infinispan > Issue Type: Sub-task > Components: Build > Affects Versions: 10.0.0.Beta3 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.0.0.Beta4 > > > We should fail builds if they introduce backwards incompatible changes to our generated .proto files in order to ensure that future ISPN versions can always read data serialized from this version onwards. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10246) Add build step to check protobuf schema changes are backwards compatible

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-10246?page=com.atlassian.jira.plugin... ] Work on ISPN-10246 started by Ryan Emerson. ------------------------------------------- > Add build step to check protobuf schema changes are backwards compatible > ------------------------------------------------------------------------ > > Key: ISPN-10246 > URL: https://issues.jboss.org/browse/ISPN-10246 > Project: Infinispan > Issue Type: Sub-task > Components: Build > Affects Versions: 10.0.0.Beta3 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.0.0.Beta4 > > > We should fail builds if they introduce backwards incompatible changes to our generated .proto files in order to ensure that future ISPN versions can always read data serialized from this version onwards. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9772) Cache v2 Resource

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-9772?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-9772: ------------------------------- Affects Version/s: 10.0.0.Beta3 > Cache v2 Resource > ----------------- > > Key: ISPN-9772 > URL: https://issues.jboss.org/browse/ISPN-9772 > Project: Infinispan > Issue Type: Sub-task > Affects Versions: 10.0.0.Beta3 > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Priority: Major > Fix For: 10.0.0.Beta4 > > > The new cache resource should include most of operations in the current v1 resource, plus: > * Possibility to create a cache passing a configuration > * Possibility to obtain the cache configuration > * Extra operations: > -* Stop cache (clustered or not) > -* Disable a cache temporarily > -* Obtain stats about the cache > -* Efficient cache entry iteration, with or without keys -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 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 July 2019