September 2026 - notifications

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

18 Sep '26

Branch: refs/heads/ci-check-in-flight-fix 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] e36d6b: [Misc] Stay quiet about a CI incident an open PR a...
by XWiki Notifications 18 Sep '26

18 Sep '26

Branch: refs/heads/master Home: https://github.com/xwiki/xwiki-dev-llm Commit: e36d6bec86101d75d794fbd0b931f2e42c91af6b https://github.com/xwiki/xwiki-dev-llm/commit/e36d6bec86101d75d794fbd0b931f… Author: Vincent Massol <vincent(a)massol.net> Date: 2026-09-18 (Fri, 18 Sep 2026) Changed paths: M xwiki/skills/xwiki-ci-check/SKILL.md M xwiki/skills/xwiki-ci-check/tools/ci-check.mjs Log Message: ----------- [Misc] Stay quiet about a CI incident an open PR already answers * Add `fix-in-flight` to `fixState`: an open PR whose title or body names the failing test class, or the JIRA key the incident is tracked as, buys the same silence a landed-but-unbuilt commit does — no deep slot, no commit comment, one line in the paste. Root-causing a test somebody is visibly working on is arguing with the room. * Run it only where the branch itself holds nothing: a landed commit will be judged by the next build, a PR is somebody's intent, and the stronger evidence is what the reader needs. Inherits S1's coverage rule whole — a PR answering one failing class of two leaves the incident live, with its blame and its comment. * Read the open PRs once per repo per run, never per incident: the plain `pulls` list newest-updated first, stopping at the first PR outside a 14-day window, three pages at most. That is 1-2 requests for xwiki-platform's ~230 open PRs, on the core quota rather than the search API's own budget. * Require the PR's base branch to be the incident's branch. A master PR cannot fix `stable-17.10.x`, and silencing that branch on it would hide a break nobody is working on. * Let a JIRA key answer for the whole incident only when the incident is a single test class — the key is the flicker issue of its first test and says nothing about classes that merely broke in the same build. * Give `fixState` a `where` clause and a per-kind headline, so the four places that render it stop spelling out one kind's story and the next value is a row in a table rather than a branch in each of them. * Word it *may be in flight*, never *fixed*: the PR may be a rewrite that touches the test, and it may never merge. What settles it is the merge, not this run. Verified against xwiki-platform/master: the live sweep is unchanged (the one answered incident is still `fix-unbuilt`, and no open PR names the other three), and a probe with the forward pass short-circuited matches `#6456` and correctly reports it as partial. Co-Authored-By: Claude Opus 5 (1M context) <noreply(a)anthropic.com> Commit: 802a3df5870cf42e6418759e0c3313dfbe34be06 https://github.com/xwiki/xwiki-dev-llm/commit/802a3df5870cf42e6418759e0c331… Author: Vincent Massol <vincent(a)massol.net> Date: 2026-09-18 (Fri, 18 Sep 2026) Changed paths: M xwiki/skills/xwiki-ci-check/SKILL.md M xwiki/skills/xwiki-ci-check/tools/ci-check.mjs Log Message: ----------- Merge pull request #152 from xwiki/ci-check-in-flight-fix [Misc] Stay quiet about a CI incident an open PR already answers Compare: https://github.com/xwiki/xwiki-dev-llm/compare/3014ce3944f5...802a3df5870c 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] e36d6b: [Misc] Stay quiet about a CI incident an open PR a...
by XWiki Notifications 18 Sep '26

18 Sep '26

