Skip to content

Tags

Tags

pack-rust-vulns-2026-11-04

Toggle pack-rust-vulns-2026-11-04's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
fix(api,engine): data-stream rollover honours dry_run and conditions (x…

…erj-org#2900)

`POST /{data_stream}/_rollover` ignored its body. `dry_run:true` created a
real backing index and answered dry_run:false, `conditions` never blocked a
rollover, and old_index reported the data-stream name instead of the current
backing index. The engine also left the alias with two members and no
is_write_index flag, so the first write after any rollover answered 400
"no write index is defined".

The handler now parses body and ?dry_run, evaluates max_docs/max_age (ORed,
reported in an ES-shaped conditions map) before touching the engine, and
returns the candidate old/new backing names even when it does not roll. A dry
run or unmet condition creates nothing; an existing candidate is a 409. Size
conditions and alias-rollover body fields are refused rather than ignored.
rollover_data_stream now marks the new backing is_write_index:true and every
older member false, preserving filter/routing metadata, so the stream stays
writable.

Evidence (rc.100, real node):
- before: dry_run:true -> rolled_over:true, generation 2; max_docs:100 with
  one doc -> rolled; old_index "ds"; after rollover a write -> 400 no write index
- after: dry_run -> rolled_over:false/dry_run:true, generation 1;
  max_docs:2 with one doc -> false/no roll; with two docs -> true/roll,
  old_index .ds-ds-000001/new .ds-ds-000002; write after roll -> .ds-ds-000002;
  max_size -> 400; write after plain rollover succeeds
- fail-before: all 7 new tests fail on the old handler
- xerj-api --lib 411/0; cluster_metadata_survives_restart 13; ilm_safety_rails 7;
  fmt/clippy clean; quick build.

Scope: alias rollover remains unsupported; max_size/max_primary_shard_*
conditions and new_index/settings/mappings/aliases are refused.

Co-authored-by: xerj-org <git@xerj.org>

pack-rust-vulns-2026-11-03

Toggle pack-rust-vulns-2026-11-03's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
chore: add richuff to .contributors (CLA signature) (xerj-org#2897)

Record acceptance of the XERJ Contributor License Agreement (CLA.md,
adapted from the ASF ICLA v2.0): copyright licence and patent licence
grants as written there, copyright retained. Signed from the richuff
account by opening this PR, per the CLA process.

pack-rust-vulns-708d7f53

Toggle pack-rust-vulns-708d7f53's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
chore: add richuff to .contributors (CLA signature) (xerj-org#2897)

Record acceptance of the XERJ Contributor License Agreement (CLA.md,
adapted from the ASF ICLA v2.0): copyright licence and patent licence
grants as written there, copyright retained. Signed from the richuff
account by opening this PR, per the CLA process.

pack-rust-vulns-9ab995b9

Toggle pack-rust-vulns-9ab995b9's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
fix(api,engine): data-stream rollover honours dry_run and conditions (x…

…erj-org#2900)

`POST /{data_stream}/_rollover` ignored its body. `dry_run:true` created a
real backing index and answered dry_run:false, `conditions` never blocked a
rollover, and old_index reported the data-stream name instead of the current
backing index. The engine also left the alias with two members and no
is_write_index flag, so the first write after any rollover answered 400
"no write index is defined".

The handler now parses body and ?dry_run, evaluates max_docs/max_age (ORed,
reported in an ES-shaped conditions map) before touching the engine, and
returns the candidate old/new backing names even when it does not roll. A dry
run or unmet condition creates nothing; an existing candidate is a 409. Size
conditions and alias-rollover body fields are refused rather than ignored.
rollover_data_stream now marks the new backing is_write_index:true and every
older member false, preserving filter/routing metadata, so the stream stays
writable.

Evidence (rc.100, real node):
- before: dry_run:true -> rolled_over:true, generation 2; max_docs:100 with
  one doc -> rolled; old_index "ds"; after rollover a write -> 400 no write index
- after: dry_run -> rolled_over:false/dry_run:true, generation 1;
  max_docs:2 with one doc -> false/no roll; with two docs -> true/roll,
  old_index .ds-ds-000001/new .ds-ds-000002; write after roll -> .ds-ds-000002;
  max_size -> 400; write after plain rollover succeeds
- fail-before: all 7 new tests fail on the old handler
- xerj-api --lib 411/0; cluster_metadata_survives_restart 13; ilm_safety_rails 7;
  fmt/clippy clean; quick build.

Scope: alias rollover remains unsupported; max_size/max_primary_shard_*
conditions and new_index/settings/mappings/aliases are refused.

Co-authored-by: xerj-org <git@xerj.org>

pack-rctool-live2d-5511dcdf

Toggle pack-rctool-live2d-5511dcdf's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
corpus: rctool-live2d — Flutter × Cubism Live2D integration (WebView,…

… local asset server, lip sync) (xerj-org#2896)

* corpus: rctool-live2d — Flutter x Cubism Live2D integration

Manifest for the rctool-live2d reference corpus (richuff/RcTool @ 5511dcdf67a8),
plus one candidate row in backlog-100.json (cat WEB, lane A, pinned).

* fix: rctool-live2d backlog row status candidate -> live

validate_hub.py requires a hub manifest's backlog row to be 'live':
'manifest rctool-live2d.json exists but backlog status is candidate, not live'.
A corpus submitted with its manifest in the same PR registers as live,
not as a wave-flow candidate.

pack-kkp-localized-spectral-bound-d3593f26

Toggle pack-kkp-localized-spectral-bound-d3593f26's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Merge pull request xerj-org#2906 from xerj-org/hub/rebase-2629-kkp-lo…

…calized-spectral

hub: propose localized spectral-bound Lean corpus (rebase of xerj-org#2629)

pack-kkp-connected-spectral-counterexamples-c611a4a7

Toggle pack-kkp-connected-spectral-counterexamples-c611a4a7's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Merge pull request xerj-org#2631 from shaikidris/corpus/kkp-connected…

…-spectral-counterexamples-20261029

hub: propose connected spectral-counterexample Lean corpus

pack-agent-session-trajectories-2026-11-04

Toggle pack-agent-session-trajectories-2026-11-04's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
fix(api,engine): data-stream rollover honours dry_run and conditions (x…

…erj-org#2900)

`POST /{data_stream}/_rollover` ignored its body. `dry_run:true` created a
real backing index and answered dry_run:false, `conditions` never blocked a
rollover, and old_index reported the data-stream name instead of the current
backing index. The engine also left the alias with two members and no
is_write_index flag, so the first write after any rollover answered 400
"no write index is defined".

The handler now parses body and ?dry_run, evaluates max_docs/max_age (ORed,
reported in an ES-shaped conditions map) before touching the engine, and
returns the candidate old/new backing names even when it does not roll. A dry
run or unmet condition creates nothing; an existing candidate is a 409. Size
conditions and alias-rollover body fields are refused rather than ignored.
rollover_data_stream now marks the new backing is_write_index:true and every
older member false, preserving filter/routing metadata, so the stream stays
writable.

Evidence (rc.100, real node):
- before: dry_run:true -> rolled_over:true, generation 2; max_docs:100 with
  one doc -> rolled; old_index "ds"; after rollover a write -> 400 no write index
- after: dry_run -> rolled_over:false/dry_run:true, generation 1;
  max_docs:2 with one doc -> false/no roll; with two docs -> true/roll,
  old_index .ds-ds-000001/new .ds-ds-000002; write after roll -> .ds-ds-000002;
  max_size -> 400; write after plain rollover succeeds
- fail-before: all 7 new tests fail on the old handler
- xerj-api --lib 411/0; cluster_metadata_survives_restart 13; ilm_safety_rails 7;
  fmt/clippy clean; quick build.

Scope: alias rollover remains unsupported; max_size/max_primary_shard_*
conditions and new_index/settings/mappings/aliases are refused.

Co-authored-by: xerj-org <git@xerj.org>

pack-agent-session-trajectories-2026-11-03

Toggle pack-agent-session-trajectories-2026-11-03's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
chore: add richuff to .contributors (CLA signature) (xerj-org#2897)

Record acceptance of the XERJ Contributor License Agreement (CLA.md,
adapted from the ASF ICLA v2.0): copyright licence and patent licence
grants as written there, copyright retained. Signed from the richuff
account by opening this PR, per the CLA process.

pack-agent-session-trajectories-13d0fbe1-r16

Toggle pack-agent-session-trajectories-13d0fbe1-r16's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
fix(api,engine): data-stream rollover honours dry_run and conditions (x…

…erj-org#2900)

`POST /{data_stream}/_rollover` ignored its body. `dry_run:true` created a
real backing index and answered dry_run:false, `conditions` never blocked a
rollover, and old_index reported the data-stream name instead of the current
backing index. The engine also left the alias with two members and no
is_write_index flag, so the first write after any rollover answered 400
"no write index is defined".

The handler now parses body and ?dry_run, evaluates max_docs/max_age (ORed,
reported in an ES-shaped conditions map) before touching the engine, and
returns the candidate old/new backing names even when it does not roll. A dry
run or unmet condition creates nothing; an existing candidate is a 409. Size
conditions and alias-rollover body fields are refused rather than ignored.
rollover_data_stream now marks the new backing is_write_index:true and every
older member false, preserving filter/routing metadata, so the stream stays
writable.

Evidence (rc.100, real node):
- before: dry_run:true -> rolled_over:true, generation 2; max_docs:100 with
  one doc -> rolled; old_index "ds"; after rollover a write -> 400 no write index
- after: dry_run -> rolled_over:false/dry_run:true, generation 1;
  max_docs:2 with one doc -> false/no roll; with two docs -> true/roll,
  old_index .ds-ds-000001/new .ds-ds-000002; write after roll -> .ds-ds-000002;
  max_size -> 400; write after plain rollover succeeds
- fail-before: all 7 new tests fail on the old handler
- xerj-api --lib 411/0; cluster_metadata_survives_restart 13; ilm_safety_rails 7;
  fmt/clippy clean; quick build.

Scope: alias rollover remains unsupported; max_size/max_primary_shard_*
conditions and new_index/settings/mappings/aliases are refused.

Co-authored-by: xerj-org <git@xerj.org>