Skip to content

[pull] trunk from spiceai:trunk#840

Merged
pull[bot] merged 7 commits into
TheRakeshPurohit:trunkfrom
spiceai:trunk
May 16, 2026
Merged

[pull] trunk from spiceai:trunk#840
pull[bot] merged 7 commits into
TheRakeshPurohit:trunkfrom
spiceai:trunk

Conversation

@pull
Copy link
Copy Markdown

@pull pull Bot commented May 16, 2026

See Commits and Changes for more details.


Created by pull[bot] (v2.0.0-alpha.4)

Can you help keep this open source service alive? 💖 Please sponsor : )

claudespice and others added 7 commits May 16, 2026 07:23
The metrics table builder declared six headers but every row added seven
cells, so `disk_write_operations` rendered without a label and the disk
columns were captioned with unrelated names ("DISK USED", "DISK AVAIL",
"DISK CAP"). Re-label so the header count matches the row count and the
labels accurately describe each metric (read/write bytes vs. ops).

Extract `metrics_table_headers()` and `metrics_table_row()` so a unit
test can assert the header count equals the row count and prevent this
regression class from recurring.

Fixes #9989

Co-authored-by: Luke Kim <80174+lukekim@users.noreply.github.com>
* fix: Deny nondistributed cayenne catalog

* review: Address comments

* chore: build

* test: ignore tests which use cayenne catalog non-distributed

* Update mod.rs

---------

Co-authored-by: Luke Kim <80174+lukekim@users.noreply.github.com>
* Upgrade Turso to v0.6.0

* feat(turso): add support for NULLS FIRST/LAST ordering in queries and implement related test

---------

Co-authored-by: Luke Kim <80174+lukekim@users.noreply.github.com>
* Remove rollback method from cloud client

The /v1/apps/{id}/rollback endpoint does not exist in the cloud API.

* remove rollback from CLI

* uncomment

* fix: remove CloudCommands::Rollback references from main.rs

The Rollback variant was removed from CloudCommands in mod.rs but two
references remained in main.rs:
- The is_json_output match arm for CloudCommands::Rollback
- The 'spice cloud rollback --output json' entry in the JSON commands list

* fix: remove extra blank line to satisfy rustfmt

---------

Co-authored-by: Jeadie <jeadie@users.noreply.github.com>
Co-authored-by: Luke Kim <80174+lukekim@users.noreply.github.com>
… (#10860)

Adds three query parameters to /v1/ready so Kubernetes readiness probes can
gate scheduler readiness on executor availability without restarting the
scheduler:

  min_ready_executors=<u32>          minimum currently-ready executors
  min_ready_executors_percent=<u8>   minimum ready/registered ratio (0-100)
  verbose=true                       multi-line diagnostic body

Decision logic: components must be ready (unchanged), then both supplied
gates must pass. A value of 0 disables that gate. Percentage uses the
currently-registered (control stream open) count as denominator so a
dynamic fleet self-adapts (no peak-of-history poisoning, no restart
asymmetry). Supplying a non-zero executor gate against a non-scheduler
runtime returns 400 to surface misconfiguration.

The verbose body mirrors Kubernetes /readyz?verbose, e.g.:

  [+] components ok
  [-] executors: 2/5 ready (40%, registered=5, min=3, min_percent=80%)
  not ready

ExecutorRegistry gains ready_executor_count() and connected_executor_count()
accessors over the existing maps; no new bookkeeping. Routes layer the
optional registry onto the unauthenticated /v1/ready router.

Co-authored-by: Luke Kim <80174+lukekim@users.noreply.github.com>
@pull pull Bot locked and limited conversation to collaborators May 16, 2026
@pull pull Bot added the ⤵️ pull label May 16, 2026
@pull pull Bot merged commit 91dca38 into TheRakeshPurohit:trunk May 16, 2026
1 of 11 checks passed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants