September 2026 - notifications

[xwiki/xwiki-dev-llm]
by XWiki Notifications 17 Sep '26

17 Sep '26

Branch: refs/heads/okf-prchecker-grant Home: https://github.com/xwiki/xwiki-dev-llm To unsubscribe from these emails, change your notification settings at https://github.com/xwiki/xwiki-dev-llm/settings/notifications

1 0

[xwiki/xwiki-dev-llm] 57d4c0: [Misc] Cover granting Programming Rights to a func...
by XWiki Notifications 17 Sep '26

17 Sep '26

Branch: refs/heads/master Home: https://github.com/xwiki/xwiki-dev-llm Commit: 57d4c005c8cbc04e971c3351e47d460caa47be54 https://github.com/xwiki/xwiki-dev-llm/commit/57d4c005c8cbc04e971c3351e47d4… Author: Vincent Massol <vincent(a)massol.net> Date: 2026-09-17 (Thu, 17 Sep 2026) Changed paths: M xwiki/okf/testing/strategy.md Log Message: ----------- [Misc] Cover granting Programming Rights to a functional test's own content * The PRChecker bullet only explained how to READ a `PRChecker: Block programming right` log line, so nothing in the OKF answered the authoring question: my test creates content that needs the right, how do I grant it? Add that direction to the same bullet, keyed on the symptoms actually seen (the rendered "You need Programming Rights to execute the script macro [groovy]" error), with the concrete `@UITest(properties = {"xwikiPropertiesAdditionalProperties=test.prchecker.excludePattern=..."})` form, the fact that the exclusion really grants the right rather than only silencing the log, and the whole-reference match trap. * Tighten the probe clause that the addition made longer. Co-Authored-By: Claude Opus 5 (1M context) <noreply(a)anthropic.com> Commit: 9aadf69ee9a6e8d64e9653f8ae5ea079f6b9e753 https://github.com/xwiki/xwiki-dev-llm/commit/9aadf69ee9a6e8d64e9653f8ae5ea… Author: Vincent Massol <vincent(a)massol.net> Date: 2026-09-17 (Thu, 17 Sep 2026) Changed paths: M xwiki/instructions/xwiki-org.md M xwiki/skills/xwiki-test-guidelines/SKILL.md Log Message: ----------- [Misc] Make the test-guidelines skill claim the act of writing a test * The skill's description described its contents instead of naming its trigger, and the always-on instruction called it "deeper testing guidance", so a small test change (one added @Test method in an existing class) routed to nothing and the rules were never loaded. Turn the description into a trigger that names the action, covers functional @UITest tests, and closes the "it's only one method / the class already exists / this one is simple" escape, and make the always-on line an obligation rather than an invitation. * Drop the *Test.java / *IT.java naming rule from the always-on file: it is stated verbatim in okf/testing/strategy.md, which is its home, and the budget is better spent on the routing rule. Co-Authored-By: Claude Opus 5 (1M context) <noreply(a)anthropic.com> Commit: 6ffdb5b4a73b1164b9c16c036e36277e0b74d687 https://github.com/xwiki/xwiki-dev-llm/commit/6ffdb5b4a73b1164b9c16c036e362… Author: Vincent Massol <vincent(a)massol.net> Date: 2026-09-17 (Thu, 17 Sep 2026) Changed paths: M xwiki/instructions/xwiki-org.md M xwiki/okf/testing/strategy.md M xwiki/skills/xwiki-test-guidelines/SKILL.md Log Message: ----------- Merge pull request #147 from xwiki/okf-prchecker-grant [Misc] Route test authoring to the test rules, and cover granting Programming Rights to a test's own content Compare: https://github.com/xwiki/xwiki-dev-llm/compare/5492f4e5a923...6ffdb5b4a73b To unsubscribe from these emails, change your notification settings at https://github.com/xwiki/xwiki-dev-llm/settings/notifications

1 0

[xwiki/xwiki-platform] 8a5434: XWIKI-6688: Possible race condition when clicking ...
by XWiki Notifications 17 Sep '26

17 Sep '26

Branch: refs/heads/XWIKI-6688 Home: https://github.com/xwiki/xwiki-platform Commit: 8a5434eb591ad41b5747027a4fa7cd72497f778d https://github.com/xwiki/xwiki-platform/commit/8a5434eb591ad41b5747027a4fa7… Author: Vincent Massol <vincent(a)massol.net> Date: 2026-09-17 (Thu, 17 Sep 2026) Changed paths: M xwiki-platform-core/xwiki-platform-administration/xwiki-platform-administration-test/xwiki-platform-administration-test-docker/src/test/it/org/xwiki/administration/test/ui/PageTemplatesIT.java M xwiki-platform-core/xwiki-platform-flamingo/xwiki-platform-flamingo-skin/xwiki-platform-flamingo-skin-test/xwiki-platform-flamingo-skin-test-docker/src/test/it/org/xwiki/flamingo/test/docker/CopyPageIT.java M xwiki-platform-core/xwiki-platform-flamingo/xwiki-platform-flamingo-skin/xwiki-platform-flamingo-skin-test/xwiki-platform-flamingo-skin-test-docker/src/test/it/org/xwiki/flamingo/test/docker/DocExtraTabsIT.java M xwiki-platform-core/xwiki-platform-flamingo/xwiki-platform-flamingo-skin/xwiki-platform-flamingo-skin-test/xwiki-platform-flamingo-skin-test-docker/src/test/it/org/xwiki/flamingo/test/docker/VersionIT.java M xwiki-platform-core/xwiki-platform-web/xwiki-platform-web-war/src/main/webapp/resources/js/xwiki/xwiki.js Log Message: ----------- XWIKI-6688: Possible race condition when clicking on a tab at the bottom of a page in view mode * Display a document extra pane only when it's still the one requested last, so that a pane which is slow to load doesn't take the place of a pane requested after it. The panes are loaded asynchronously and their responses can arrive in any order, which happens in particular when the user clicks on a pane while the first pane, loaded automatically when the page is loaded, is still loading. * Mark a loaded pane as no longer empty even when it ends up not being displayed, so that its content isn't fetched and inserted a second time when it's displayed later. * Add a functional test opening a pane while a slow one is still loading. * Remove the waits that the functional tests were using to work around this bug. Co-Authored-By: Claude Opus 5 (1M context) <noreply(a)anthropic.com> To unsubscribe from these emails, change your notification settings at https://github.com/xwiki/xwiki-platform/settings/notifications

