June 2016 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-6742) Console shows cache available and disabled at the same time

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-6742?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-6742: -------------------------------------- Status: Open (was: New) > Console shows cache available and disabled at the same time > ----------------------------------------------------------- > > Key: ISPN-6742 > URL: https://issues.jboss.org/browse/ISPN-6742 > Project: Infinispan > Issue Type: Bug > Components: Console > Affects Versions: 8.2.2.Final > Reporter: Jiří Holuša > Assignee: Vladimir Blagojevic > Attachments: attachment.png > > > Page: go to cache detail and click "Actions" -> "Disable". > After confirmation, the cache status is still "Available", but new red box appears with text "Disabled", see the attachment. This doesn't seem to me very intuitive, if the cache is disabled, it should be IMO unavailable and this should be also reflected in the caches list. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6742) Console shows cache available and disabled at the same time

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-6742?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic commented on ISPN-6742: ------------------------------------------- Confirmed - thanks [~jholusa] > Console shows cache available and disabled at the same time > ----------------------------------------------------------- > > Key: ISPN-6742 > URL: https://issues.jboss.org/browse/ISPN-6742 > Project: Infinispan > Issue Type: Bug > Components: Console > Affects Versions: 8.2.2.Final > Reporter: Jiří Holuša > Assignee: Vladimir Blagojevic > Attachments: attachment.png > > > Page: go to cache detail and click "Actions" -> "Disable". > After confirmation, the cache status is still "Available", but new red box appears with text "Disabled", see the attachment. This doesn't seem to me very intuitive, if the cache is disabled, it should be IMO unavailable and this should be also reflected in the caches list. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (HRJS-16) Generate API docs for JS client

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/HRJS-16?page=com.atlassian.jira.plugin.sy... ] Galder Zamarreño updated HRJS-16: --------------------------------- Attachment: screenshot-1.png > Generate API docs for JS client > ------------------------------- > > Key: HRJS-16 > URL: https://issues.jboss.org/browse/HRJS-16 > Project: Infinispan Javascript client > Issue Type: Task > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 0.3.0 > > Attachments: screenshot-1.png > > > We should generate API documentation for the JS client so that it is clear which API is available. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (HRJS-16) Generate API docs for JS client

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/HRJS-16?page=com.atlassian.jira.plugin.sy... ] Galder Zamarreño commented on HRJS-16: -------------------------------------- The best option out there seems to be to use JSDoc. I played a bit with it in this [branch|https://github.com/galderz/js-client/tree/t_16] {code} $ npm install jsdoc $ ./node_modules/.bin/jsdoc lib/*.js {code} ^ Executing that generates, on the minimal JSDoc added in the branch, generates some reasonably looking API docs, see attached screenshot. > Generate API docs for JS client > ------------------------------- > > Key: HRJS-16 > URL: https://issues.jboss.org/browse/HRJS-16 > Project: Infinispan Javascript client > Issue Type: Task > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 0.3.0 > > > We should generate API documentation for the JS client so that it is clear which API is available. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6748) Deprecate Singleton Mode for Persistent Stores

by Ryan Emerson (JIRA)

Ryan Emerson created ISPN-6748: ---------------------------------- Summary: Deprecate Singleton Mode for Persistent Stores Key: ISPN-6748 URL: https://issues.jboss.org/browse/ISPN-6748 Project: Infinispan Issue Type: Task Affects Versions: 9.0.0.Alpha2 Reporter: Ryan Emerson Assignee: Ryan Emerson In shared mode only the primary owner of a key writes to the shared store, therefore there is no obvious use-case for having a singleton mode which delegates all writes to a single node. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6748) Deprecate Singleton Mode for Persistent Stores

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-6748?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-6748: ------------------------------- Component/s: Loaders and Stores > Deprecate Singleton Mode for Persistent Stores > ---------------------------------------------- > > Key: ISPN-6748 > URL: https://issues.jboss.org/browse/ISPN-6748 > Project: Infinispan > Issue Type: Task > Components: Loaders and Stores > Affects Versions: 9.0.0.Alpha2 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > > In shared mode only the primary owner of a key writes to the shared store, therefore there is no obvious use-case for having a singleton mode which delegates all writes to a single node. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6747) Disabled buttons in dropdown menus are still functional

by Jiří Holuša (JIRA)

[ https://issues.jboss.org/browse/ISPN-6747?page=com.atlassian.jira.plugin.... ] Jiří Holuša updated ISPN-6747: ------------------------------ Description: For example, on cache detail page, in "Actions" dropdown menu, if cache is enabled than the "Enable" option is disabled. Currently, the button is grey, but when you try clicking on it, it will execute the operation anyway. Please note that this affects every button in the dropdown menus, more specifically every <a> link, because you cannot use disabled="disabled" (therefore ng-disabled) on the <a> link as you do with the <button> elements. I found a root cause and also a fix, however, I wasn't able to find a place, where to modify the CSS style, since the hierarchy is quite complicated. To fix the issue, you have to add {code} li.disabled { cursor: not-allowed; } {code} to the CSS of the directly encapsulating <li>, and following {code} li.disabled a { pointer-events: none; } {code} to the CSS of the disabled <a> tag. The reason to split this two is that the cursor and pointer-events don't work well together and we want to have both "not-allowed" cursor and not-clickable link. See https://github.com/twbs/bootstrap/issues/16088 for details. I would be happy to implement the fix and send a PR, just give me a hint which one is the CSS style to be modified. I essentially need to modify the CSS on the URL http://localhost:9990/console/built_components/patternfly/dist/css/patter... . Or should it be overwritten somewhere else? I've tested the fix via modifying the CSS directly in the browser on the fly, so I can confirm that it works. was: For example, on cache detail page, in "Actions" dropdown menu, if cache is enabled than the "Enable" option is disabled. Currently, the button is grey, but when you try clicking on it, it will execute the operation anyway. Please note that this affects every button in the dropdown menus, more specifically every <a> link, because you cannot use disabled="disabled" (therefore ng-disabled) on the <a> link as you do with the <button> elements. I found a root cause and also a fix, however, I wasn't able to find a place, where to modify the CSS style, since the hierarchy is quite complicated. To fix the issue, you have to add {code} li.disabled { cursor: not-allowed; } {code} to the CSS of the directly encapsulating <li>, and following {code} li.disabled a { pointer-events: none; } {code} to the CSS of the disabled <a> tag. The reason to split this two is that the cursor and pointer-events don't work well together and we want to have both "not-allowed" cursor and not-clickable link. See https://github.com/twbs/bootstrap/issues/16088 for details. I would be happy to implement the fix and send a PR, just give me a hint which one is the CSS style to be modified. I essentially need to modify the CSS on the URL http://localhost:9990/console/built_components/patternfly/dist/css/patter... . Or should it be overwritten somewhere else? > Disabled buttons in dropdown menus are still functional > ------------------------------------------------------- > > Key: ISPN-6747 > URL: https://issues.jboss.org/browse/ISPN-6747 > Project: Infinispan > Issue Type: Bug > Components: Console > Affects Versions: 8.2.2.Final > Reporter: Jiří Holuša > Assignee: Vladimir Blagojevic > > For example, on cache detail page, in "Actions" dropdown menu, if cache is enabled than the "Enable" option is disabled. Currently, the button is grey, but when you try clicking on it, it will execute the operation anyway. Please note that this affects every button in the dropdown menus, more specifically every <a> link, because you cannot use disabled="disabled" (therefore ng-disabled) on the <a> link as you do with the <button> elements. > I found a root cause and also a fix, however, I wasn't able to find a place, where to modify the CSS style, since the hierarchy is quite complicated. To fix the issue, you have to add > {code} > li.disabled { > cursor: not-allowed; > } > {code} > to the CSS of the directly encapsulating <li>, and following > {code} > li.disabled a { > pointer-events: none; > } > {code} > to the CSS of the disabled <a> tag. The reason to split this two is that the cursor and pointer-events don't work well together and we want to have both "not-allowed" cursor and not-clickable link. See https://github.com/twbs/bootstrap/issues/16088 for details. > I would be happy to implement the fix and send a PR, just give me a hint which one is the CSS style to be modified. I essentially need to modify the CSS on the URL http://localhost:9990/console/built_components/patternfly/dist/css/patter... . Or should it be overwritten somewhere else? > I've tested the fix via modifying the CSS directly in the browser on the fly, so I can confirm that it works. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6747) Disabled buttons in dropdown menus are still functional

by Jiří Holuša (JIRA)

Jiří Holuša created ISPN-6747: --------------------------------- Summary: Disabled buttons in dropdown menus are still functional Key: ISPN-6747 URL: https://issues.jboss.org/browse/ISPN-6747 Project: Infinispan Issue Type: Bug Components: Console Affects Versions: 8.2.2.Final Reporter: Jiří Holuša Assignee: Vladimir Blagojevic For example, on cache detail page, in "Actions" dropdown menu, if cache is enabled than the "Enable" option is disabled. Currently, the button is grey, but when you try clicking on it, it will execute the operation anyway. Please note that this affects every button in the dropdown menus, more specifically every <a> link, because you cannot use disabled="disabled" (therefore ng-disabled) on the <a> link as you do with the <button> elements. I found a root cause and also a fix, however, I wasn't able to find a place, where to modify the CSS style, since the hierarchy is quite complicated. To fix the issue, you have to add {code} li.disabled { cursor: not-allowed; } {code} to the CSS of the directly encapsulating <li>, and following {code} li.disabled a { pointer-events: none; } {code} to the CSS of the disabled <a> tag. The reason to split this two is that the cursor and pointer-events don't work well together and we want to have both "not-allowed" cursor and not-clickable link. See https://github.com/twbs/bootstrap/issues/16088 for details. I would be happy to implement the fix and send a PR, just give me a hint which one is the CSS style to be modified. I essentially need to modify the CSS on the URL http://localhost:9990/console/built_components/patternfly/dist/css/patter... . Or should it be overwritten somewhere else? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (HRJS-16) Generate API docs for JS client

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/HRJS-16?page=com.atlassian.jira.plugin.sy... ] Tristan Tarrant updated HRJS-16: -------------------------------- Fix Version/s: 0.3.0 > Generate API docs for JS client > ------------------------------- > > Key: HRJS-16 > URL: https://issues.jboss.org/browse/HRJS-16 > Project: Infinispan Javascript client > Issue Type: Task > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 0.3.0 > > > We should generate API documentation for the JS client so that it is clear which API is available. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (HRJS-16) Generate API docs for JS client

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/HRJS-16?page=com.atlassian.jira.plugin.sy... ] Tristan Tarrant updated HRJS-16: -------------------------------- Status: Open (was: New) > Generate API docs for JS client > ------------------------------- > > Key: HRJS-16 > URL: https://issues.jboss.org/browse/HRJS-16 > Project: Infinispan Javascript client > Issue Type: Task > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 0.3.0 > > > We should generate API documentation for the JS client so that it is clear which API is available. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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