October 2019 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-10579) TransactionalExceptionEvictionInterceptor 1PC PrepareCommand should not be added to pending map

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-10579?page=com.atlassian.jira.plugin... ] Dan Berindei updated ISPN-10579: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > TransactionalExceptionEvictionInterceptor 1PC PrepareCommand should not be added to pending map > ----------------------------------------------------------------------------------------------- > > Key: ISPN-10579 > URL: https://issues.jboss.org/browse/ISPN-10579 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.4.16.Final, 10.0.0.CR1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 10.0.0.CR3, 9.4.17.Final > > > One-phase {{PrepareCommand}} s commit their changes directly, no need to add them to the {{pending}} map. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10718) Ensure protobuf metadata cache is predictably started when the cache manager has finished initializing

by Nistor Adrian (Jira)

[ https://issues.jboss.org/browse/ISPN-10718?page=com.atlassian.jira.plugin... ] Nistor Adrian updated ISPN-10718: --------------------------------- Status: Open (was: New) > Ensure protobuf metadata cache is predictably started when the cache manager has finished initializing > ------------------------------------------------------------------------------------------------------ > > Key: ISPN-10718 > URL: https://issues.jboss.org/browse/ISPN-10718 > Project: Infinispan > Issue Type: Enhancement > Components: Remote Querying > Affects Versions: 10.0.0.CR2 > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 10.0.0.CR3 > > > Casual code browsing led me to ProtobufMetadataCacheStartedTest where I see we actually assert that protobuf metadata cache is not started on cache manager start, it is actually started lazily, when first non-internal cache starts. And the code is written as if this is a (happy) accident. That's very dangerous. We should start it predictably, when the cache manager has finished startup. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10718) Ensure protobuf metadata cache is predictably started when the cache manager has finished initializing

by Nistor Adrian (Jira)

[ https://issues.jboss.org/browse/ISPN-10718?page=com.atlassian.jira.plugin... ] Nistor Adrian updated ISPN-10718: --------------------------------- Summary: Ensure protobuf metadata cache is predictably started when the cache manager has finished initializing (was: Move creation of protobuf metadata cache config back into ProtobufMetadataManagerImpl) > Ensure protobuf metadata cache is predictably started when the cache manager has finished initializing > ------------------------------------------------------------------------------------------------------ > > Key: ISPN-10718 > URL: https://issues.jboss.org/browse/ISPN-10718 > Project: Infinispan > Issue Type: Enhancement > Components: Remote Querying > Affects Versions: 10.0.0.CR2 > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 10.0.0.CR3 > > > Casual code browsing led me to ProtobufMetadataCacheStartedTest where I see we actually assert that protobuf metadata cache is not started on cache manager start, it is actually started lazily, when first non-internal cache starts. And the code is written as if this is a (happy) accident. That's very dangerous. We should start it predictably, when the cache manager has finished startup. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10718) Move creation of protobuf metadata cache config back into ProtobufMetadataManagerImpl

by Nistor Adrian (Jira)

Nistor Adrian created ISPN-10718: ------------------------------------ Summary: Move creation of protobuf metadata cache config back into ProtobufMetadataManagerImpl Key: ISPN-10718 URL: https://issues.jboss.org/browse/ISPN-10718 Project: Infinispan Issue Type: Enhancement Components: Remote Querying Affects Versions: 10.0.0.CR2 Reporter: Nistor Adrian Assignee: Nistor Adrian Fix For: 10.0.0.CR3 Casual code browsing led me to ProtobufMetadataCacheStartedTest where I see we actually assert that protobuf metadata cache is not started on cache manager start, it is actually started lazily, when first non-internal cache starts. And the code is written as if this is a (happy) accident. That's very dangerous. We should start it predictably, when the cache manager has finished startup. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10717) Administration should not require the REST endpoint to be enabled

by Alan Field (Jira)

[ https://issues.jboss.org/browse/ISPN-10717?page=com.atlassian.jira.plugin... ] Alan Field updated ISPN-10717: ------------------------------ Description: Administration should not require the REST endpoint to be enabled. We should be able to use Admin even if that isn't enabled. Admin should not require REST, it is a design/usability problem. was: Administration should not require the REST endpoint to be enabled. We should be able to use Admin even if that isn't enabled. Admin should require REST, it is a design/usability problem. > Administration should not require the REST endpoint to be enabled > ----------------------------------------------------------------- > > Key: ISPN-10717 > URL: https://issues.jboss.org/browse/ISPN-10717 > Project: Infinispan > Issue Type: Bug > Affects Versions: 10.0.0.CR2 > Reporter: Diego Lovison > Priority: Minor > > Administration should not require the REST endpoint to be enabled. We should be able to use Admin even if that isn't enabled. > Admin should not require REST, it is a design/usability problem. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10717) Administration should not require the REST endpoint to be enabled

by Diego Lovison (Jira)

Diego Lovison created ISPN-10717: ------------------------------------ Summary: Administration should not require the REST endpoint to be enabled Key: ISPN-10717 URL: https://issues.jboss.org/browse/ISPN-10717 Project: Infinispan Issue Type: Bug Affects Versions: 10.0.0.CR2 Reporter: Diego Lovison Administration should not require the REST endpoint to be enabled. We should be able to use Admin even if that isn't enabled. Admin should require REST, it is a design/usability problem. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10626) Community Site: Clean up fetch_docs to remove asciidoc warnings

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10626?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10626: ----------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 10.0.0.CR3 Resolution: Done > Community Site: Clean up fetch_docs to remove asciidoc warnings > --------------------------------------------------------------- > > Key: ISPN-10626 > URL: https://issues.jboss.org/browse/ISPN-10626 > Project: Infinispan > Issue Type: Task > Components: Documentation-Core, Website > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > Fix For: 10.0.0.CR3 > > > fetch_docs.rb generates html for .adoc files which results in warnings when building the community site, such as the following: > asciidoctor: WARNING: dropping line containing reference to missing attribute: topics > asciidoctor: WARNING: dropping line containing reference to missing attribute: topics > asciidoctor: WARNING: dropping line containing reference to missing attribute: topics > asciidoctor: WARNING: dropping line containing reference to missing attribute: topics > asciidoctor: WARNING: dropping line containing reference to missing attribute: topics > asciidoctor: WARNING: dropping line containing reference to missing attribute: topics > asciidoctor: WARNING: dropping line containing reference to missing attribute: topics > asciidoctor: WARNING: dropping line containing reference to missing attribute: topics > asciidoctor: WARNING: dropping line containing reference to missing attribute: topics > asciidoctor: WARNING: dropping line containing reference to missing attribute: topics > asciidoctor: WARNING: dropping line containing reference to missing attribute: stories > asciidoctor: WARNING: dropping line containing reference to missing attribute: stories > asciidoctor: WARNING: dropping line containing reference to missing attribute: stories > asciidoctor: WARNING: dropping line containing reference to missing attribute: stories > asciidoctor: WARNING: dropping line containing reference to missing attribute: stories > asciidoctor: WARNING: oc_logs_clusterview.adoc: line 7: invalid style for paragraph: {example_crd_name}-0|0] (1) [{example_crd_name}-0 > The purpose of this task is to modify fetch_docs.rb so that it generates HTML from the .asciidoc file only. Also leave the community site in a cleaner state. No need to copy across the asciidoc files and other content. We only need a single HTML file per title on the site. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10716) Infinispan index banner links to a page with invalid certificates

by Pavel Drobek (Jira)

Pavel Drobek created ISPN-10716: ----------------------------------- Summary: Infinispan index banner links to a page with invalid certificates Key: ISPN-10716 URL: https://issues.jboss.org/browse/ISPN-10716 Project: Infinispan Issue Type: Bug Components: REST Affects Versions: 10.0.0.CR2 Reporter: Pavel Drobek Infinispans banner on main page (http://localhost:11222) redirects to https://www.infinispan.org which doesn't have valid certificates. Certificates on that page are valid only for github.com. Quoting Firefox: bq. Firefox does not trust this site because it uses a certificate that is not valid for www.infinispan.org. The certificate is only valid for the following names: www.github.com, *.github.io, *.githubusercontent.com, *.github.com, github.com, github.io, githubusercontent.com Either [link|https://github.com/infinispan/infinispan/blob/master/server/rest/src...] should be fixed to point to https://infinispan.org with valid certificates or fix the page's certificates. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10427) ServerNG: Windows batch files

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-10427?page=com.atlassian.jira.plugin... ] Ryan Emerson resolved ISPN-10427. --------------------------------- Resolution: Done > ServerNG: Windows batch files > ----------------------------- > > Key: ISPN-10427 > URL: https://issues.jboss.org/browse/ISPN-10427 > Project: Infinispan > Issue Type: Sub-task > Components: Server > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.0.0.CR3 > > > We need batch files for starting the server and tools on Windows -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10458) Address comments on ISPN-9723

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-10458?page=com.atlassian.jira.plugin... ] Dan Berindei updated ISPN-10458: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Address comments on ISPN-9723 > ----------------------------- > > Key: ISPN-10458 > URL: https://issues.jboss.org/browse/ISPN-10458 > Project: Infinispan > Issue Type: Task > Components: Core > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > Fix For: 10.0.0.CR3 > > > There are some comments on https://github.com/infinispan/infinispan/pull/7168 that still need to be addressed or changed. -- This message was sent by Atlassian Jira (v7.13.8#713008)

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