Branch: refs/heads/ci-check-in-flight-fix Home: https://github.com/xwiki/xwiki-dev-llm Commit: e36d6bec86101d75d794fbd0b931f2e42c91af6b https://github.com/xwiki/xwiki-dev-llm/commit/e36d6bec86101d75d794fbd0b931f… Author: Vincent Massol <vincent(a)massol.net> Date: 2026-09-18 (Fri, 18 Sep 2026) Changed paths: M xwiki/skills/xwiki-ci-check/SKILL.md M xwiki/skills/xwiki-ci-check/tools/ci-check.mjs Log Message: ----------- [Misc] Stay quiet about a CI incident an open PR already answers * Add `fix-in-flight` to `fixState`: an open PR whose title or body names the failing test class, or the JIRA key the incident is tracked as, buys the same silence a landed-but-unbuilt commit does — no deep slot, no commit comment, one line in the paste. Root-causing a test somebody is visibly working on is arguing with the room. * Run it only where the branch itself holds nothing: a landed commit will be judged by the next build, a PR is somebody's intent, and the stronger evidence is what the reader needs. Inherits S1's coverage rule whole — a PR answering one failing class of two leaves the incident live, with its blame and its comment. * Read the open PRs once per repo per run, never per incident: the plain `pulls` list newest-updated first, stopping at the first PR outside a 14-day window, three pages at most. That is 1-2 requests for xwiki-platform's ~230 open PRs, on the core quota rather than the search API's own budget. * Require the PR's base branch to be the incident's branch. A master PR cannot fix `stable-17.10.x`, and silencing that branch on it would hide a break nobody is working on. * Let a JIRA key answer for the whole incident only when the incident is a single test class — the key is the flicker issue of its first test and says nothing about classes that merely broke in the same build. * Give `fixState` a `where` clause and a per-kind headline, so the four places that render it stop spelling out one kind's story and the next value is a row in a table rather than a branch in each of them. * Word it *may be in flight*, never *fixed*: the PR may be a rewrite that touches the test, and it may never merge. What settles it is the merge, not this run. Verified against xwiki-platform/master: the live sweep is unchanged (the one answered incident is still `fix-unbuilt`, and no open PR names the other three), and a probe with the forward pass short-circuited matches `#6456` and correctly reports it as partial. 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]
by XWiki Notifications 18 Sep '26

18 Sep '26

Branch: refs/tags/v1.12.3 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] 3014ce: [Misc] Release 1.12.3
by XWiki Notifications 18 Sep '26

18 Sep '26

Branch: refs/heads/master Home: https://github.com/xwiki/xwiki-dev-llm Commit: 3014ce3944f5041a6be3e9f6b630605492955d1f https://github.com/xwiki/xwiki-dev-llm/commit/3014ce3944f5041a6be3e9f6b6306… Author: github-actions[bot] <41898282+github-actions[bot](a)users.noreply.github.com> Date: 2026-09-18 (Fri, 18 Sep 2026) Changed paths: M .claude-plugin/marketplace.json M kimi.plugin.json M opencode.jsonc M xwiki/.claude-plugin/plugin.json Log Message: ----------- [Misc] Release 1.12.3 * content edits only (no capability added or removed) 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]
by XWiki Notifications 18 Sep '26

18 Sep '26

Branch: refs/heads/ci-check-forward-fix 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] 4719d2: [Misc] Stay quiet about a CI incident the branch h...
by XWiki Notifications 18 Sep '26

18 Sep '26

Branch: refs/heads/master Home: https://github.com/xwiki/xwiki-dev-llm Commit: 4719d20d62a9e73166c51a0e389cafb0f13a794b https://github.com/xwiki/xwiki-dev-llm/commit/4719d20d62a9e73166c51a0e389ca… Author: Vincent Massol <vincent(a)massol.net> Date: 2026-09-18 (Fri, 18 Sep 2026) Changed paths: M xwiki/skills/xwiki-ci-check/SKILL.md M xwiki/skills/xwiki-ci-check/tools/ci-check.mjs Log Message: ----------- [Misc] Stay quiet about a CI incident the branch has already fixed * Look forward as well as backward: blame reads the commits inside the regression window, and nothing read the ones pushed after CI last built the branch — so a break fixed at 22:27 was still being root-caused, and its author still pinged, at 06:00 the next morning. * Add `fixState` to an incident, computed before the deep budget is allocated: a settled incident spends no slot, gets one line instead of an analysis, and is written about nowhere. * Match on the failing file alone, never the package around it. Backward, a commit touching the test's package is a fair suspect and the cost of being wrong is a comment that asks; forward, the cost is silence about a live breakage. Measured on master: with the package key, a commit touching `VersionIT.java` silenced a systematic failure of its neighbour `DocExtraTabsIT`. * Count coverage in tests, not in keys: one incident spans the N tests that broke together, and only a full house goes quiet. A commit answering some of them is reported beside an incident that still stands. * Cache each commit's record for the run — one push otherwise costs a request per job per commit, now that every job walks the unbuilt range. Verified against xwiki-platform/master, where the two commits of `#6449` and `#6450` answer one incident between them and it went quiet correctly. Co-Authored-By: Claude Opus 5 (1M context) <noreply(a)anthropic.com> Commit: 871e5e077a3889fa48a59fe1bb45e08146d2e6a8 https://github.com/xwiki/xwiki-dev-llm/commit/871e5e077a3889fa48a59fe1bb45e… Author: Vincent Massol <vincent(a)massol.net> Date: 2026-09-18 (Fri, 18 Sep 2026) Changed paths: M xwiki/skills/xwiki-ci-check/SKILL.md M xwiki/skills/xwiki-ci-check/tools/ci-check.mjs Log Message: ----------- Merge pull request #151 from xwiki/ci-check-forward-fix [Misc] Stay quiet about a CI incident the branch has already fixed Compare: https://github.com/xwiki/xwiki-dev-llm/compare/0d6c0e531124...871e5e077a38 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] 4719d2: [Misc] Stay quiet about a CI incident the branch h...
by XWiki Notifications 18 Sep '26

