[GitHub] [sling-org-apache-sling-jcr-jackrabbit-accessmanager] sonarcloud[bot] commented on pull request #8: SLING-11272 support for get, modify and delete of a principalbased ACE
sonarcloud[bot] commented on PR #8: URL: https://github.com/apache/sling-org-apache-sling-jcr-jackrabbit-accessmanager/pull/8#issuecomment-1110435931 Kudos, SonarCloud Quality Gate passed! [](https://sonarcloud.io/dashboard?id=apache_sling-org-apache-sling-jcr-jackrabbit-accessmanager&pullRequest=8) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jcr-jackrabbit-accessmanager&pullRequest=8&resolved=false&types=BUG) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jcr-jackrabbit-accessmanager&pullRequest=8&resolved=false&types=BUG) [0 Bugs](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jcr-jackrabbit-accessmanager&pullRequest=8&resolved=false&types=BUG) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jcr-jackrabbit-accessmanager&pullRequest=8&resolved=false&types=VULNERABILITY) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jcr-jackrabbit-accessmanager&pullRequest=8&resolved=false&types=VULNERABILITY) [0 Vulnerabilities](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jcr-jackrabbit-accessmanager&pullRequest=8&resolved=false&types=VULNERABILITY) [](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-jcr-jackrabbit-accessmanager&pullRequest=8&resolved=false&types=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-jcr-jackrabbit-accessmanager&pullRequest=8&resolved=false&types=SECURITY_HOTSPOT) [0 Security Hotspots](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-jcr-jackrabbit-accessmanager&pullRequest=8&resolved=false&types=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jcr-jackrabbit-accessmanager&pullRequest=8&resolved=false&types=CODE_SMELL) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jcr-jackrabbit-accessmanager&pullRequest=8&resolved=false&types=CODE_SMELL) [2 Code Smells](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jcr-jackrabbit-accessmanager&pullRequest=8&resolved=false&types=CODE_SMELL) [](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-jcr-jackrabbit-accessmanager&pullRequest=8&metric=new_coverage&view=list) [91.4% Coverage](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-jcr-jackrabbit-accessmanager&pullRequest=8&metric=new_coverage&view=list) [](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-jcr-jackrabbit-accessmanager&pullRequest=8&metric=new_duplicated_lines_density&view=list) [0.0% Duplication](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-jcr-jackrabbit-accessmanager&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
Re: [VOTE] Release Apache Sling Content Distribution API 0.7.0
Good catch, thank you! Included the issue. Regards, Timothee Le mar. 26 avr. 2022 à 14:10, Stefan Seifert a écrit : > +1 > > please note: there is also a commit for SLING-9389 in this release, should > be added to the changelog > > stefan > > > >-Original Message- > >From: Timothee Maret > >Sent: Tuesday, April 26, 2022 12:20 PM > >To: dev@sling.apache.org > >Subject: [VOTE] Release Apache Sling Content Distribution API 0.7.0 > > > >Hi, > > > >We solved 1 issues in this release: > >https://issues.apache.org/jira/projects/SLING/versions/12351368 > > > >Staging repository: > >https://repository.apache.org/content/repositories/orgapachesling-2626/ > > > >You can use this UNIX script to download the release and verify the > >signatures: > >https://gitbox.apache.org/repos/asf?p=sling-tooling- > >release.git;a=blob;f=check_staged_release.sh;hb=HEAD > > > >Usage: > >sh check_staged_release.sh 2626 /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. >
[jira] [Resolved] (SLING-9389) Distribution Event Packages should contain queue item creation time
[ https://issues.apache.org/jira/browse/SLING-9389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothee Maret resolved SLING-9389. --- Resolution: Fixed > Distribution Event Packages should contain queue item creation time > --- > > Key: SLING-9389 > URL: https://issues.apache.org/jira/browse/SLING-9389 > Project: Sling > Issue Type: Improvement > Components: Content Distribution >Reporter: Harsh Chiki >Assignee: Timothee Maret >Priority: Major > Fix For: Content Distribution Journal Core 0.1.26 > > Attachments: image-2020-04-30-10-28-58-011.png, scdapi.patch, > scdcore.patch > > Time Spent: 2h 10m > Remaining Estimate: 0h > > Currently the Distribution Event package contains the following details: > * Distribution Component Name > * Distribution Component Kind > * Distribution Type > * Distribution Paths > > Improvement aims at adding the queue item creation time, essentially when the > the item was creation for the first time, and enqueue into the queue. The > value does not change over retries (on failure). > > The purpose to get this detail is to be able to capture metrics at the > consumer level. The consumers could have an event handler, which can capture > the duration which turns out to be (NOW MINUS queue item creation time thrown > in the distribution event package); NOW being the current time in the event > handler (consumer). > > \cc: [~shgu...@adobe.com], [~ashishc] -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (SLING-9389) Distribution Event Packages should contain queue item creation time
[ https://issues.apache.org/jira/browse/SLING-9389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothee Maret updated SLING-9389: -- Fix Version/s: Content Distribution Journal Core 0.1.26 (was: Content Distribution Journal Core 0.1.28) > Distribution Event Packages should contain queue item creation time > --- > > Key: SLING-9389 > URL: https://issues.apache.org/jira/browse/SLING-9389 > Project: Sling > Issue Type: Improvement > Components: Content Distribution >Reporter: Harsh Chiki >Assignee: Timothee Maret >Priority: Major > Fix For: Content Distribution Journal Core 0.1.26 > > Attachments: image-2020-04-30-10-28-58-011.png, scdapi.patch, > scdcore.patch > > Time Spent: 2h 10m > Remaining Estimate: 0h > > Currently the Distribution Event package contains the following details: > * Distribution Component Name > * Distribution Component Kind > * Distribution Type > * Distribution Paths > > Improvement aims at adding the queue item creation time, essentially when the > the item was creation for the first time, and enqueue into the queue. The > value does not change over retries (on failure). > > The purpose to get this detail is to be able to capture metrics at the > consumer level. The consumers could have an event handler, which can capture > the duration which turns out to be (NOW MINUS queue item creation time thrown > in the distribution event package); NOW being the current time in the event > handler (consumer). > > \cc: [~shgu...@adobe.com], [~ashishc] -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (SLING-9389) Distribution Event Packages should contain queue item creation time
[ https://issues.apache.org/jira/browse/SLING-9389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothee Maret updated SLING-9389: -- Fix Version/s: Content Distribution Journal Core 0.1.28 > Distribution Event Packages should contain queue item creation time > --- > > Key: SLING-9389 > URL: https://issues.apache.org/jira/browse/SLING-9389 > Project: Sling > Issue Type: Improvement > Components: Content Distribution >Reporter: Harsh Chiki >Assignee: Timothee Maret >Priority: Major > Fix For: Content Distribution Journal Core 0.1.28 > > Attachments: image-2020-04-30-10-28-58-011.png, scdapi.patch, > scdcore.patch > > Time Spent: 2h 10m > Remaining Estimate: 0h > > Currently the Distribution Event package contains the following details: > * Distribution Component Name > * Distribution Component Kind > * Distribution Type > * Distribution Paths > > Improvement aims at adding the queue item creation time, essentially when the > the item was creation for the first time, and enqueue into the queue. The > value does not change over retries (on failure). > > The purpose to get this detail is to be able to capture metrics at the > consumer level. The consumers could have an event handler, which can capture > the duration which turns out to be (NOW MINUS queue item creation time thrown > in the distribution event package); NOW being the current time in the event > handler (consumer). > > \cc: [~shgu...@adobe.com], [~ashishc] -- This message was sent by Atlassian Jira (v8.20.7#820007)
[GitHub] [sling-org-apache-sling-xss] sonarcloud[bot] commented on pull request #19: Bump antisamy from 1.6.4 to 1.6.7
sonarcloud[bot] commented on PR #19: URL: https://github.com/apache/sling-org-apache-sling-xss/pull/19#issuecomment-111049 Kudos, SonarCloud Quality Gate passed! [](https://sonarcloud.io/dashboard?id=apache_sling-org-apache-sling-xss&pullRequest=19) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-xss&pullRequest=19&resolved=false&types=BUG) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-xss&pullRequest=19&resolved=false&types=BUG) [0 Bugs](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-xss&pullRequest=19&resolved=false&types=BUG) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-xss&pullRequest=19&resolved=false&types=VULNERABILITY) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-xss&pullRequest=19&resolved=false&types=VULNERABILITY) [0 Vulnerabilities](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-xss&pullRequest=19&resolved=false&types=VULNERABILITY) [](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-xss&pullRequest=19&resolved=false&types=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-xss&pullRequest=19&resolved=false&types=SECURITY_HOTSPOT) [0 Security Hotspots](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-xss&pullRequest=19&resolved=false&types=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-xss&pullRequest=19&resolved=false&types=CODE_SMELL) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-xss&pullRequest=19&resolved=false&types=CODE_SMELL) [0 Code Smells](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-xss&pullRequest=19&resolved=false&types=CODE_SMELL) [](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-xss&pullRequest=19&metric=coverage&view=list) No Coverage information [](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-xss&pullRequest=19&metric=new_duplicated_lines_density&view=list) [0.0% Duplication](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-xss&pullRequest=19&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-xss] dependabot[bot] opened a new pull request, #19: Bump antisamy from 1.6.4 to 1.6.7
dependabot[bot] opened a new pull request, #19: URL: https://github.com/apache/sling-org-apache-sling-xss/pull/19 Bumps [antisamy](https://github.com/nahsra/antisamy) from 1.6.4 to 1.6.7. Release notes Sourced from https://github.com/nahsra/antisamy/releases";>antisamy's releases. Release version 1.6.7 This release addresses a minor issue in the security fixes implemented in 1.6.6. While those fixes addressed most of the security concerns in the security issue reported to us by the researcher, our fix had a minor bug that allowed something to sneak through. This release fixes that, and includes the changes from 1.6.6.1 that compile AntiSamy.jar to Java 7 bytecode. Release version 1.6.6.1 The 1.6.6.1 release corrects a minor issue in the 1.6.6 release: We accidentally upgraded the byte code generated for antisamy.jar to be Java 8, when it can still be Java 7. So this release generates a Java 7 jar file instead. This allows Java 7 projects to use AntiSamy 1.6.6.1 by doing the following: Exclude the 2 Java 8 dependencies we currently use: commons-o:commons-io:2.11.0 net.sourceforge.htmlunit:neko-htmlunit:2.60.0 You then import and use the last Java 7 versions of these libraries: commons-io:commons-io:2.6 net.sourceforge.htmlunit:neko-htmlunit:2.24 A few plugins were upgraded and some were added but none of the dependencies were changed. The previous 1.6.6 release addressed the following issues: This release fixes 3 security issues reported by researcher Hyeongkwan Lee CVEs for these have not been created yet, so we are not providing any details on the issues at this time. Enhancement https://github-redirect.dependabot.com/nahsra/antisamy/issues/147";>#147: Add require-closing-tags to default AntiSamy policy file Bug https://github-redirect.dependabot.com/nahsra/antisamy/issues/151";>#151: Change in behavior between 1.6.4 and 1.6.5 for getErrorMessages We accidentally stopped propagating an errorMessages parameter in 1 API. This is now fixed. NOTIFICATION 1: This 1.6.6 release has 2 dependencies which require Java 8, although the AntiSamy source code itself still only requires Java 7. NOTIFICATION 2: The 1.7.0 release will drop support for several things deprecated in the 1.6.x series of releases. a) AntiSamy 1.6.0 introduced XML schema validation for AntiSamy policy files to address issue https://github-redirect.dependabot.com/nahsra/antisamy/issues/58";>#58. In all the 1.6.X releases, enforcement of schema validation is optional, with warnings generated to indicate it should be enforced. Starting with AntiSamy 1.7.0 this will no longer be optional. To support this new feature, but keep it optional, 2 new Policy class methods were created, and immediately deprecated: public static boolean getSchemaValidation() public static void setSchemaValidation(boolean enable) These two methods will be dropped in the 1.7.0 release, and any AntiSamy policy files that fail schema validation will result in an error and have to be fixed. b) AntiSamy 1.6.5 changed some APIs. Specifically: These constructors are now https://github.com/Deprecated";>@Deprecated: public CssHandler(Policy policy, LinkedList embeddedStyleSheets, List errorMessages, ResourceBundle messages) ... (truncated) Commits https://github.com/nahsra/antisamy/commit/a42865ce3956c0e1c8c1993533209d825ff9a19b";>a42865c Merge pull request https://github-redirect.dependabot.com/nahsra/antisamy/issues/168";>#168 from nahsra/1.6.7 https://github.com/nahsra/antisamy/commit/a0ec25d2ec70b794e6a78f6251c21735696ea832";>a0ec25d Update pom to reflect 1.6.7 release. https://github.com/nahsra/antisamy/commit/32e273507da0e964b58c50fd8a4c94c9d9363af0";>32e2735 Fix child node removal on style tag processing https://github.com/nahsra/antisamy/commit/b6e76de85a07549f2c97941437dd73430d7287a8";>b6e76de Update pom.xml so it builds Java 7 bytecode instead of Java 8, which https://github.com/nahsra/antisamy/commit/99b1143bd2219c7645a8d68ca856a51e67f7bbfa";>99b1143 Mention new security issues fixed in 1.6.6 release. https://github.com/nahsra/antisamy/commit/5d58ffa4fbdd59fee42a81478bdd3f27fbe84cab";>5d58ffa Fix 2 issues reported by SpotBugs in new code for this release. Fix two https://github.com/nahsra/antisamy/commit/5bf2038ea6de6eeb2dd7ae143faa89d85b2853e7";>5bf2038 Merge pull request https://github-redirect.dependabot.com/nahsra/antisamy/issues/162";>#162 from nahsra/1.6.6 https://github.com/nahsra/antisamy/commit/513c02d6afd85714688fd949bce827b7ca401198";>513c02d Add CssScannerTest class https://github.com/nahsra/antisamy/commit/a6d1dd80f0867002060e33c809c8c9289daa7176";>a6d1dd8 Add setConnectTimeout back in CssScanner https://github.com/nahsra/antisamy/commit/eaa10c65ef9d3b118b9ba7465d845bb834684612";>eaa10c6 Merge pull request https://
[GitHub] [sling-org-apache-sling-scripting-jsp-taglib] rombert commented on pull request #3: Upgrade to sling47 and some test dependencies
rombert commented on PR #3: URL: https://github.com/apache/sling-org-apache-sling-scripting-jsp-taglib/pull/3#issuecomment-1109947702 BTW, I have created an issue for this PR - SLING-11283. Please use "SLING-11283 - Scripting JSP taglib: update to parent 47" as the commit title. -- 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] [Resolved] (SLING-11282) Testing Email: update to parent 47
[ https://issues.apache.org/jira/browse/SLING-11282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu resolved SLING-11282. - Assignee: Robert Munteanu Resolution: Fixed Fixed by [~ashokmc...@gmail.com] in https://github.com/apache/sling-org-apache-sling-testing-email/pull/1 . > Testing Email: update to parent 47 > -- > > Key: SLING-11282 > URL: https://issues.apache.org/jira/browse/SLING-11282 > Project: Sling > Issue Type: Sub-task >Reporter: Robert Munteanu >Assignee: Robert Munteanu >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Resolved] (SLING-11281) Testing Hamcrest: update to parent 47
[ https://issues.apache.org/jira/browse/SLING-11281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu resolved SLING-11281. - Resolution: Fixed Fixed by [~ashokmc...@gmail.com] in https://github.com/apache/sling-org-apache-sling-testing-hamcrest/pull/1 . > Testing Hamcrest: update to parent 47 > - > > Key: SLING-11281 > URL: https://issues.apache.org/jira/browse/SLING-11281 > Project: Sling > Issue Type: Sub-task >Reporter: Robert Munteanu >Assignee: Robert Munteanu >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Assigned] (SLING-11283) Scripting JSP taglib: update to parent 47
[ https://issues.apache.org/jira/browse/SLING-11283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu reassigned SLING-11283: --- Assignee: Robert Munteanu > Scripting JSP taglib: update to parent 47 > - > > Key: SLING-11283 > URL: https://issues.apache.org/jira/browse/SLING-11283 > Project: Sling > Issue Type: Sub-task >Reporter: Robert Munteanu >Assignee: Robert Munteanu >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (SLING-11282) Testing Email: update to parent 47
Robert Munteanu created SLING-11282: --- Summary: Testing Email: update to parent 47 Key: SLING-11282 URL: https://issues.apache.org/jira/browse/SLING-11282 Project: Sling Issue Type: Sub-task Reporter: Robert Munteanu -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (SLING-11281) Testing Hamcrest: update to parent 47
Robert Munteanu created SLING-11281: --- Summary: Testing Hamcrest: update to parent 47 Key: SLING-11281 URL: https://issues.apache.org/jira/browse/SLING-11281 Project: Sling Issue Type: Sub-task Reporter: Robert Munteanu Assignee: Robert Munteanu -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (SLING-11283) Scripting JSP taglib: update to parent 47
Robert Munteanu created SLING-11283: --- Summary: Scripting JSP taglib: update to parent 47 Key: SLING-11283 URL: https://issues.apache.org/jira/browse/SLING-11283 Project: Sling Issue Type: Sub-task Reporter: Robert Munteanu -- This message was sent by Atlassian Jira (v8.20.7#820007)
[GitHub] [sling-org-apache-sling-testing-email] rombert commented on pull request #1: Upgrade to sling47
rombert commented on PR #1: URL: https://github.com/apache/sling-org-apache-sling-testing-email/pull/1#issuecomment-1109935328 Thanks for the PR @ashokmca07 ! -- 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-testing-email] rombert merged pull request #1: Upgrade to sling47
rombert merged PR #1: URL: https://github.com/apache/sling-org-apache-sling-testing-email/pull/1 -- 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-testing-hamcrest] rombert commented on pull request #1: Upgrade to sling47
rombert commented on PR #1: URL: https://github.com/apache/sling-org-apache-sling-testing-hamcrest/pull/1#issuecomment-1109932522 Thanks for the contribution @ashokmca07 ! -- 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-testing-hamcrest] rombert merged pull request #1: Upgrade to sling47
rombert merged PR #1: URL: https://github.com/apache/sling-org-apache-sling-testing-hamcrest/pull/1 -- 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] [Comment Edited] (SLING-8734) Perform migration of modules to parent 35 (or newer)
[ https://issues.apache.org/jira/browse/SLING-8734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17528214#comment-17528214 ] Robert Munteanu edited comment on SLING-8734 at 4/26/22 2:47 PM: - [~cschneider] - we did not create sub-tasks for all projects. I suspect we have quite a few left. _edit_: I re-ran the scripts from SLING-8732 and I get 184 results still. It includes samples and stuff from the whiteboard, but those should (eventually) be migrated as well if we want to move our CI to Java 11. was (Author: rombert): [~cschneider] - we did not create sub-tasks for all projects. I suspect we have quite a few left. > Perform migration of modules to parent 35 (or newer) > > > Key: SLING-8734 > URL: https://issues.apache.org/jira/browse/SLING-8734 > Project: Sling > Issue Type: Task >Reporter: Robert Munteanu >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (SLING-8734) Perform migration of modules to parent 35 (or newer)
[ https://issues.apache.org/jira/browse/SLING-8734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17528214#comment-17528214 ] Robert Munteanu commented on SLING-8734: [~cschneider] - we did not create sub-tasks for all projects. I suspect we have quite a few left. > Perform migration of modules to parent 35 (or newer) > > > Key: SLING-8734 > URL: https://issues.apache.org/jira/browse/SLING-8734 > Project: Sling > Issue Type: Task >Reporter: Robert Munteanu >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[GitHub] [sling-org-apache-sling-testing-clients] sonarcloud[bot] commented on pull request #31: SLING-11279 Fixing to specify exactly expected code on which httpRetr…
sonarcloud[bot] commented on PR #31: URL: https://github.com/apache/sling-org-apache-sling-testing-clients/pull/31#issuecomment-1109862113 SonarCloud Quality Gate failed. [](https://sonarcloud.io/dashboard?id=apache_sling-org-apache-sling-testing-clients&pullRequest=31) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-clients&pullRequest=31&resolved=false&types=BUG) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-clients&pullRequest=31&resolved=false&types=BUG) [0 Bugs](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-clients&pullRequest=31&resolved=false&types=BUG) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-clients&pullRequest=31&resolved=false&types=VULNERABILITY) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-clients&pullRequest=31&resolved=false&types=VULNERABILITY) [0 Vulnerabilities](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-clients&pullRequest=31&resolved=false&types=VULNERABILITY) [](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-testing-clients&pullRequest=31&resolved=false&types=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-testing-clients&pullRequest=31&resolved=false&types=SECURITY_HOTSPOT) [0 Security Hotspots](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-testing-clients&pullRequest=31&resolved=false&types=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-clients&pullRequest=31&resolved=false&types=CODE_SMELL) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-clients&pullRequest=31&resolved=false&types=CODE_SMELL) [1 Code Smell](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-clients&pullRequest=31&resolved=false&types=CODE_SMELL) [](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-testing-clients&pullRequest=31&metric=new_coverage&view=list) [100.0% Coverage](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-testing-clients&pullRequest=31&metric=new_coverage&view=list) [](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-testing-clients&pullRequest=31&metric=new_duplicated_lines_density&view=list) [0.0% Duplication](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-testing-clients&pullRequest=31&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-8734) Perform migration of modules to parent 35 (or newer)
[ https://issues.apache.org/jira/browse/SLING-8734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17528172#comment-17528172 ] Christian Schneider commented on SLING-8734: Seems all subtasks are done now. > Perform migration of modules to parent 35 (or newer) > > > Key: SLING-8734 > URL: https://issues.apache.org/jira/browse/SLING-8734 > Project: Sling > Issue Type: Task >Reporter: Robert Munteanu >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Closed] (SLING-11261) Exception while starting CodehaleMetricsReporter component on Windows Machine
[
https://issues.apache.org/jira/browse/SLING-11261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu closed SLING-11261.
---
> Exception while starting CodehaleMetricsReporter component on Windows Machine
> -
>
> Key: SLING-11261
> URL: https://issues.apache.org/jira/browse/SLING-11261
> Project: Sling
> Issue Type: Bug
> Components: Commons
> Environment: OS: Windows machine
>Reporter: Sagar Miglani
>Assignee: Robert Munteanu
>Priority: Major
> Fix For: Commons Metrics RRD4J 1.0.6
>
> Attachments: RRD4JReporterProblem.java
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> On windows machine, I am getting the following Exception for while starting
> the CodehaleMetricsReporter component
> {code:xml}
> java.nio.file.InvalidPathException: Illegal char <:> at index 2:
> /C:/playground/rrd4j/metrics/metrics.rrd
> at sun.nio.fs.WindowsPathParser.normalize(WindowsPathParser.java:182)
> at sun.nio.fs.WindowsPathParser.parse(WindowsPathParser.java:153)
> at sun.nio.fs.WindowsPathParser.parse(WindowsPathParser.java:77)
> at sun.nio.fs.WindowsPath.parse(WindowsPath.java:94)
> at sun.nio.fs.WindowsFileSystem.getPath(WindowsFileSystem.java:255)
> at java.nio.file.Paths.get(Paths.java:84)
> at
> org.rrd4j.core.RrdFileBackendFactory.exists(RrdFileBackendFactory.java:26)
> at org.rrd4j.core.RrdBackendFactory.exists(RrdBackendFactory.java:543)
> at org.rrd4j.core.RrdDb.(RrdDb.java:624)
> at org.rrd4j.core.RrdDb.of(RrdDb.java:500)
> {code}
> This is because we are creating RrdDB by passing the path returned by
> RrdDef.getPath() method (see
> [here|https://github.com/apache/sling-org-apache-sling-commons-metrics-rrd4j/blob/master/src/main/java/org/apache/sling/commons/metrics/rrd4j/impl/RRD4JReporter.java#L374])
> which does not return the path correctly and is unreliable as discussed
> [here|https://github.com/rrd4j/rrd4j/issues/152] and It is suggested to use
> RrdDef.getUri() instead.
> Also, while creating the RrdDef with a path RRD4J lib creates an internal
> generic URI which again can not be use directly for creating the File or
> Paths api as this generic URI could be non-absolute in some cases.
> Attaching the test case which should fail on windows machine.
> [^RRD4JReporterProblem.java]
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Closed] (SLING-11008) commons.metrics.rrd4j - switch to slf4j-simple for test logs
[ https://issues.apache.org/jira/browse/SLING-11008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu closed SLING-11008. --- > commons.metrics.rrd4j - switch to slf4j-simple for test logs > > > Key: SLING-11008 > URL: https://issues.apache.org/jira/browse/SLING-11008 > Project: Sling > Issue Type: Task > Components: Commons >Reporter: Robert Munteanu >Assignee: Robert Munteanu >Priority: Major > Fix For: Commons Metrics RRD4J 1.0.6 > > Time Spent: 0.5h > Remaining Estimate: 0h > > For tests we don't often need a complex logging implementation. Logging to > stdout and controlling a couple of parameters are supported for slf4j and we > should use that if at all possible. Being managed as part of the parent pom > is also an advantage. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[RESULT] [VOTE] Release Apache Sling Commons Metrics RRD4J 1.0.6
Hi, The vote has passed with the following result: +1 (binding): Carsten Ziegeler, Dan Klco, Nicolas Peltier +1 (non-binding): Sagar Miglani I will copy this release to the Sling dist directory and promote the artifacts to the central Maven repository. Regards, Robert Munteanu
Re: [VOTE] Release Apache Sling Content Distribution API 0.7.0
+1 Carsten Am 26.04.2022 um 12:19 schrieb Timothee Maret: Hi, We solved 1 issues in this release: https://issues.apache.org/jira/projects/SLING/versions/12351368 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-2626/ You can use this UNIX script to download the release and verify the signatures: https://gitbox.apache.org/repos/asf?p=sling-tooling-release.git;a=blob;f=check_staged_release.sh;hb=HEAD Usage: sh check_staged_release.sh 2626 /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. -- Carsten Ziegeler Adobe cziege...@apache.org
[jira] [Resolved] (SLING-11280) Reference without field and method throws exception
[ https://issues.apache.org/jira/browse/SLING-11280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-11280. -- Resolution: Fixed Fixed by removing the check in https://github.com/apache/sling-org-apache-sling-testing-osgi-mock/commit/4b7a41509a667a3f415665ea0ec357a055fa65e7 > Reference without field and method throws exception > --- > > Key: SLING-11280 > URL: https://issues.apache.org/jira/browse/SLING-11280 > Project: Sling > Issue Type: Bug > Components: Testing >Affects Versions: Testing OSGi Mock 3.2.2 >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler >Priority: Major > Fix For: Testing OSGi Mock 3.2.4 > > > A reference without specifying a field or method is allowed for a DS > component, however with testing mocks this will throw an exception, due to > https://github.com/apache/sling-org-apache-sling-testing-osgi-mock/blob/master/core/src/main/java/org/apache/sling/testing/mock/osgi/OsgiServiceUtil.java#L660 -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Assigned] (SLING-11280) Reference without field and method throws exception
[ https://issues.apache.org/jira/browse/SLING-11280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler reassigned SLING-11280: Assignee: Carsten Ziegeler > Reference without field and method throws exception > --- > > Key: SLING-11280 > URL: https://issues.apache.org/jira/browse/SLING-11280 > Project: Sling > Issue Type: Bug > Components: Testing >Affects Versions: Testing OSGi Mock 3.2.2 >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler >Priority: Major > Fix For: Testing OSGi Mock 3.2.4 > > > A reference without specifying a field or method is allowed for a DS > component, however with testing mocks this will throw an exception, due to > https://github.com/apache/sling-org-apache-sling-testing-osgi-mock/blob/master/core/src/main/java/org/apache/sling/testing/mock/osgi/OsgiServiceUtil.java#L660 -- This message was sent by Atlassian Jira (v8.20.7#820007)
Re: [VOTE] Release Apache Sling Content Distribution API 0.7.0
+1 (non binding) Christian Am Di., 26. Apr. 2022 um 12:19 Uhr schrieb Timothee Maret : > Hi, > > We solved 1 issues in this release: > https://issues.apache.org/jira/projects/SLING/versions/12351368 > > Staging repository: > https://repository.apache.org/content/repositories/orgapachesling-2626/ > > You can use this UNIX script to download the release and verify the > signatures: > > https://gitbox.apache.org/repos/asf?p=sling-tooling-release.git;a=blob;f=check_staged_release.sh;hb=HEAD > > Usage: > sh check_staged_release.sh 2626 /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. > -- -- Christian Schneider http://www.liquid-reality.de Computer Scientist http://www.adobe.com
[jira] [Created] (SLING-11280) Reference without field and method throws exception
Carsten Ziegeler created SLING-11280: Summary: Reference without field and method throws exception Key: SLING-11280 URL: https://issues.apache.org/jira/browse/SLING-11280 Project: Sling Issue Type: Bug Components: Testing Affects Versions: Testing OSGi Mock 3.2.2 Reporter: Carsten Ziegeler Fix For: Testing OSGi Mock 3.2.4 A reference without specifying a field or method is allowed for a DS component, however with testing mocks this will throw an exception, due to https://github.com/apache/sling-org-apache-sling-testing-osgi-mock/blob/master/core/src/main/java/org/apache/sling/testing/mock/osgi/OsgiServiceUtil.java#L660 -- This message was sent by Atlassian Jira (v8.20.7#820007)
[GitHub] [sling-org-apache-sling-testing-clients] tyge68 commented on pull request #31: SLING-11279 Fixing to specify exactly expected code on which httpRetr…
tyge68 commented on PR #31: URL: https://github.com/apache/sling-org-apache-sling-testing-clients/pull/31#issuecomment-1109723748 @dulvac this is an issue we observes on our ITs when running our tests with httpRetries on 404 among with other code, so it would be great to include this fix too. -- 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-testing-clients] tyge68 opened a new pull request, #31: SLING-11279 Fixing to specify exactly expected code on which httpRetr…
tyge68 opened a new pull request, #31: URL: https://github.com/apache/sling-org-apache-sling-testing-clients/pull/31 …iesCode will not be effective Note that existing test already cover this line of code. -- 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-11279) Make SlingClient.exists() more resilient with http retries codes
[ https://issues.apache.org/jira/browse/SLING-11279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thierry Ygé updated SLING-11279: Description: Currently if we are in cluster with affinity cookie and use httpRetries code to retries on 404 to avoid sync problems, the exists() method can be confused for 404 responses. In order to fix it, it need to explicitely list generally expected code that might not need retries in that context. was:SlingHttpResponse.getSlingLocation and other get methods should work when the HTML response is customised by adding things like class="" in order to test the customised application. > Make SlingClient.exists() more resilient with http retries codes > - > > Key: SLING-11279 > URL: https://issues.apache.org/jira/browse/SLING-11279 > Project: Sling > Issue Type: Improvement > Components: Apache Sling Testing Clients >Affects Versions: Apache Sling Testing Clients 3.0.12 >Reporter: Thierry Ygé >Priority: Major > > Currently if we are in cluster with affinity cookie and use httpRetries code > to retries on 404 to avoid sync problems, the exists() method can be confused > for 404 responses. > In order to fix it, it need to explicitely list generally expected code that > might not need retries in that context. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[GitHub] [sling-org-apache-sling-testing-clients] sonarcloud[bot] commented on pull request #30: SLING-11205 Missing fix to be correct
sonarcloud[bot] commented on PR #30: URL: https://github.com/apache/sling-org-apache-sling-testing-clients/pull/30#issuecomment-1109721440 Kudos, SonarCloud Quality Gate passed! [](https://sonarcloud.io/dashboard?id=apache_sling-org-apache-sling-testing-clients&pullRequest=30) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-clients&pullRequest=30&resolved=false&types=BUG) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-clients&pullRequest=30&resolved=false&types=BUG) [0 Bugs](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-clients&pullRequest=30&resolved=false&types=BUG) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-clients&pullRequest=30&resolved=false&types=VULNERABILITY) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-clients&pullRequest=30&resolved=false&types=VULNERABILITY) [0 Vulnerabilities](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-clients&pullRequest=30&resolved=false&types=VULNERABILITY) [](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-testing-clients&pullRequest=30&resolved=false&types=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-testing-clients&pullRequest=30&resolved=false&types=SECURITY_HOTSPOT) [0 Security Hotspots](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-testing-clients&pullRequest=30&resolved=false&types=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-clients&pullRequest=30&resolved=false&types=CODE_SMELL) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-clients&pullRequest=30&resolved=false&types=CODE_SMELL) [0 Code Smells](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-clients&pullRequest=30&resolved=false&types=CODE_SMELL) [](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-testing-clients&pullRequest=30&metric=new_coverage&view=list) [100.0% Coverage](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-testing-clients&pullRequest=30&metric=new_coverage&view=list) [](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-testing-clients&pullRequest=30&metric=new_duplicated_lines_density&view=list) [0.0% Duplication](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-testing-clients&pullRequest=30&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] [Created] (SLING-11279) Make SlingClient.exists() more resilient with http retries codes
Thierry Ygé created SLING-11279: --- Summary: Make SlingClient.exists() more resilient with http retries codes Key: SLING-11279 URL: https://issues.apache.org/jira/browse/SLING-11279 Project: Sling Issue Type: Improvement Components: Apache Sling Testing Clients Affects Versions: Apache Sling Testing Clients 3.0.12 Reporter: Thierry Ygé SlingHttpResponse.getSlingLocation and other get methods should work when the HTML response is customised by adding things like class="" in order to test the customised application. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[GitHub] [sling-org-apache-sling-testing-clients] sonarcloud[bot] commented on pull request #30: SLING-11205 Missing fix to be correct
sonarcloud[bot] commented on PR #30: URL: https://github.com/apache/sling-org-apache-sling-testing-clients/pull/30#issuecomment-1109718132 Kudos, SonarCloud Quality Gate passed! [](https://sonarcloud.io/dashboard?id=apache_sling-org-apache-sling-testing-clients&pullRequest=30) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-clients&pullRequest=30&resolved=false&types=BUG) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-clients&pullRequest=30&resolved=false&types=BUG) [0 Bugs](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-clients&pullRequest=30&resolved=false&types=BUG) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-clients&pullRequest=30&resolved=false&types=VULNERABILITY) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-clients&pullRequest=30&resolved=false&types=VULNERABILITY) [0 Vulnerabilities](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-clients&pullRequest=30&resolved=false&types=VULNERABILITY) [](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-testing-clients&pullRequest=30&resolved=false&types=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-testing-clients&pullRequest=30&resolved=false&types=SECURITY_HOTSPOT) [0 Security Hotspots](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-testing-clients&pullRequest=30&resolved=false&types=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-clients&pullRequest=30&resolved=false&types=CODE_SMELL) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-clients&pullRequest=30&resolved=false&types=CODE_SMELL) [0 Code Smells](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-clients&pullRequest=30&resolved=false&types=CODE_SMELL) [](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-testing-clients&pullRequest=30&metric=new_coverage&view=list) [0.0% Coverage](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-testing-clients&pullRequest=30&metric=new_coverage&view=list) [](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-testing-clients&pullRequest=30&metric=new_duplicated_lines_density&view=list) [0.0% Duplication](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-testing-clients&pullRequest=30&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: [VOTE] Release Apache Sling Content Distribution API 0.7.0
+1 please note: there is also a commit for SLING-9389 in this release, should be added to the changelog stefan >-Original Message- >From: Timothee Maret >Sent: Tuesday, April 26, 2022 12:20 PM >To: dev@sling.apache.org >Subject: [VOTE] Release Apache Sling Content Distribution API 0.7.0 > >Hi, > >We solved 1 issues in this release: >https://issues.apache.org/jira/projects/SLING/versions/12351368 > >Staging repository: >https://repository.apache.org/content/repositories/orgapachesling-2626/ > >You can use this UNIX script to download the release and verify the >signatures: >https://gitbox.apache.org/repos/asf?p=sling-tooling- >release.git;a=blob;f=check_staged_release.sh;hb=HEAD > >Usage: >sh check_staged_release.sh 2626 /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.
[GitHub] [sling-org-apache-sling-testing-clients] tyge68 opened a new pull request, #30: SLING-11205 Missing fix to be correct
tyge68 opened a new pull request, #30: URL: https://github.com/apache/sling-org-apache-sling-testing-clients/pull/30 Currently the original fix in the PR #29 is incomplete, it makes all our tests fails when calling getSlingPath on the response as it would now prefix with ">" the path. As solution I suggest this PR to fix it. @absarasw -- 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-testing-clients] dulvac commented on pull request #29: SLING-11205 Make SlingHttpResponse.getSlingLocation and other get methods resilient to customisations
dulvac commented on PR #29: URL: https://github.com/apache/sling-org-apache-sling-testing-clients/pull/29#issuecomment-1109708336 @absarasw can you correct this as soon as you can and add the unit test please? Thanks @tyge68 -- 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-testing-clients] tyge68 commented on pull request #29: SLING-11205 Make SlingHttpResponse.getSlingLocation and other get methods resilient to customisations
tyge68 commented on PR #29: URL: https://github.com/apache/sling-org-apache-sling-testing-clients/pull/29#issuecomment-1109702717 it's not good it's now returning > as prefix to the path when calling .getSlingPath(), also it lack of tests which explains this PR passed the build -- 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-pipes] sonarcloud[bot] commented on pull request #16: SLING-11278 switch to commons collections 4
sonarcloud[bot] commented on PR #16: URL: https://github.com/apache/sling-org-apache-sling-pipes/pull/16#issuecomment-1109663507 Kudos, SonarCloud Quality Gate passed! [](https://sonarcloud.io/dashboard?id=apache_sling-org-apache-sling-pipes&pullRequest=16) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-pipes&pullRequest=16&resolved=false&types=BUG) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-pipes&pullRequest=16&resolved=false&types=BUG) [0 Bugs](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-pipes&pullRequest=16&resolved=false&types=BUG) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-pipes&pullRequest=16&resolved=false&types=VULNERABILITY) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-pipes&pullRequest=16&resolved=false&types=VULNERABILITY) [0 Vulnerabilities](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-pipes&pullRequest=16&resolved=false&types=VULNERABILITY) [](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-pipes&pullRequest=16&resolved=false&types=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-pipes&pullRequest=16&resolved=false&types=SECURITY_HOTSPOT) [0 Security Hotspots](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-pipes&pullRequest=16&resolved=false&types=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-pipes&pullRequest=16&resolved=false&types=CODE_SMELL) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-pipes&pullRequest=16&resolved=false&types=CODE_SMELL) [1 Code Smell](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-pipes&pullRequest=16&resolved=false&types=CODE_SMELL) [](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-pipes&pullRequest=16&metric=coverage&view=list) No Coverage information [](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-pipes&pullRequest=16&metric=new_duplicated_lines_density&view=list) [0.0% Duplication](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-pipes&pullRequest=16&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-pipes] stefanseifert opened a new pull request, #16: SLING-11278 switch to commons collections 4
stefanseifert opened a new pull request, #16: URL: https://github.com/apache/sling-org-apache-sling-pipes/pull/16 * switch to Commons Collections 4 * this also implies an update of caconfig api 1.2.0/impl 1.5.0 dependencies -- 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] [Created] (SLING-11278) sling-pipes: Switch to Commons Collections 4
Stefan Seifert created SLING-11278: -- Summary: sling-pipes: Switch to Commons Collections 4 Key: SLING-11278 URL: https://issues.apache.org/jira/browse/SLING-11278 Project: Sling Issue Type: Improvement Components: pipes Reporter: Stefan Seifert Assignee: Stefan Seifert Fix For: pipes 4.4.4 switch to Commons Collections 4 this also implies an update of caconfig api 1.2.0/impl 1.5.0 dependencies -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (SLING-8595) Update of sling parent pom
[ https://issues.apache.org/jira/browse/SLING-8595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schneider updated SLING-8595: --- Fix Version/s: Content Distribution Journal Core 0.1.24 (was: Content Distribution Journal Core 0.1.28) > Update of sling parent pom > -- > > Key: SLING-8595 > URL: https://issues.apache.org/jira/browse/SLING-8595 > Project: Sling > Issue Type: Sub-task > Components: Content Distribution >Reporter: Christian Schneider >Assignee: Christian Schneider >Priority: Blocker > Fix For: Content Distribution Journal Core 0.1.24 > > Time Spent: 4h > Remaining Estimate: 0h > > When running upstream modules together with sling distribution core in > eclipse I got issues as the outdated osgi core jar slipped into the build > dependencies of the upstream module. > I found that updating the parent pom fixed the issue. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Resolved] (SLING-9600) Update Sling Query to Commons Lang 3
[
https://issues.apache.org/jira/browse/SLING-9600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert resolved SLING-9600.
---
Resolution: Fixed
https://github.com/apache/sling-org-apache-sling-query/commit/9ec132a80e7d5c99aade8c98537f5ab1f5b5b4b8
> Update Sling Query to Commons Lang 3
>
>
> Key: SLING-9600
> URL: https://issues.apache.org/jira/browse/SLING-9600
> Project: Sling
> Issue Type: Improvement
> Components: Sling Query
>Affects Versions: Sling Query 4.0.2
>Reporter: Cris Rockwell
>Assignee: Stefan Seifert
>Priority: Major
> Fix For: Sling Query 4.0.4
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Logs show this error commons-lang is missing...
> {quote}23.07.2020 11:16:28.973 *INFO* [OsgiInstallerImpl]
> org.apache.sling.installer.core.impl.tasks.BundleStartTask Could not start
> bundle org.apache.sling.query [218]. Reason: {}. Will retry.
> org.osgi.framework.BundleException: Unable to resolve org.apache.sling.query
> [218](R 218.0): missing requirement [org.apache.sling.query [218](R 218.0)]
> osgi.wiring.package;
> (&(osgi.wiring.package=org.apache.commons.lang)(version>=2.5.0)(!(version>=3.0.0)))
> Unresolved requirements: [[org.apache.sling.query [218](R 218.0)]
> osgi.wiring.package;
> (&(osgi.wiring.package=org.apache.commons.lang)(version>=2.5.0)(!(version>=3.0.0)))]
> at
> org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:4368)
> at org.apache.felix.framework.Felix.startBundle(Felix.java:2281)
> at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:998)
> at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:984)
> at
> org.apache.sling.installer.core.impl.tasks.BundleStartTask.execute(BundleStartTask.java:97)
> [org.apache.sling.installer.core:3.11.2]
> at
> org.apache.sling.installer.core.impl.OsgiInstallerImpl.doExecuteTasks(OsgiInstallerImpl.java:918)
> [org.apache.sling.installer.core:3.11.2]
> at
> org.apache.sling.installer.core.impl.OsgiInstallerImpl.executeTasks(OsgiInstallerImpl.java:755)
> [org.apache.sling.installer.core:3.11.2]
> at
> org.apache.sling.installer.core.impl.OsgiInstallerImpl.run(OsgiInstallerImpl.java:304)
> [org.apache.sling.installer.core:3.11.2]
> at java.base/java.lang.Thread.run(Thread.java:834)
> 23.07.2020 11:16:28.978 *INFO* [OsgiInstallerImpl]
> org.apache.sling.installer.core.impl.tasks.BundleStartTask Could not start
> bundle org.apache.sling.query [218]. Reason: {}. Will retry.
> org.osgi.framework.BundleException: Unable to resolve org.apache.sling.query
> [218](R 218.0): missing requirement [org.apache.sling.query [218](R 218.0)]
> osgi.wiring.package;
> (&(osgi.wiring.package=org.apache.commons.lang)(version>=2.5.0)(!(version>=3.0.0)))
> Unresolved requirements: [[org.apache.sling.query [218](R 218.0)]
> osgi.wiring.package;
> (&(osgi.wiring.package=org.apache.commons.lang)(version>=2.5.0)(!(version>=3.0.0)))]
> at
> org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:4368)
> at org.apache.felix.framework.Felix.startBundle(Felix.java:2281)
> at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:998)
> at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:984)
> at
> org.apache.sling.installer.core.impl.tasks.BundleStartTask.execute(BundleStartTask.java:97)
> [org.apache.sling.installer.core:3.11.2]
> at
> org.apache.sling.installer.core.impl.OsgiInstallerImpl.doExecuteTasks(OsgiInstallerImpl.java:918)
> [org.apache.sling.installer.core:3.11.2]
> at
> org.apache.sling.installer.core.impl.OsgiInstallerImpl.executeTasks(OsgiInstallerImpl.java:755)
> [org.apache.sling.installer.core:3.11.2]
> at
> org.apache.sling.installer.core.impl.OsgiInstallerImpl.run(OsgiInstallerImpl.java:304)
> [org.apache.sling.installer.core:3.11.2]
> at java.base/java.lang.Thread.run(Thread.java:834){quote}
> *After updating the pom dependency and various import statements, the bundle
> builds and installs. *
>
> Removed
>
>
>
>
>
>
> Added
>
> org.apache.commons
> commons-lang3
> 3.9
> }}
> Based on the migration guide, most use cases should be fine just updating the
> import statements. I think that's the case for Sling Query as well.
> http://commons.apache.org/proper/commons-lang/article3_0.html
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[GitHub] [sling-org-apache-sling-query] stefanseifert merged pull request #3: SLING-9600 Updated commons-lang to commons-lang3
stefanseifert merged PR #3: URL: https://github.com/apache/sling-org-apache-sling-query/pull/3 -- 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
[VOTE] Release Apache Sling Content Distribution API 0.7.0
Hi, We solved 1 issues in this release: https://issues.apache.org/jira/projects/SLING/versions/12351368 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-2626/ You can use this UNIX script to download the release and verify the signatures: https://gitbox.apache.org/repos/asf?p=sling-tooling-release.git;a=blob;f=check_staged_release.sh;hb=HEAD Usage: sh check_staged_release.sh 2626 /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.
[jira] [Assigned] (SLING-9600) Update Sling Query to Commons Lang 3
[
https://issues.apache.org/jira/browse/SLING-9600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert reassigned SLING-9600:
-
Fix Version/s: Sling Query 4.0.4
Assignee: Stefan Seifert
Issue Type: Improvement (was: Bug)
Summary: Update Sling Query to Commons Lang 3 (was: Sling Query
won't install on Sling12 Launcher Instance)
> Update Sling Query to Commons Lang 3
>
>
> Key: SLING-9600
> URL: https://issues.apache.org/jira/browse/SLING-9600
> Project: Sling
> Issue Type: Improvement
> Components: Sling Query
>Affects Versions: Sling Query 4.0.2
>Reporter: Cris Rockwell
>Assignee: Stefan Seifert
>Priority: Major
> Fix For: Sling Query 4.0.4
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Logs show this error commons-lang is missing...
> {quote}23.07.2020 11:16:28.973 *INFO* [OsgiInstallerImpl]
> org.apache.sling.installer.core.impl.tasks.BundleStartTask Could not start
> bundle org.apache.sling.query [218]. Reason: {}. Will retry.
> org.osgi.framework.BundleException: Unable to resolve org.apache.sling.query
> [218](R 218.0): missing requirement [org.apache.sling.query [218](R 218.0)]
> osgi.wiring.package;
> (&(osgi.wiring.package=org.apache.commons.lang)(version>=2.5.0)(!(version>=3.0.0)))
> Unresolved requirements: [[org.apache.sling.query [218](R 218.0)]
> osgi.wiring.package;
> (&(osgi.wiring.package=org.apache.commons.lang)(version>=2.5.0)(!(version>=3.0.0)))]
> at
> org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:4368)
> at org.apache.felix.framework.Felix.startBundle(Felix.java:2281)
> at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:998)
> at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:984)
> at
> org.apache.sling.installer.core.impl.tasks.BundleStartTask.execute(BundleStartTask.java:97)
> [org.apache.sling.installer.core:3.11.2]
> at
> org.apache.sling.installer.core.impl.OsgiInstallerImpl.doExecuteTasks(OsgiInstallerImpl.java:918)
> [org.apache.sling.installer.core:3.11.2]
> at
> org.apache.sling.installer.core.impl.OsgiInstallerImpl.executeTasks(OsgiInstallerImpl.java:755)
> [org.apache.sling.installer.core:3.11.2]
> at
> org.apache.sling.installer.core.impl.OsgiInstallerImpl.run(OsgiInstallerImpl.java:304)
> [org.apache.sling.installer.core:3.11.2]
> at java.base/java.lang.Thread.run(Thread.java:834)
> 23.07.2020 11:16:28.978 *INFO* [OsgiInstallerImpl]
> org.apache.sling.installer.core.impl.tasks.BundleStartTask Could not start
> bundle org.apache.sling.query [218]. Reason: {}. Will retry.
> org.osgi.framework.BundleException: Unable to resolve org.apache.sling.query
> [218](R 218.0): missing requirement [org.apache.sling.query [218](R 218.0)]
> osgi.wiring.package;
> (&(osgi.wiring.package=org.apache.commons.lang)(version>=2.5.0)(!(version>=3.0.0)))
> Unresolved requirements: [[org.apache.sling.query [218](R 218.0)]
> osgi.wiring.package;
> (&(osgi.wiring.package=org.apache.commons.lang)(version>=2.5.0)(!(version>=3.0.0)))]
> at
> org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:4368)
> at org.apache.felix.framework.Felix.startBundle(Felix.java:2281)
> at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:998)
> at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:984)
> at
> org.apache.sling.installer.core.impl.tasks.BundleStartTask.execute(BundleStartTask.java:97)
> [org.apache.sling.installer.core:3.11.2]
> at
> org.apache.sling.installer.core.impl.OsgiInstallerImpl.doExecuteTasks(OsgiInstallerImpl.java:918)
> [org.apache.sling.installer.core:3.11.2]
> at
> org.apache.sling.installer.core.impl.OsgiInstallerImpl.executeTasks(OsgiInstallerImpl.java:755)
> [org.apache.sling.installer.core:3.11.2]
> at
> org.apache.sling.installer.core.impl.OsgiInstallerImpl.run(OsgiInstallerImpl.java:304)
> [org.apache.sling.installer.core:3.11.2]
> at java.base/java.lang.Thread.run(Thread.java:834){quote}
> *After updating the pom dependency and various import statements, the bundle
> builds and installs. *
>
> Removed
>
>
>
>
>
>
> Added
>
> org.apache.commons
> commons-lang3
> 3.9
> }}
> Based on the migration guide, most use cases should be fine just updating the
> import statements. I think that's the case for Sling Query as well.
> http://commons.apache.org/proper/commons-lang/article3_0.html
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Resolved] (SLING-11277) sling-query: Update to parent pom 47
[ https://issues.apache.org/jira/browse/SLING-11277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seifert resolved SLING-11277. Resolution: Fixed https://github.com/apache/sling-org-apache-sling-query/commit/d13fd084c20e15567a739416a4702b651a13b1a3 > sling-query: Update to parent pom 47 > > > Key: SLING-11277 > URL: https://issues.apache.org/jira/browse/SLING-11277 > Project: Sling > Issue Type: Sub-task > Components: Extensions >Reporter: Stefan Seifert >Assignee: Stefan Seifert >Priority: Major > Fix For: Sling Query 4.0.4 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[GitHub] [sling-org-apache-sling-query] stefanseifert merged pull request #4: SLING-11277 update to parent pom 47 - switch to bnd-maven-plugin
stefanseifert merged PR #4: URL: https://github.com/apache/sling-org-apache-sling-query/pull/4 -- 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-query] sonarcloud[bot] commented on pull request #4: SLING-11277 update to parent pom 47 - switch to bnd-maven-plugin
sonarcloud[bot] commented on PR #4: URL: https://github.com/apache/sling-org-apache-sling-query/pull/4#issuecomment-1109609713 Kudos, SonarCloud Quality Gate passed! [](https://sonarcloud.io/dashboard?id=apache_sling-org-apache-sling-query&pullRequest=4) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-query&pullRequest=4&resolved=false&types=BUG) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-query&pullRequest=4&resolved=false&types=BUG) [0 Bugs](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-query&pullRequest=4&resolved=false&types=BUG) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-query&pullRequest=4&resolved=false&types=VULNERABILITY) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-query&pullRequest=4&resolved=false&types=VULNERABILITY) [0 Vulnerabilities](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-query&pullRequest=4&resolved=false&types=VULNERABILITY) [](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-query&pullRequest=4&resolved=false&types=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-query&pullRequest=4&resolved=false&types=SECURITY_HOTSPOT) [0 Security Hotspots](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-query&pullRequest=4&resolved=false&types=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-query&pullRequest=4&resolved=false&types=CODE_SMELL) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-query&pullRequest=4&resolved=false&types=CODE_SMELL) [0 Code Smells](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-query&pullRequest=4&resolved=false&types=CODE_SMELL) [](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-query&pullRequest=4&metric=coverage&view=list) No Coverage information [](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-query&pullRequest=4&metric=new_duplicated_lines_density&view=list) [0.0% Duplication](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-query&pullRequest=4&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] [Resolved] (SLING-8595) Update of sling parent pom
[ https://issues.apache.org/jira/browse/SLING-8595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schneider resolved SLING-8595. Resolution: Fixed > Update of sling parent pom > -- > > Key: SLING-8595 > URL: https://issues.apache.org/jira/browse/SLING-8595 > Project: Sling > Issue Type: Sub-task > Components: Content Distribution >Reporter: Christian Schneider >Assignee: Christian Schneider >Priority: Blocker > Fix For: Content Distribution Journal Core 0.1.28 > > Time Spent: 4h > Remaining Estimate: 0h > > When running upstream modules together with sling distribution core in > eclipse I got issues as the outdated osgi core jar slipped into the build > dependencies of the upstream module. > I found that updating the parent pom fixed the issue. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (SLING-11277) sling-query: Update to parent pom 47
Stefan Seifert created SLING-11277: -- Summary: sling-query: Update to parent pom 47 Key: SLING-11277 URL: https://issues.apache.org/jira/browse/SLING-11277 Project: Sling Issue Type: Sub-task Components: Extensions Reporter: Stefan Seifert Assignee: Stefan Seifert Fix For: Sling Query 4.0.4 -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Resolved] (SLING-11181) Emit metrics that distinguish transient and permanent distribution failures
[
https://issues.apache.org/jira/browse/SLING-11181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothee Maret resolved SLING-11181.
Resolution: Fixed
> Emit metrics that distinguish transient and permanent distribution failures
> ---
>
> Key: SLING-11181
> URL: https://issues.apache.org/jira/browse/SLING-11181
> Project: Sling
> Issue Type: Improvement
> Components: Content Distribution
>Reporter: José Correia
>Assignee: José Correia
>Priority: Major
> Fix For: Content Distribution Journal Core 0.1.26
>
>
> h3. Context
> Currently, our error metrics don't distinguish between distribution failures
> that are permanent and will fail even if retried, or failures that succeed
> after being retried.
> We want to improve this in order to be able to differentiate both scenarios.
> h3. Solution
> Failure metric should be labeled by:
> * {{Transient failure}}
> * {{Permanent failure}}
> h3. Proposed approach
> We can distinguish both these scenarios by using the following rationale:
> * Transient failures happen whenever a package is distributed successfully
> but had more than 1 attempt at being distributed: {{retries > 0}}
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[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 ] Timothee Maret updated SLING-9143: -- Fix Version/s: Content Distribution Journal Core 0.1.28 (was: Content Distribution Journal Core 0.1.26) > 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.1.28 > > > 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.7#820007)
[jira] [Updated] (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 ] Timothee Maret updated SLING-9403: -- Fix Version/s: Content Distribution Journal Core 0.1.28 (was: Content Distribution Journal Core 0.1.26) > 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.1.28 > > > 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.7#820007)
[jira] [Updated] (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 ] Timothee Maret updated SLING-9321: -- Fix Version/s: Content Distribution Journal Core 0.1.28 (was: Content Distribution Journal Core 0.1.26) > 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.1.28 > > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (SLING-10614) Document package limits
[ https://issues.apache.org/jira/browse/SLING-10614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothee Maret updated SLING-10614: --- Fix Version/s: Content Distribution Journal Core 0.1.28 (was: Content Distribution Journal Core 0.1.26) > 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.1.28 > > > 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.7#820007)
[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
]
Timothee Maret updated SLING-9078:
--
Fix Version/s: Content Distribution Journal Core 0.1.28
(was: Content Distribution Journal Core 0.1.26)
> 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.1.28
>
>
> 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.7#820007)
[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 ] Timothee Maret updated SLING-9065: -- Fix Version/s: Content Distribution Journal Core 0.1.28 (was: Content Distribution Journal Core 0.1.26) > 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.1.28 > > > 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.7#820007)
[jira] [Updated] (SLING-8595) Update of sling parent pom
[ https://issues.apache.org/jira/browse/SLING-8595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothee Maret updated SLING-8595: -- Fix Version/s: Content Distribution Journal Core 0.1.28 (was: Content Distribution Journal Core 0.1.26) > Update of sling parent pom > -- > > Key: SLING-8595 > URL: https://issues.apache.org/jira/browse/SLING-8595 > Project: Sling > Issue Type: Sub-task > Components: Content Distribution >Reporter: Christian Schneider >Assignee: Christian Schneider >Priority: Blocker > Fix For: Content Distribution Journal Core 0.1.28 > > Time Spent: 4h > Remaining Estimate: 0h > > When running upstream modules together with sling distribution core in > eclipse I got issues as the outdated osgi core jar slipped into the build > dependencies of the upstream module. > I found that updating the parent pom fixed the issue. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[GitHub] [sling-org-apache-sling-jcr-repoinit] joerghoh merged pull request #25: SLING-11276 retry on RepoInitExceptions
joerghoh merged PR #25: URL: https://github.com/apache/sling-org-apache-sling-jcr-repoinit/pull/25 -- 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-repoinit] sonarcloud[bot] commented on pull request #25: SLING-11276 retry on RepoInitExceptions
sonarcloud[bot] commented on PR #25: URL: https://github.com/apache/sling-org-apache-sling-jcr-repoinit/pull/25#issuecomment-1109455905 SonarCloud Quality Gate failed. [](https://sonarcloud.io/dashboard?id=apache_sling-org-apache-sling-jcr-repoinit&pullRequest=25) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jcr-repoinit&pullRequest=25&resolved=false&types=BUG) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jcr-repoinit&pullRequest=25&resolved=false&types=BUG) [0 Bugs](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jcr-repoinit&pullRequest=25&resolved=false&types=BUG) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jcr-repoinit&pullRequest=25&resolved=false&types=VULNERABILITY) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jcr-repoinit&pullRequest=25&resolved=false&types=VULNERABILITY) [0 Vulnerabilities](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jcr-repoinit&pullRequest=25&resolved=false&types=VULNERABILITY) [](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-jcr-repoinit&pullRequest=25&resolved=false&types=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-jcr-repoinit&pullRequest=25&resolved=false&types=SECURITY_HOTSPOT) [0 Security Hotspots](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-jcr-repoinit&pullRequest=25&resolved=false&types=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jcr-repoinit&pullRequest=25&resolved=false&types=CODE_SMELL) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jcr-repoinit&pullRequest=25&resolved=false&types=CODE_SMELL) [0 Code Smells](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jcr-repoinit&pullRequest=25&resolved=false&types=CODE_SMELL) [](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-jcr-repoinit&pullRequest=25&metric=new_coverage&view=list) [76.9% Coverage](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-jcr-repoinit&pullRequest=25&metric=new_coverage&view=list) [](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-jcr-repoinit&pullRequest=25&metric=new_duplicated_lines_density&view=list) [0.0% Duplication](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-jcr-repoinit&pullRequest=25&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
