[JBoss JIRA] (ISPN-6124) List of caches is sometimes visually corrupt
by Jiří Holuša (JIRA)
[ https://issues.jboss.org/browse/ISPN-6124?page=com.atlassian.jira.plugin.... ]
Jiří Holuša commented on ISPN-6124:
-----------------------------------
[~vblagojevic] Hi Vladimir, I found the root cause of this issue. In the cluster-view/cluster-view.html, there is the div with ng-repeat directive to list the caches according to filters:
{code}
<div class="col-xs-6 col-sm-4 col-md-2" ng-repeat="cache in filtered = (currentCluster.getCachesAsArray() |
filter: {name: searchNameQuery} | cacheTrait:traitCheckboxes | cacheType:typeCheckboxes)" ng-show="cache.show" on-finish-render="matchHeight()">
{code}
The thing that makes all the boxes the same height is the matchHeight() function. The bug is that this method is not called after every change of the filters. It is called after the first load of the page. I also tried to click on the filters (cache types) and I don't know but I cannot find any deterministic reason when the method is called then. Sometimes it's called after clicking "Invalidation" with checked "Local", sometimes not, I don't know. The key thing in here is that the matchHeight() must be called after filter change and re-rendering the cache list.
Unfortunately my AngularJS knowledge ends here, I don't know how to solve it, but I think it will be fairly easy for you, you just need to find out the right place, where to put it :)
> List of caches is sometimes visually corrupt
> --------------------------------------------
>
> Key: ISPN-6124
> URL: https://issues.jboss.org/browse/ISPN-6124
> Project: Infinispan
> Issue Type: Bug
> Components: Console
> Affects Versions: 8.1.0.Final
> Reporter: Jiří Holuša
> Assignee: Jiří Holuša
> Attachments: Snímek z 2016-01-29 11-37-21.png
>
>
> Page: Cache -> select some container -> list of caches
> Under certain circumstances, the cache cards are wrongly aligned, see the screenshot in attachments. I think it's because those two caches on the right don't have any icons below the cache type, making the box smaller.
> The solution would be to assign fixed height, since it can be predictable or add a "clearing" div after each row, I guess.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (ISPN-6124) List of caches is sometimes visually corrupt
by Jiří Holuša (JIRA)
[ https://issues.jboss.org/browse/ISPN-6124?page=com.atlassian.jira.plugin.... ]
Jiří Holuša reassigned ISPN-6124:
---------------------------------
Assignee: Vladimir Blagojevic (was: Jiří Holuša)
> List of caches is sometimes visually corrupt
> --------------------------------------------
>
> Key: ISPN-6124
> URL: https://issues.jboss.org/browse/ISPN-6124
> Project: Infinispan
> Issue Type: Bug
> Components: Console
> Affects Versions: 8.1.0.Final
> Reporter: Jiří Holuša
> Assignee: Vladimir Blagojevic
> Attachments: Snímek z 2016-01-29 11-37-21.png
>
>
> Page: Cache -> select some container -> list of caches
> Under certain circumstances, the cache cards are wrongly aligned, see the screenshot in attachments. I think it's because those two caches on the right don't have any icons below the cache type, making the box smaller.
> The solution would be to assign fixed height, since it can be predictable or add a "clearing" div after each row, I guess.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (ISPN-5753) SIFS can reincarnate deleted entries during startup
by Radim Vansa (JIRA)
[ https://issues.jboss.org/browse/ISPN-5753?page=com.atlassian.jira.plugin.... ]
Radim Vansa commented on ISPN-5753:
-----------------------------------
Yes, it doesn't rely on any change in 8.x.
> SIFS can reincarnate deleted entries during startup
> ---------------------------------------------------
>
> Key: ISPN-5753
> URL: https://issues.jboss.org/browse/ISPN-5753
> Project: Infinispan
> Issue Type: Bug
> Components: Loaders and Stores
> Affects Versions: 8.0.1.Final, 7.2.5.Final
> Reporter: Radim Vansa
> Assignee: Radim Vansa
> Fix For: 9.0.0.Alpha2, 8.2.2.Final, 9.0.0.Final
>
>
> Since we don't keep deleted entries in index, we can't see that an entry was deleted (don't know it's last seqId) if files are read in unlucky order. Then we could add the entry into the index even though it was deleted.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (ISPN-5753) SIFS can reincarnate deleted entries during startup
by Andreas Pabst (JIRA)
[ https://issues.jboss.org/browse/ISPN-5753?page=com.atlassian.jira.plugin.... ]
Andreas Pabst commented on ISPN-5753:
-------------------------------------
If we pick the changes you made to the SIFS from the 8.2.x branch this will be safe? It compiles fine at least. None of your changes rely on other changes that are not present in 7.2.x branch?
> SIFS can reincarnate deleted entries during startup
> ---------------------------------------------------
>
> Key: ISPN-5753
> URL: https://issues.jboss.org/browse/ISPN-5753
> Project: Infinispan
> Issue Type: Bug
> Components: Loaders and Stores
> Affects Versions: 8.0.1.Final, 7.2.5.Final
> Reporter: Radim Vansa
> Assignee: Radim Vansa
> Fix For: 9.0.0.Alpha2, 8.2.2.Final, 9.0.0.Final
>
>
> Since we don't keep deleted entries in index, we can't see that an entry was deleted (don't know it's last seqId) if files are read in unlucky order. Then we could add the entry into the index even though it was deleted.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (ISPN-6436) Overriding the name of an indexed property is not supported with DSL query
by Gustavo Fernandes (JIRA)
[ https://issues.jboss.org/browse/ISPN-6436?page=com.atlassian.jira.plugin.... ]
Gustavo Fernandes updated ISPN-6436:
------------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> Overriding the name of an indexed property is not supported with DSL query
> --------------------------------------------------------------------------
>
> Key: ISPN-6436
> URL: https://issues.jboss.org/browse/ISPN-6436
> Project: Infinispan
> Issue Type: Bug
> Components: Embedded Querying
> Affects Versions: 8.0.0.Final
> Reporter: Adrian Nistor
> Assignee: Adrian Nistor
> Fix For: 9.0.0.Alpha2, 9.0.0.Final
>
>
> If @Field(name="xyz") is used on an object property to customize the property name this will lead to the property not being found by the parser. The parser still looks for it using the java-beans naming conventions and ignores the 'name' attribute of the annotation.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (ISPN-6549) The query-dsl bundle does not export required packages for OSGi
by Gustavo Fernandes (JIRA)
[ https://issues.jboss.org/browse/ISPN-6549?page=com.atlassian.jira.plugin.... ]
Gustavo Fernandes updated ISPN-6549:
------------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> The query-dsl bundle does not export required packages for OSGi
> ---------------------------------------------------------------
>
> Key: ISPN-6549
> URL: https://issues.jboss.org/browse/ISPN-6549
> Project: Infinispan
> Issue Type: Bug
> Components: Remote Querying
> Affects Versions: 8.2.0.Final
> Reporter: Adrian Nistor
> Assignee: Adrian Nistor
> Fix For: 9.0.0.Alpha2, 8.2.2.Final
>
>
> The query-dsl bundle does not export correct packages via Export-Package entry in Manifest.mf file. Packages called org.infinispan.query.dsl and org.infinispan.query.dsl.impl are required by other Hot Rod client modules. As a result, the Remote Queries are not available through camel-jbossdatagrid component.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (ISPN-6298) Network partition detection not working in mgmt console
by Pedro Zapata (JIRA)
[ https://issues.jboss.org/browse/ISPN-6298?page=com.atlassian.jira.plugin.... ]
Pedro Zapata updated ISPN-6298:
-------------------------------
Status: Open (was: New)
> Network partition detection not working in mgmt console
> -------------------------------------------------------
>
> Key: ISPN-6298
> URL: https://issues.jboss.org/browse/ISPN-6298
> Project: Infinispan
> Issue Type: Bug
> Components: Console
> Affects Versions: 8.1.2.Final
> Reporter: Jiří Holuša
> Assignee: Vladimir Blagojevic
>
> Page: Clusters -> select server group.
> When I create a network partition and go to the page above, I still see the cluster status as "started". According to https://issues.jboss.org/browse/ISPN-5768 , there should be something as "Degraded"
> I checked that the cluster is really partitioned. When I go to JConsole, I see in JGroups JChannel attributes, that the "view" is only partial. I also see in the server logs that servers correctly detected the split.
> When I go to homepage (or the "Status event" tab), I see in the "Latest Grid Events:" that the split happened, hence the mgmt console is able to correctly detect it elsewhere.
> Note that neither the status of a cache, which has configured partition handling to true, changes.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months