1 0

[xwiki/xwiki-dev-llm] 9aadf6: [Misc] Make the test-guidelines skill claim the ac...
by XWiki Notifications 17 Sep '26

17 Sep '26

Branch: refs/heads/okf-prchecker-grant Home: https://github.com/xwiki/xwiki-dev-llm Commit: 9aadf69ee9a6e8d64e9653f8ae5ea079f6b9e753 https://github.com/xwiki/xwiki-dev-llm/commit/9aadf69ee9a6e8d64e9653f8ae5ea… Author: Vincent Massol <vincent(a)massol.net> Date: 2026-09-17 (Thu, 17 Sep 2026) Changed paths: M xwiki/instructions/xwiki-org.md M xwiki/skills/xwiki-test-guidelines/SKILL.md Log Message: ----------- [Misc] Make the test-guidelines skill claim the act of writing a test * The skill's description described its contents instead of naming its trigger, and the always-on instruction called it "deeper testing guidance", so a small test change (one added @Test method in an existing class) routed to nothing and the rules were never loaded. Turn the description into a trigger that names the action, covers functional @UITest tests, and closes the "it's only one method / the class already exists / this one is simple" escape, and make the always-on line an obligation rather than an invitation. * Drop the *Test.java / *IT.java naming rule from the always-on file: it is stated verbatim in okf/testing/strategy.md, which is its home, and the budget is better spent on the routing rule. Co-Authored-By: Claude Opus 5 (1M context) <noreply(a)anthropic.com> To unsubscribe from these emails, change your notification settings at https://github.com/xwiki/xwiki-dev-llm/settings/notifications

1 0

[xwiki/xwiki-dev-llm] 57d4c0: [Misc] Cover granting Programming Rights to a func...
by XWiki Notifications 17 Sep '26

17 Sep '26

Branch: refs/heads/okf-prchecker-grant Home: https://github.com/xwiki/xwiki-dev-llm Commit: 57d4c005c8cbc04e971c3351e47d460caa47be54 https://github.com/xwiki/xwiki-dev-llm/commit/57d4c005c8cbc04e971c3351e47d4… Author: Vincent Massol <vincent(a)massol.net> Date: 2026-09-17 (Thu, 17 Sep 2026) Changed paths: M xwiki/okf/testing/strategy.md Log Message: ----------- [Misc] Cover granting Programming Rights to a functional test's own content * The PRChecker bullet only explained how to READ a `PRChecker: Block programming right` log line, so nothing in the OKF answered the authoring question: my test creates content that needs the right, how do I grant it? Add that direction to the same bullet, keyed on the symptoms actually seen (the rendered "You need Programming Rights to execute the script macro [groovy]" error), with the concrete `@UITest(properties = {"xwikiPropertiesAdditionalProperties=test.prchecker.excludePattern=..."})` form, the fact that the exclusion really grants the right rather than only silencing the log, and the whole-reference match trap. * Tighten the probe clause that the addition made longer. Co-Authored-By: Claude Opus 5 (1M context) <noreply(a)anthropic.com> To unsubscribe from these emails, change your notification settings at https://github.com/xwiki/xwiki-dev-llm/settings/notifications

1 0

[[email protected]][Issue] Updates for XWIKI-6688: Possible race condition when clicking on a tab at the bottom of a page in view mode
by XWiki Notifications 17 Sep '26

17 Sep '26

1 0

[[email protected]][Issue] Updates for XWIKI-6688: Possible race condition when clicking on a tab at the bottom of a page in view mode
by XWiki Notifications 17 Sep '26

17 Sep '26

1 0

[[email protected]][Issue] Updates for XWIKI-6161: Reset action does not work anymore
by XWiki Notifications 17 Sep '26

17 Sep '26

1 0

[[email protected]][Issue] Updates for XWIKI-25019: Acquiring a document lock can fail with a deadlock on MySQL
by XWiki Notifications 17 Sep '26

17 Sep '26

1 0

[[email protected]][Issue] Updates for XWIKI-6161: Reset action does not work anymore
by XWiki Notifications 17 Sep '26

17 Sep '26

1 0