[GitHub] [sling-org-apache-sling-jcr-oak-server] sonarcloud[bot] commented on pull request #8: SLING-12035 bump oak dependency for compatibility with version 1.56.0
sonarcloud[bot] commented on PR #8: URL: https://github.com/apache/sling-org-apache-sling-jcr-oak-server/pull/8#issuecomment-1730363739 Kudos, SonarCloud Quality Gate passed! [](https://sonarcloud.io/dashboard?id=apache_sling-org-apache-sling-jcr-oak-server&pullRequest=8) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jcr-oak-server&pullRequest=8&resolved=false&types=BUG) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jcr-oak-server&pullRequest=8&resolved=false&types=BUG) [0 Bugs](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jcr-oak-server&pullRequest=8&resolved=false&types=BUG) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jcr-oak-server&pullRequest=8&resolved=false&types=VULNERABILITY) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jcr-oak-server&pullRequest=8&resolved=false&types=VULNERABILITY) [0 Vulnerabilities](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jcr-oak-server&pullRequest=8&resolved=false&types=VULNERABILITY) [](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-jcr-oak-server&pullRequest=8&resolved=false&types=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-jcr-oak-server&pullRequest=8&resolved=false&types=SECURITY_HOTSPOT) [0 Security Hotspots](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-jcr-oak-server&pullRequest=8&resolved=false&types=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jcr-oak-server&pullRequest=8&resolved=false&types=CODE_SMELL) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jcr-oak-server&pullRequest=8&resolved=false&types=CODE_SMELL) [0 Code Smells](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jcr-oak-server&pullRequest=8&resolved=false&types=CODE_SMELL) [](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-jcr-oak-server&pullRequest=8&metric=coverage&view=list) No Coverage information [](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-jcr-oak-server&pullRequest=8&metric=new_duplicated_lines_density&view=list) [0.0% Duplication](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-jcr-oak-server&pullRequest=8&metric=new_duplicated_lines_density&view=list) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [sling-org-apache-sling-jcr-maintenance] sonarcloud[bot] commented on pull request #3: SLING-12034 bump oak dependency for compatibility with version 1.56.0
sonarcloud[bot] commented on PR #3: URL: https://github.com/apache/sling-org-apache-sling-jcr-maintenance/pull/3#issuecomment-1730358828 Kudos, SonarCloud Quality Gate passed! [](https://sonarcloud.io/dashboard?id=apache_sling-org-apache-sling-jcr-maintenance&pullRequest=3) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jcr-maintenance&pullRequest=3&resolved=false&types=BUG) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jcr-maintenance&pullRequest=3&resolved=false&types=BUG) [0 Bugs](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jcr-maintenance&pullRequest=3&resolved=false&types=BUG) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jcr-maintenance&pullRequest=3&resolved=false&types=VULNERABILITY) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jcr-maintenance&pullRequest=3&resolved=false&types=VULNERABILITY) [0 Vulnerabilities](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jcr-maintenance&pullRequest=3&resolved=false&types=VULNERABILITY) [](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-jcr-maintenance&pullRequest=3&resolved=false&types=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-jcr-maintenance&pullRequest=3&resolved=false&types=SECURITY_HOTSPOT) [0 Security Hotspots](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-jcr-maintenance&pullRequest=3&resolved=false&types=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jcr-maintenance&pullRequest=3&resolved=false&types=CODE_SMELL) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jcr-maintenance&pullRequest=3&resolved=false&types=CODE_SMELL) [0 Code Smells](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jcr-maintenance&pullRequest=3&resolved=false&types=CODE_SMELL) [](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-jcr-maintenance&pullRequest=3&metric=coverage&view=list) No Coverage information [](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-jcr-maintenance&pullRequest=3&metric=new_duplicated_lines_density&view=list) [0.0% Duplication](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-jcr-maintenance&pullRequest=3&metric=new_duplicated_lines_density&view=list) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (SLING-12035) bump oak dependency for compatibility with oak version 1.56.0
[ https://issues.apache.org/jira/browse/SLING-12035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17767739#comment-17767739 ] Eric Norman commented on SLING-12035: - [~rombert] It doesn't seem that this scenario fits exactly into any of the examples from the version policy docs since only the version ranges of the "Import-Package" clause is really different. However, I think that would make sense to bump the minor version number to indicate that the change is more than a simple bug fix. # [https://sling.apache.org/documentation/development/version-policy.html] I will change the version number in the PR and add a section to the README about the compatibility of the various versions. > bump oak dependency for compatibility with oak version 1.56.0 > - > > Key: SLING-12035 > URL: https://issues.apache.org/jira/browse/SLING-12035 > Project: Sling > Issue Type: Improvement >Reporter: Eric Norman >Assignee: Eric Norman >Priority: Major > Fix For: JCR Oak Server 1.3.2 > > > In order for sling to work with the latest release of oak, the oak > dependencies must be bumped to 1.56.0 or later. > The oak 1.56.0 release completed the removal of the dependency on the old > guava library which required a bump of the major version of some exported > packages whose public api has changed. The imports of those changed packages > must be bumped to the new major version number in order for the bundles to > resolve properly in the runtime. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[Jenkins] Sling » Modules » sling-org-apache-sling-starter » master #1029 is FIXED
Please see https://ci-builds.apache.org/job/Sling/job/modules/job/sling-org-apache-sling-starter/job/master/1029/ for details. No further emails will be sent until the status of the build is changed.
[GitHub] [sling-org-apache-sling-starter] rombert opened a new pull request, #238: SLING-12036 - Switch JDK image to Eclipse Temurin
rombert opened a new pull request, #238: URL: https://github.com/apache/sling-org-apache-sling-starter/pull/238 (no comment) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (SLING-12036) Switch JDK image to Eclipse Temurin
[ https://issues.apache.org/jira/browse/SLING-12036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-12036: Summary: Switch JDK image to Eclipse Temurin (was: Switch JDK image to Eclipse Temurim) > Switch JDK image to Eclipse Temurin > --- > > Key: SLING-12036 > URL: https://issues.apache.org/jira/browse/SLING-12036 > Project: Sling > Issue Type: Improvement > Components: Starter >Reporter: Robert Munteanu >Assignee: Robert Munteanu >Priority: Major > Fix For: Starter 13 > > > The openjdk images are no longer maintained, see note at > https://hub.docker.com/_/openjdk . Eclipse Temurim seems like a viable > alternative, we should use that instead. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (SLING-12036) Switch JDK image to Eclipse Temurim
Robert Munteanu created SLING-12036: --- Summary: Switch JDK image to Eclipse Temurim Key: SLING-12036 URL: https://issues.apache.org/jira/browse/SLING-12036 Project: Sling Issue Type: Improvement Components: Starter Reporter: Robert Munteanu Assignee: Robert Munteanu Fix For: Starter 13 The openjdk images are no longer maintained, see note at https://hub.docker.com/_/openjdk . Eclipse Temurim seems like a viable alternative, we should use that instead. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [sling-org-apache-sling-starter] renovate-bot opened a new pull request, #237: chore(deps): update dependency org.apache.sling:org.apache.sling.resourceresolver to v1.11.0
renovate-bot opened a new pull request, #237: URL: https://github.com/apache/sling-org-apache-sling-starter/pull/237 [](https://renovatebot.com) This PR contains the following updates: | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | [org.apache.sling:org.apache.sling.resourceresolver](https://sling.apache.org) ([source](https://gitbox.apache.org/repos/asf?p=sling-org-apache-sling-resourceresolver.git)) | `1.10.0` -> `1.11.0` | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate](https://www.mend.io/free-developer-tools/renovate/). View repository job log [here](https://developer.mend.io/github/apache/sling-org-apache-sling-starter). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [sling-org-apache-sling-caconfig-integration-tests] sonarcloud[bot] commented on pull request #1: SLING-11114 update SLING API to 2.21.0
sonarcloud[bot] commented on PR #1: URL: https://github.com/apache/sling-org-apache-sling-caconfig-integration-tests/pull/1#issuecomment-1730036093 Kudos, SonarCloud Quality Gate passed! [](https://sonarcloud.io/dashboard?id=apache_sling-org-apache-sling-caconfig-integration-tests&pullRequest=1) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-caconfig-integration-tests&pullRequest=1&resolved=false&types=BUG) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-caconfig-integration-tests&pullRequest=1&resolved=false&types=BUG) [0 Bugs](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-caconfig-integration-tests&pullRequest=1&resolved=false&types=BUG) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-caconfig-integration-tests&pullRequest=1&resolved=false&types=VULNERABILITY) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-caconfig-integration-tests&pullRequest=1&resolved=false&types=VULNERABILITY) [0 Vulnerabilities](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-caconfig-integration-tests&pullRequest=1&resolved=false&types=VULNERABILITY) [](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-caconfig-integration-tests&pullRequest=1&resolved=false&types=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-caconfig-integration-tests&pullRequest=1&resolved=false&types=SECURITY_HOTSPOT) [0 Security Hotspots](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-caconfig-integration-tests&pullRequest=1&resolved=false&types=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-caconfig-integration-tests&pullRequest=1&resolved=false&types=CODE_SMELL) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-caconfig-integration-tests&pullRequest=1&resolved=false&types=CODE_SMELL) [0 Code Smells](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-caconfig-integration-tests&pullRequest=1&resolved=false&types=CODE_SMELL) [](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-caconfig-integration-tests&pullRequest=1) No Coverage information [](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-caconfig-integration-tests&pullRequest=1&metric=new_duplicated_lines_density&view=list) [0.0% Duplication](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-caconfig-integration-tests&pullRequest=1&metric=new_duplicated_lines_density&view=list) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
RE: [RESULT] [VOTE] Release Apache Sling GraphQL Core version 0.0.24
> Can a PMC push the release to > https://dist.apache.org/repos/dist/release/sling/. I will finish the rest > afterwards. Completed: At revision: 64132 stefan
Re: [RESULT] [VOTE] Release Apache Sling GraphQL Core version 0.0.24
Hi This is still push is still pending. Can a PMC do it for me as I cannot. Cheers - Andy > On Sep 19, 2023, at 12:49 PM, Andreas Schaefer > wrote: > > Can a PMC push the release to > https://dist.apache.org/repos/dist/release/sling/. I will finish the rest > afterwards.
[jira] [Closed] (SLING-11756) resource resolver: rewrite getVanityPathDefinition for more clarity
[ https://issues.apache.org/jira/browse/SLING-11756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Sedding closed SLING-11756. -- > resource resolver: rewrite getVanityPathDefinition for more clarity > > > Key: SLING-11756 > URL: https://issues.apache.org/jira/browse/SLING-11756 > Project: Sling > Issue Type: Sub-task > Components: ResourceResolver >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Trivial > Fix For: Resource Resolver 1.11.0 > > Time Spent: 2h 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (SLING-12020) resource resolver: alias metric has confusing name
[ https://issues.apache.org/jira/browse/SLING-12020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Sedding closed SLING-12020. -- > resource resolver: alias metric has confusing name > -- > > Key: SLING-12020 > URL: https://issues.apache.org/jira/browse/SLING-12020 > Project: Sling > Issue Type: Bug > Components: ResourceResolver >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Major > Fix For: Resource Resolver 1.11.0 > > > The metric "numberOfAliases" has a very very misleading name; actually it's > the number of nodes that have any number of child nodes with aliases. So, > this could be a magnitude less than the actual number of aliases. > Rename? Fix? (that would require counting instead of just returning the map > size) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (SLING-11541) vanity path query: attempt to query sorted by first vanity path, check results
[ https://issues.apache.org/jira/browse/SLING-11541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Sedding closed SLING-11541. -- > vanity path query: attempt to query sorted by first vanity path, check results > -- > > Key: SLING-11541 > URL: https://issues.apache.org/jira/browse/SLING-11541 > Project: Sling > Issue Type: Improvement > Components: ResourceResolver >Reporter: Julian Reschke >Assignee: Carsten Ziegeler >Priority: Minor > Fix For: Resource Resolver 1.11.0 > > Time Spent: 2h 10m > Remaining Estimate: 0h > > This is another step towards the goal of using paged queries. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (SLING-11742) Provide alternative equitable terminology for properties
[ https://issues.apache.org/jira/browse/SLING-11742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Sedding closed SLING-11742. -- > Provide alternative equitable terminology for properties > > > Key: SLING-11742 > URL: https://issues.apache.org/jira/browse/SLING-11742 > Project: Sling > Issue Type: Improvement >Reporter: Cioriia Cristian >Assignee: Cioriia Cristian >Priority: Major > Fix For: Resource Resolver 1.11.0 > > Time Spent: 1h 40m > Remaining Estimate: 0h > > The "resource.resolver.vanitypath.blacklist" and > "resource.resolver.vanitypath.whitelist" proeprties contain terms which are > considered inequitable terminology and some customers are prevented to use > these terms by their git commit policies. > Therefore, some more acceptable equivalents should be provided for these > terms. The proposal is to provide the > "resource.resolver.vanitypath.deniedlist" and > "resource.resolver.vanitypath.allowedlist" alternatives for them. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (SLING-11835) resource resolver: should not use SNAPSHOT version of API
[ https://issues.apache.org/jira/browse/SLING-11835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Sedding closed SLING-11835. -- > resource resolver: should not use SNAPSHOT version of API > - > > Key: SLING-11835 > URL: https://issues.apache.org/jira/browse/SLING-11835 > Project: Sling > Issue Type: Task > Components: ResourceResolver >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Major > Fix For: Resource Resolver 1.11.0 > > > Introduced during the last release > (https://github.com/apache/sling-org-apache-sling-resourceresolver/commit/0fa68503b788bd016a9e87ab8dcf406848e0ea07) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (SLING-12017) resource resolver: add fallback when paged query fails due to missing index
[ https://issues.apache.org/jira/browse/SLING-12017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Sedding closed SLING-12017. -- > resource resolver: add fallback when paged query fails due to missing index > --- > > Key: SLING-12017 > URL: https://issues.apache.org/jira/browse/SLING-12017 > Project: Sling > Issue Type: Bug > Components: ResourceResolver >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Major > Fix For: Resource Resolver 1.11.0 > > > When the underlying repo supports the "first" operator, but the appropiate > index is missing, the query might fail with an UnspportedOperationException, > even though it might have suceeded without paging. > Therefore, catch that exception and fallback to simple query. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (SLING-11593) Clarify behaviour of "Vanity Path Precedence" flag for the resource resolver factory
[
https://issues.apache.org/jira/browse/SLING-11593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Sedding closed SLING-11593.
--
> Clarify behaviour of "Vanity Path Precedence" flag for the resource resolver
> factory
>
>
> Key: SLING-11593
> URL: https://issues.apache.org/jira/browse/SLING-11593
> Project: Sling
> Issue Type: Improvement
> Components: ResourceResolver
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
>Priority: Minor
> Fix For: Resource Resolver 1.11.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The "Vanity Path Precedence" flag is currently described as {quote}This flag
> controls whether vanity paths will have precedence over existing /etc/map
> mapping{quote}.
> We should clarify that this flag influences only the resolution process, not
> mapping selection.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (SLING-11757) resource resolver: pathless URL in vanity path causes NPE in ResourceMapperImpl.apply()
[
https://issues.apache.org/jira/browse/SLING-11757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Sedding closed SLING-11757.
--
> resource resolver: pathless URL in vanity path causes NPE in
> ResourceMapperImpl.apply()
> ---
>
> Key: SLING-11757
> URL: https://issues.apache.org/jira/browse/SLING-11757
> Project: Sling
> Issue Type: Sub-task
> Components: ResourceResolver
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Major
> Fix For: Resource Resolver 1.11.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> {noformat}
> java.lang.NullPointerException
> at java.lang.String.concat(String.java:2027)
> at
> org.apache.sling.resourceresolver.impl.mapping.ResourceMapperImpl$ApplyContextPath.apply(ResourceMapperImpl.java:371)
> at
> org.apache.sling.resourceresolver.impl.mapping.ResourceMapperImpl$ApplyContextPath.apply(ResourceMapperImpl.java:345)
> at java.util.ArrayList.replaceAll(ArrayList.java:1452)
> at
> org.apache.sling.resourceresolver.impl.mapping.ResourceMapperImpl.getAllMappings(ResourceMapperImpl.java:171)
> at
> org.apache.sling.resourceresolver.impl.mapping.ResourceMapperImpl.getMapping(ResourceMapperImpl.java:73)
> at
> org.apache.sling.resourceresolver.impl.mapping.ResourceMapperImplTest$ExpectedMappings.verify(ResourceMapperImplTest.java:510)
> at
> org.apache.sling.resourceresolver.impl.mapping.ResourceMapperImplTest.mapResourceWithVanityPathsURLTargetNoPath(ResourceMapperImplTest.java:402)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (SLING-12018) resource resolver: add metrics for resources with sling:alias/vanityPath found on startup
[ https://issues.apache.org/jira/browse/SLING-12018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Sedding closed SLING-12018. -- > resource resolver: add metrics for resources with sling:alias/vanityPath > found on startup > - > > Key: SLING-12018 > URL: https://issues.apache.org/jira/browse/SLING-12018 > Project: Sling > Issue Type: New Feature > Components: ResourceResolver >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Major > Fix For: Resource Resolver 1.11.0 > > > ...because the data model on the resources is not the same as in the caches, > so we want to know the actual numbers as well. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (SLING-12019) Avoid duplicate ResourceResolverFactory registrations
[ https://issues.apache.org/jira/browse/SLING-12019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Sedding closed SLING-12019. -- > Avoid duplicate ResourceResolverFactory registrations > - > > Key: SLING-12019 > URL: https://issues.apache.org/jira/browse/SLING-12019 > Project: Sling > Issue Type: Bug > Components: ResourceResolver >Affects Versions: Resource Resolver 1.10.0 >Reporter: Carsten Ziegeler >Assignee: Julian Sedding >Priority: Critical > Fix For: Resource Resolver 1.11.0 > > > It seems that in some situations a new resource resolver factory is > registered without unregistering the old one - which leads to two factories > being registered. As not all components do eager service binding, these > components stick to the old factory - and the old factory in turn is > basically "empty" meaning all resource providers are unregistered. This > prevents those components from reaching any resource, although everything > looks fine. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (SLING-11755) resource resolver: add test coverage for URL patterns in vanity paths
[ https://issues.apache.org/jira/browse/SLING-11755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Sedding closed SLING-11755. -- > resource resolver: add test coverage for URL patterns in vanity paths > - > > Key: SLING-11755 > URL: https://issues.apache.org/jira/browse/SLING-11755 > Project: Sling > Issue Type: Sub-task > Components: ResourceResolver >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Fix For: Resource Resolver 1.11.0 > > Time Spent: 1h 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (SLING-11581) use keyset pagination for vanity path query
[ https://issues.apache.org/jira/browse/SLING-11581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Sedding closed SLING-11581. -- > use keyset pagination for vanity path query > --- > > Key: SLING-11581 > URL: https://issues.apache.org/jira/browse/SLING-11581 > Project: Sling > Issue Type: Bug > Components: ResourceResolver >Reporter: Julian Reschke >Priority: Major > Fix For: Resource Resolver 1.11.0 > > Time Spent: 1h 50m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (SLING-11604) Async VanityPathInitializer should log when completed
[ https://issues.apache.org/jira/browse/SLING-11604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Sedding closed SLING-11604. -- > Async VanityPathInitializer should log when completed > - > > Key: SLING-11604 > URL: https://issues.apache.org/jira/browse/SLING-11604 > Project: Sling > Issue Type: Improvement > Components: ResourceResolver >Affects Versions: Resource Resolver 1.10.0 >Reporter: Joerg Hoh >Assignee: Carsten Ziegeler >Priority: Major > Fix For: Resource Resolver 1.11.0 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > In case the vanity paths are loaded asynchronously, the current > implementation writes a debug statement on completion which contains some > metrics. > It would be good if the loglevel is changed to INFO, because the information > of completion can be useful to understand that the vanity paths are now fully > available. > Also it would be good to have the total time of this thread being logged. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (SLING-12021) Update to Parent 52
[ https://issues.apache.org/jira/browse/SLING-12021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Sedding closed SLING-12021. -- > Update to Parent 52 > --- > > Key: SLING-12021 > URL: https://issues.apache.org/jira/browse/SLING-12021 > Project: Sling > Issue Type: Task > Components: ResourceResolver >Affects Versions: Resource Resolver 1.10.0 >Reporter: Joerg Hoh >Assignee: Joerg Hoh >Priority: Major > Fix For: Resource Resolver 1.11.0 > > > Right now the ResourceResolver does not build on Java 17. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[RESULT] [VOTE] Release Apache Sling Resource Resolver 1.11.0
Hi, The vote has passed with the following result: +1 (binding): Stefan Seifert, Carsten Ziegeler, Dan Klco, Julian Sedding +1 (non-binding): none I will copy this release to the Sling dist directory and promote the artifacts to the central Maven repository. Regards, Julian
[jira] [Updated] (SLING-11914) Accept initial offset via OffsetMessage
[ https://issues.apache.org/jira/browse/SLING-11914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schneider updated SLING-11914: Fix Version/s: Content Distribution Journal Messages 0.5.2 > Accept initial offset via OffsetMessage > --- > > Key: SLING-11914 > URL: https://issues.apache.org/jira/browse/SLING-11914 > Project: Sling > Issue Type: Improvement > Components: Content Distribution >Reporter: Christian Schneider >Assignee: Christian Schneider >Priority: Major > Fix For: Content Distribution Journal Core 0.2.0, Content > Distribution Journal Messages 0.5.2 > > > When DistributionSubscriber does not yet have a stored offset it is in a > problematic state. > When a package message is sent and DistributionSubscriber starts late or > restarts it might miss the message. > This issue aim to improve the situation by accepting offsets via > OffsetMessage. The messaging provider can send such a message immediately > when the poller is created to inform subscriber about the current offset on > the topic. This offset is then written to repository. > From this point in time the timing problem is solved. No message after the > stored offset can be lost. -- This message was sent by Atlassian Jira (v8.20.10#820010)
DigiCert ONE code signing certificate
Hi Sling developers, I just wanted to let you know that I have renewed your code signing certificate in DigiCert ONE. The current certificate expires on 2023-09-29. The new certificate is valid from now until 2024-09-20. Please update your release process to use the new certificate going forwards. Thanks, Mark
[jira] [Updated] (SLING-11772) Add EventHandler dependency to the DistributionEventNotifier component
[ https://issues.apache.org/jira/browse/SLING-11772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schneider updated SLING-11772: Fix Version/s: Content Distribution Journal Core 0.2.2 (was: Content Distribution Journal Core 0.2.0) > Add EventHandler dependency to the DistributionEventNotifier component > -- > > Key: SLING-11772 > URL: https://issues.apache.org/jira/browse/SLING-11772 > Project: Sling > Issue Type: Improvement > Components: Content Distribution >Affects Versions: Content Distribution Journal Core 0.1.26 >Reporter: José Correia >Priority: Major > Fix For: Content Distribution Journal Core 0.2.2 > > > We should add an _EventHandler_ dependency to the _DistributionEventNotifier_ > in order to make sure that the OSGI components responsible for processing the > event are activated before the event emitter is up and sending events. > > This way we avoid loosing created events. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (SLING-9143) RangePoller is not closed when the cache is closed
[ https://issues.apache.org/jira/browse/SLING-9143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schneider updated SLING-9143: --- Fix Version/s: Content Distribution Journal Core 0.2.2 (was: Content Distribution Journal Core 0.2.0) > RangePoller is not closed when the cache is closed > -- > > Key: SLING-9143 > URL: https://issues.apache.org/jira/browse/SLING-9143 > Project: Sling > Issue Type: Bug > Components: Content Distribution >Affects Versions: Content Distribution Journal Core 0.1.4 >Reporter: Timothee Maret >Assignee: Timothee Maret >Priority: Minor > Fix For: Content Distribution Journal Core 0.2.2 > > > When the PubQueueCache is closed, the underlying head poller (RangePoller) is > not closed. This issue will only manifest when the cache is closed while an > historical page is being fetched. This scenario is more likely when requests > to the journal are being throttled. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (SLING-11607) Emit metric on the time that a package spends in the journal
[
https://issues.apache.org/jira/browse/SLING-11607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Schneider resolved SLING-11607.
-
Resolution: Fixed
> Emit metric on the time that a package spends in the journal
>
>
> Key: SLING-11607
> URL: https://issues.apache.org/jira/browse/SLING-11607
> Project: Sling
> Issue Type: Improvement
> Components: Content Distribution
>Reporter: José Correia
>Assignee: José Correia
>Priority: Major
> Fix For: Content Distribution Journal Core 0.2.0
>
> Original Estimate: 4h
> Remaining Estimate: 4h
>
> We should emit a metric that calculates the time in milliseconds that a
> package spends in the journal.
>
> We already have a metric called {{request_distributed_duration}} that tracks
> the time since a package is enqueued until it is successfully imported.
> However, since this timer includes the import of the package content, we are
> not measuring the latency in the journal.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (SLING-11607) Emit metric on the time that a package spends in the journal
[
https://issues.apache.org/jira/browse/SLING-11607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Schneider updated SLING-11607:
Fix Version/s: Content Distribution Journal Core 0.2.0
(was: Content Distribution Journal Core 0.2.2)
> Emit metric on the time that a package spends in the journal
>
>
> Key: SLING-11607
> URL: https://issues.apache.org/jira/browse/SLING-11607
> Project: Sling
> Issue Type: Improvement
> Components: Content Distribution
>Reporter: José Correia
>Assignee: José Correia
>Priority: Major
> Fix For: Content Distribution Journal Core 0.2.0
>
> Original Estimate: 4h
> Remaining Estimate: 4h
>
> We should emit a metric that calculates the time in milliseconds that a
> package spends in the journal.
>
> We already have a metric called {{request_distributed_duration}} that tracks
> the time since a package is enqueued until it is successfully imported.
> However, since this timer includes the import of the package content, we are
> not measuring the latency in the journal.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (SLING-11607) Emit metric on the time that a package spends in the journal
[
https://issues.apache.org/jira/browse/SLING-11607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Schneider updated SLING-11607:
Fix Version/s: Content Distribution Journal Core 0.2.2
(was: Content Distribution Journal Core 0.2.0)
> Emit metric on the time that a package spends in the journal
>
>
> Key: SLING-11607
> URL: https://issues.apache.org/jira/browse/SLING-11607
> Project: Sling
> Issue Type: Improvement
> Components: Content Distribution
>Reporter: José Correia
>Assignee: José Correia
>Priority: Major
> Fix For: Content Distribution Journal Core 0.2.2
>
> Original Estimate: 4h
> Remaining Estimate: 4h
>
> We should emit a metric that calculates the time in milliseconds that a
> package spends in the journal.
>
> We already have a metric called {{request_distributed_duration}} that tracks
> the time since a package is enqueued until it is successfully imported.
> However, since this timer includes the import of the package content, we are
> not measuring the latency in the journal.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (SLING-10614) Document package limits
[ https://issues.apache.org/jira/browse/SLING-10614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schneider updated SLING-10614: Fix Version/s: Content Distribution Journal Core 0.2.2 (was: Content Distribution Journal Core 0.2.0) > Document package limits > --- > > Key: SLING-10614 > URL: https://issues.apache.org/jira/browse/SLING-10614 > Project: Sling > Issue Type: Task > Components: Content Distribution >Reporter: Timothee Maret >Priority: Major > Fix For: Content Distribution Journal Core 0.2.2 > > > With SLING-10528 we started rejecting packages bigger than 5MB. We should > document this limitation and provide strategies to avoid the limit. > The strategy is to use multi paths distribution requests instead of deep > distributing a single path. Limit to max 100 hierarchical node paths per > distribution request. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (SLING-9403) Filter status messages by subscriber agent
[ https://issues.apache.org/jira/browse/SLING-9403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schneider resolved SLING-9403. Resolution: Fixed I think we already filter the status messages by subscriber agent. > Filter status messages by subscriber agent > -- > > Key: SLING-9403 > URL: https://issues.apache.org/jira/browse/SLING-9403 > Project: Sling > Issue Type: Bug > Components: Content Distribution >Reporter: Timothee Maret >Assignee: Timothee Maret >Priority: Major > Fix For: Content Distribution Journal Core 0.2.0 > > > Status messages are emit by editable subscriber agents. Multiple editable > agents may exist at the same time, e.g. when replacing services using a > rolling update strategy. Different editable agents may evolve differently and > thus the status messages are not interchangeable. > This issue tracks > 1. Identifying the subscriber agent producing the status messages > 2. Extending the staging precondition to filter by subscriber agent -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (SLING-9321) Update to declarative services 1.4
[ https://issues.apache.org/jira/browse/SLING-9321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schneider resolved SLING-9321. Resolution: Fixed > Update to declarative services 1.4 > -- > > Key: SLING-9321 > URL: https://issues.apache.org/jira/browse/SLING-9321 > Project: Sling > Issue Type: Bug > Components: Content Distribution >Affects Versions: Content Distribution Journal Core 0.1.10 >Reporter: Christian Schneider >Assignee: Christian Schneider >Priority: Major > Fix For: Content Distribution Journal Core 0.2.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (SLING-9078) Keep skipped offsets in memory
[
https://issues.apache.org/jira/browse/SLING-9078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Schneider reassigned SLING-9078:
--
Assignee: (was: Christian Schneider)
> Keep skipped offsets in memory
> --
>
> Key: SLING-9078
> URL: https://issues.apache.org/jira/browse/SLING-9078
> Project: Sling
> Issue Type: Improvement
> Components: Content Distribution
>Affects Versions: Content Distribution Journal Core 0.1.8
>Reporter: Timothee Maret
>Priority: Major
> Fix For: Content Distribution Journal Core 0.2.2
>
>
> In SLING-8908 we introduced a mechanism to keep track of skipped packages
> such that in case of journal availability flip flop, the agents would still
> progress. The implementation was done by persisting the offset in the
> repository. In environments where many skipped packages will occur (e.g.
> large customer with multiple agents) then those commits will start to
> generate a non negligible load on the repository, consuming resources and
> creating bottlenecks.
>
> A first mitigation to this issue has been added in SLING-8965, however for
> very large customers the mitigation will not be effective. Increasing the
> grouping of skipped packages (e.g. 1/100 instead of 1/10) reduce the load on
> the repository but may fail to ensure progress in case of flip/flop.
>
> Instead of storing the skipped packages in the repository, we should keep
> them in memory. A new service that does not reference the
> {{JournalAvailable}} service could be added. The offsets would be
> consolidated on demand from the stored offsets and those stored in memory.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (SLING-9078) Keep skipped offsets in memory
[
https://issues.apache.org/jira/browse/SLING-9078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Schneider updated SLING-9078:
---
Fix Version/s: Content Distribution Journal Core 0.2.2
(was: Content Distribution Journal Core 0.2.0)
> Keep skipped offsets in memory
> --
>
> Key: SLING-9078
> URL: https://issues.apache.org/jira/browse/SLING-9078
> Project: Sling
> Issue Type: Improvement
> Components: Content Distribution
>Affects Versions: Content Distribution Journal Core 0.1.8
>Reporter: Timothee Maret
>Assignee: Christian Schneider
>Priority: Major
> Fix For: Content Distribution Journal Core 0.2.2
>
>
> In SLING-8908 we introduced a mechanism to keep track of skipped packages
> such that in case of journal availability flip flop, the agents would still
> progress. The implementation was done by persisting the offset in the
> repository. In environments where many skipped packages will occur (e.g.
> large customer with multiple agents) then those commits will start to
> generate a non negligible load on the repository, consuming resources and
> creating bottlenecks.
>
> A first mitigation to this issue has been added in SLING-8965, however for
> very large customers the mitigation will not be effective. Increasing the
> grouping of skipped packages (e.g. 1/100 instead of 1/10) reduce the load on
> the repository but may fail to ensure progress in case of flip/flop.
>
> Instead of storing the skipped packages in the repository, we should keep
> them in memory. A new service that does not reference the
> {{JournalAvailable}} service could be added. The offsets would be
> consolidated on demand from the stored offsets and those stored in memory.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (SLING-9065) Incorrect error handling for content distribution if binary is not present in blob store
[ https://issues.apache.org/jira/browse/SLING-9065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schneider updated SLING-9065: --- Fix Version/s: Content Distribution Journal Core 0.2.2 (was: Content Distribution Journal Core 0.2.0) > Incorrect error handling for content distribution if binary is not present in > blob store > > > Key: SLING-9065 > URL: https://issues.apache.org/jira/browse/SLING-9065 > Project: Sling > Issue Type: Bug > Components: Content Distribution >Affects Versions: Content Distribution Journal Core 0.1.6 >Reporter: Christian Schneider >Assignee: Christian Schneider >Priority: Major > Fix For: Content Distribution Journal Core 0.2.2 > > > We did a content distribution and the publisher used a different blob store. > So the reference to the binary could not be resolved. > We get a stack trace like below but the ui just shows the queue as running > with 0 retries. So it seems the error is not handled correctly. > [https://gist.github.com/cschneider/c663fa7912b4e643c9d761aa8b70906f] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (SLING-11990) Fix TEST distribution requests
[ https://issues.apache.org/jira/browse/SLING-11990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schneider updated SLING-11990: Fix Version/s: Content Distribution Journal Core 0.2.0 > Fix TEST distribution requests > -- > > Key: SLING-11990 > URL: https://issues.apache.org/jira/browse/SLING-11990 > Project: Sling > Issue Type: Bug > Components: Content Distribution >Reporter: Christian Schneider >Assignee: Christian Schneider >Priority: Major > Fix For: Content Distribution Journal Core 0.2.0 > > > Currently test requests do not work as they do not have a path. > So they fail with exception saying "Empty paths". > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (SLING-11560) Vault error when importing a node with the same name and UUID as a pre-existing non-sibling node
[
https://issues.apache.org/jira/browse/SLING-11560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Schneider updated SLING-11560:
Fix Version/s: Content Distribution Journal Core 0.2.0
> Vault error when importing a node with the same name and UUID as a
> pre-existing non-sibling node
>
>
> Key: SLING-11560
> URL: https://issues.apache.org/jira/browse/SLING-11560
> Project: Sling
> Issue Type: Bug
> Components: Content Distribution
>Reporter: Manas Kumar Maji
>Assignee: Timothee Maret
>Priority: Major
> Fix For: Content Distribution Core 0.6.0, Content Distribution
> Core 0.4.6, Content Distribution Journal Core 0.2.0
>
> Time Spent: 4h 50m
> Remaining Estimate: 0h
>
> The latest version of _org.apache.jackrabbit.vault_
> (_3.6.1.T20220805092633-0b8a2641_) is throwing an exception when trying to
> install a content package (via SCD), which has a node with the same name and
> UUID as an existing non-sibling node.
> {noformat}
> Caused by: javax.jcr.ReferentialIntegrityException: Node identifier
> Optional[df89c4d9-6d47-480a-af2d-1bffa49bc5d1] already taken by node
> /content/dam/test/SYEW0105.JPG
> at
> org.apache.jackrabbit.vault.fs.impl.io.DocViewImporter.addNode(DocViewImporter.java:862)
> [org.apache.jackrabbit.vault:3.6.1.T20220805092633-0b8a2641]
> at
> org.apache.jackrabbit.vault.fs.impl.io.DocViewImporter.startDocViewNode(DocViewImporter.java:405)
> [org.apache.jackrabbit.vault:3.6.1.T20220805092633-0b8a2641]
> at
> org.apache.jackrabbit.vault.fs.impl.io.DocViewSAXHandler.startElement(DocViewSAXHandler.java:348)
> [org.apache.jackrabbit.vault:3.6.1.T20220805092633-0b8a2641]
> {noformat}
> *Older Behaviour:* In the older version of jackrabbit vault (3.4.6), an new
> UUID would be created for the new node:
> {noformat}
> 17.08.2022 17:37:00.739 *WARN* [qtp1778855870-1811]
> org.apache.jackrabbit.vault.fs.impl.io.DocViewSAXImporter Packaged node at
> /content/dam/hunting/SYEW0105.JPG is referenceable and collides with existing
> node at /content/dam/test/SYEW0105.JPG. Will create new UUID.
> {noformat}
> *Current Behaviour:* From the AEM author logs, it seems that the OSGi config
> having the _IdConflictPolicy.LEGACY_ is not being respected by SCD:
> {noformat}
> 24.08.2022 15:10:45.799 *WARN* [qtp1859723769-86]
> org.apache.jackrabbit.vault.fs.impl.io.DocViewImporter Node Collision: To-be
> imported node /content/dam/hunting/SYEW0105.JPG uses a node identifier
> Optional[df89c4d9-6d47-480a-af2d-1bffa49bc5d1] which is already taken by
> /content/dam/test/SYEW0105.JPG, trying to resolve conflict according to
> policy FAIL
> {noformat}
> *Expected Behaviour:* SCD should take the _IdConflictPolicy_ into
> consideration when installing the content packages. So if
> _IdConflictPolicy.LEGACY_ is set, then a new UUID should be generated for the
> new node.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (SLING-11914) Accept initial offset via OffsetMessage
[ https://issues.apache.org/jira/browse/SLING-11914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schneider updated SLING-11914: Fix Version/s: Content Distribution Journal Core 0.2.0 > Accept initial offset via OffsetMessage > --- > > Key: SLING-11914 > URL: https://issues.apache.org/jira/browse/SLING-11914 > Project: Sling > Issue Type: Improvement > Components: Content Distribution >Reporter: Christian Schneider >Assignee: Christian Schneider >Priority: Major > Fix For: Content Distribution Journal Core 0.2.0 > > > When DistributionSubscriber does not yet have a stored offset it is in a > problematic state. > When a package message is sent and DistributionSubscriber starts late or > restarts it might miss the message. > This issue aim to improve the situation by accepting offsets via > OffsetMessage. The messaging provider can send such a message immediately > when the poller is created to inform subscriber about the current offset on > the topic. This offset is then written to repository. > From this point in time the timing problem is solved. No message after the > stored offset can be lost. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[Jenkins] Sling » Modules » sling-org-apache-sling-starter » master #1028 is BROKEN
) [INFO] Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-plugin-registry/2.2.1/maven-plugin-registry-2.2.1.jar [INFO] Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-model/2.2.1/maven-model-2.2.1.jar (88 kB at 942 kB/s) [INFO] Downloading from central: https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-interpolation/1.11/plexus-interpolation-1.11.jar [INFO] Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-settings/2.2.1/maven-settings-2.2.1.jar (49 kB at 481 kB/s) [INFO] Downloading from central: https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-component-annotations/2.1.0/plexus-component-annotations-2.1.0.jar [INFO] Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-project/2.2.1/maven-project-2.2.1.jar (156 kB at 1.4 MB/s) [INFO] Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-plugin-api/2.2.1/maven-plugin-api-2.2.1.jar [INFO] Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-profile/2.2.1/maven-profile-2.2.1.jar (35 kB at 313 kB/s) [INFO] Downloading from central: https://repo.maven.apache.org/maven2/org/apache/commons/commons-lang3/3.5/commons-lang3-3.5.jar [INFO] Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-plugin-registry/2.2.1/maven-plugin-registry-2.2.1.jar (30 kB at 258 kB/s) [INFO] Downloaded from central: https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-interpolation/1.11/plexus-interpolation-1.11.jar (51 kB at 411 kB/s) [INFO] Downloaded from central: https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-component-annotations/2.1.0/plexus-component-annotations-2.1.0.jar (4.2 kB at 32 kB/s) [INFO] Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-plugin-api/2.2.1/maven-plugin-api-2.2.1.jar (12 kB at 88 kB/s) [INFO] Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/commons/commons-lang3/3.5/commons-lang3-3.5.jar (480 kB at 2.6 MB/s) [INFO] Enabled default license matchers. [INFO] Will parse SCM ignores for exclusions... [INFO] Parsing exclusions from /home/jenkins/workspace/_org-apache-sling-starter_master/jdk_11_latest/.gitignore [INFO] Finished adding exclusions from SCM ignore files. [INFO] 79 implicit excludes. [INFO] 15 explicit excludes. [INFO] 21 resources included [INFO] Rat check: Summary over all files. Unapproved: 0, unknown: 0, generated: 0, approved: 20 licenses. [INFO] [INFO] --- jacoco:0.8.10:report (report) @ org.apache.sling.starter --- [INFO] Skipping JaCoCo execution due to missing execution data file. [INFO] [INFO] --- jacoco:0.8.10:report-integration (report-integration) @ org.apache.sling.starter --- [INFO] Loading execution data file /home/jenkins/workspace/_org-apache-sling-starter_master/jdk_11_latest/target/jacoco-it.exec [INFO] Analyzed bundle 'Apache Sling Starter' with 0 classes [INFO] [INFO] --- jacoco:0.8.10:report (report-merged) @ org.apache.sling.starter --- [INFO] Loading execution data file /home/jenkins/workspace/_org-apache-sling-starter_master/jdk_11_latest/target/jacoco-merged.exec [INFO] Analyzed bundle 'Apache Sling Starter' with 0 classes [INFO] [INFO] --- docker:0.43.4:stop (stop-mongo) @ org.apache.sling.starter --- [INFO] DOCKER> [mongo:4.4.6] "mongo": Stop and removed container 905de4e29637 after 0 ms [INFO] [INFO] --- failsafe:3.0.0-M5:verify (default) @ org.apache.sling.starter --- [INFO] Failsafe report directory: /home/jenkins/workspace/_org-apache-sling-starter_master/jdk_11_latest/target/failsafe-reports [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 08:33 min [INFO] Finished at: 2023-09-21T11:26:52Z [INFO] [INFO] [jenkins-event-spy] Generated /home/jenkins/workspace/_org-apache-sling-starter_master/jdk_11_latest@tmp/withMaven30a85f23/maven-spy-20230921-111818-17616676030919702893652.log [ERROR] Failed to execute goal org.apache.maven.plugins:maven-failsafe-plugin:3.0.0-M5:verify (default) on project org.apache.sling.starter: There are test failures. [ERROR] [ERROR] Please refer to /home/jenkins/workspace/_org-apache-sling-starter_master/jdk_11_latest/target/failsafe-reports for the individual test results. [ERROR] Please refer to dump files (if any exist) [date].dump, [date]-jvmRun[N].dump and [date].dumpstream. [ERROR] -> [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-failsafe-plugin:3.0.0-M5:verify (default) on project org.apache.sling.starter: There are test failures. Please refer to /home/jenkins/worksp
Re: Simpler Feature flags for sling
On Thu, 2023-09-21 at 11:06 +0200, Robert Munteanu wrote: > On Thu, 2023-09-21 at 09:07 +0200, Christian Schneider wrote: > > He proposed a nice alternative to simply use "toggle.FT-SLING-1234" > > scheme > > for the Condition ids. > > I think I am still missing context, sorry for being dense :-) > > What does using the toggle mean for a Sling module? I am not sure if > and how we need to explicitly add these conditions to the source > code. Christian and I had a brief chat and I think I get it know :-) There are two main ways of using OSGi Conditions 1. as a condition for activating OSGi DS components 2. as an optional service reference for OSGi DS components The first one can be done declaratively but both work programatically, i.e. declare a reference and check at runtime if the condition is present. I personally think that this is fine, given that we document this usage clearly and we have a proper naming convention for it (Christian already proposed one). We should also clarify the relation between using 'toggle conditions' and the existing feature flags module [1][2]. Christian, please fill in anything that I might've missed. Thanks, Robert [1]: https://github.com/apache/sling-org-apache-sling-featureflags [2]: https://sling.apache.org/documentation/the-sling-engine/featureflags.html
Re: [VOTE] Release Apache Sling Resource Resolver 1.11.0
+1 Regards Julian On Mon, Sep 18, 2023 at 10:49 PM Daniel Klco wrote: > > +1 > > On Mon, Sep 18, 2023 at 11:12 AM Carsten Ziegeler > wrote: > > > +1 > > > > Carsten > > > > On 18.09.2023 16:11, Julian Sedding wrote: > > > Hi, > > > > > > We solved 14 issues in this release: > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310710&version=12352186&styleName=Text > > > > > > Staging repository: > > > https://repository.apache.org/content/repositories/orgapachesling-2782/ > > > > > > You can use this UNIX script to download the release and verify the > > signatures: > > > > > https://raw.githubusercontent.com/apache/sling-tooling-release/master/check_staged_release.sh > > > > > > Usage: > > > sh check_staged_release.sh 2782 /tmp/sling-staging > > > > > > Please vote to approve this release: > > > > > >[ ] +1 Approve the release > > >[ ] 0 Don't care > > >[ ] -1 Don't release, because ... > > > > > > This majority vote is open for at least 72 hours. > > > > > > Regards, > > > Julian > > > > -- > > Carsten Ziegeler > > Adobe > > cziege...@apache.org > >
Re: Simpler Feature flags for sling
On Thu, 2023-09-21 at 09:07 +0200, Christian Schneider wrote: > He proposed a nice alternative to simply use "toggle.FT-SLING-1234" > scheme > for the Condition ids. I think I am still missing context, sorry for being dense :-) What does using the toggle mean for a Sling module? I am not sure if and how we need to explicitly add these conditions to the source code. Thanks, Robert
[jira] [Commented] (SLING-12035) bump oak dependency for compatibility with oak version 1.56.0
[ https://issues.apache.org/jira/browse/SLING-12035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17767469#comment-17767469 ] Robert Munteanu commented on SLING-12035: - Would it make sense to bump the bundle version to 1.4.0 after this change is applied? > bump oak dependency for compatibility with oak version 1.56.0 > - > > Key: SLING-12035 > URL: https://issues.apache.org/jira/browse/SLING-12035 > Project: Sling > Issue Type: Improvement >Reporter: Eric Norman >Assignee: Eric Norman >Priority: Major > Fix For: JCR Oak Server 1.3.2 > > > In order for sling to work with the latest release of oak, the oak > dependencies must be bumped to 1.56.0 or later. > The oak 1.56.0 release completed the removal of the dependency on the old > guava library which required a bump of the major version of some exported > packages whose public api has changed. The imports of those changed packages > must be bumped to the new major version number in order for the bundles to > resolve properly in the runtime. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [sling-org-apache-sling-feature-extension-content] rombert merged pull request #22: SLING-12032 - Slf4j classes included and not relocated in the final jar
rombert merged PR #22: URL: https://github.com/apache/sling-org-apache-sling-feature-extension-content/pull/22 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: Simpler Feature flags for sling
I spoke to Carsten about how to have feature flags for closed as well as open source OSGi projects. He proposed a nice alternative to simply use "toggle.FT-SLING-1234" scheme for the Condition ids. This would work universally if all our OSGi projects (Oak, Sling, Felix) can agree on it. What do you think? Christian Am Di., 19. Sept. 2023 um 13:52 Uhr schrieb Robert Munteanu < romb...@apache.org>: > Hi Christian, > > On Mon, 2023-09-18 at 16:57 +0200, Christian Schneider wrote: > > I propose that we expose feature toggles using a prefix + the toggle > > name. > > So for example it could be "org.apache.sling.toggle.FT-SLING-1234". > > > > I have already experimented with this and it seems feasible. > > This looks like a good idea but I'm missing the concrete change you > propose for Sling :-) > > Thanks, > Robert > -- -- Christian Schneider http://www.liquid-reality.de Computer Scientist http://www.adobe.com