18 Sep '26

Branch: refs/heads/ci-check-forward-fix Home: https://github.com/xwiki/xwiki-dev-llm Commit: 4719d20d62a9e73166c51a0e389cafb0f13a794b https://github.com/xwiki/xwiki-dev-llm/commit/4719d20d62a9e73166c51a0e389ca… Author: Vincent Massol <vincent(a)massol.net> Date: 2026-09-18 (Fri, 18 Sep 2026) Changed paths: M xwiki/skills/xwiki-ci-check/SKILL.md M xwiki/skills/xwiki-ci-check/tools/ci-check.mjs Log Message: ----------- [Misc] Stay quiet about a CI incident the branch has already fixed * Look forward as well as backward: blame reads the commits inside the regression window, and nothing read the ones pushed after CI last built the branch — so a break fixed at 22:27 was still being root-caused, and its author still pinged, at 06:00 the next morning. * Add `fixState` to an incident, computed before the deep budget is allocated: a settled incident spends no slot, gets one line instead of an analysis, and is written about nowhere. * Match on the failing file alone, never the package around it. Backward, a commit touching the test's package is a fair suspect and the cost of being wrong is a comment that asks; forward, the cost is silence about a live breakage. Measured on master: with the package key, a commit touching `VersionIT.java` silenced a systematic failure of its neighbour `DocExtraTabsIT`. * Count coverage in tests, not in keys: one incident spans the N tests that broke together, and only a full house goes quiet. A commit answering some of them is reported beside an incident that still stands. * Cache each commit's record for the run — one push otherwise costs a request per job per commit, now that every job walks the unbuilt range. Verified against xwiki-platform/master, where the two commits of `#6449` and `#6450` answer one incident between them and it went quiet correctly. 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-contrib/application-changerequest] 0ae184: [Misc] Second attempt to enable sonar
by XWiki Notifications 18 Sep '26

18 Sep '26

Branch: refs/heads/main Home: https://github.com/xwiki-contrib/application-changerequest Commit: 0ae184db9c1bf20ae08a5a44eb50199955399eb0 https://github.com/xwiki-contrib/application-changerequest/commit/0ae184db9… Author: Simon Urli <simon.urli(a)xwiki.com> Date: 2026-09-18 (Fri, 18 Sep 2026) Changed paths: M Jenkinsfile Log Message: ----------- [Misc] Second attempt to enable sonar To unsubscribe from these emails, change your notification settings at https://github.com/xwiki-contrib/application-changerequest/settings/notific…

1 0

[xwiki-contrib/application-changerequest] 05c66e: CRAPP-438: Review invalidation is skipped when a s...
by XWiki Notifications 18 Sep '26

18 Sep '26

Branch: refs/heads/CRAPP-438-cache Home: https://github.com/xwiki-contrib/application-changerequest Commit: 05c66e00e00c3cee3351351ad63bc3609afea0ae https://github.com/xwiki-contrib/application-changerequest/commit/05c66e00e… Author: Simon Urli <simon.urli(a)xwiki.com> Date: 2026-09-18 (Fri, 18 Sep 2026) Changed paths: M application-changerequest-default/src/main/java/org/xwiki/contrib/changerequest/internal/cache/ChangeRequestStorageCacheManager.java Log Message: ----------- CRAPP-438: Review invalidation is skipped when a stale change request is served from the storage cache * Explain in ChangeRequestStorageCacheManager#cacheChangeRequest why nothing is stored when the generation does not match or the entry is gone, namely that another save invalidated the change request while it was being loaded, and why that needs no fallback 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-contrib/application-changerequest/settings/notific…

1 0