chore: add log for runners with no alloc idx

[MasterPtato]

Description

Please include a summary of the changes and the related issue. Please also include relevant motivation and context.

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes.

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

[railway-app]

🚅 Deployed to the rivet-pr-4316 environment in rivet-frontend

Service	Status	Web	Updated (UTC)
website	😴 Sleeping (View Logs)	Web	Feb 26, 2026 at 1:49 am
frontend-inspector	❌ Build Failed (View Logs)	Web	Feb 26, 2026 at 1:42 am
mcp-hub	✅ Success (View Logs)	Web	Feb 26, 2026 at 1:42 am
frontend-cloud	❌ Build Failed (View Logs)	Web	Feb 26, 2026 at 1:42 am
ladle	❌ Build Failed (View Logs)	Web	Feb 26, 2026 at 1:41 am

[MasterPtato]

• fix: always trigger serverless ended early error #4320
• fix: remove useless config params #4319
• fix: add serverless leak fix oneoff #4318
• chore: add log for runners with no alloc idx #4316 👈 (View in Graphite)
• fix(ups): upgrade nats, fix chunking, add chunking tests #4315
• chore: fix tests #4314
• fix: various serverless bug fixes #4313
• fix(guard, runner): enforce http body size and ws msg size #4252
• fix(pegboard): add threshold parameters to runner protocol metadata #4247
• chore: get docker compose working again #4246
• fix(epoxy): make quorum sizes match paper #4234
• fix(rivetkit): stall stop handler until start completes #4192
• main

---

How to use the Graphite Merge Queue

Add the label merge-queue to this PR to add it to the merge queue.

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

[claude]

PR Review: chore: add log for runners with no alloc idx

Summary: This PR adds a temporary diagnostic branch in check_expired to detect runners that are missing their RunnerAllocIdxKey entry when they should have one (not expired, not draining). It also threads draining state into the CheckExpiredInput struct with #[serde(default)] for backwards-compatibility.

---

Bug: Tuple Mismatch in tokio::try_join! (Compile Error)

The most critical issue is in the new else if !input.draining branch. The tokio::try_join! call produces a 6-tuple, but the binding destructure lists 7 names:

let (
    namespace_id_entry,
    name_entry,
    version_entry,
    remaining_slots_entry,
    total_slots_entry,
    protocol_version_entry,  // ← 7th name, no corresponding entry in try_join!
    last_ping_ts_entry,
) = tokio::try_join!(
    tx.read_opt(&namespace_id_key, Snapshot),    // 1
    tx.read_opt(&name_key, Snapshot),            // 2
    tx.read_opt(&version_key, Snapshot),         // 3
    tx.read_opt(&remaining_slots_key, Snapshot), // 4
    tx.read_opt(&total_slots_key, Snapshot),     // 5
    tx.read_opt(&last_ping_ts_key, Snapshot),    // 6
)?;

This is a compile error — Rust cannot destructure a 6-tuple into 7 binding names. protocol_version_entry also never appears in the subsequent let ... else match, confirming it's a leftover from a copy-paste (protocol version is not a parameter of RunnerAllocIdxKey::new and isn't needed here).

Fix: Remove protocol_version_entry from the destructure:

let (
    namespace_id_entry,
    name_entry,
    version_entry,
    remaining_slots_entry,
    total_slots_entry,
    last_ping_ts_entry,
) = tokio::try_join!(...)?;

---

Minor: Potential Division by Zero

let remaining_millislots = (remaining_slots * 1000) / total_slots;

If total_slots is ever 0 this panics. If it's guaranteed to be non-zero by the time a runner has initiated (the Some(total_slots) guard only ensures it was stored, not that it's non-zero), consider a guard or a saturating division. This mirrors the same expression at line 414 in the existing connect_runner2 path, so it's consistent, but worth noting.

---

Positives

• #[serde(default)] on draining is the right approach for activity input backwards-compatibility.
• The TODO comment clearly marks this as temporary scaffolding.
• The tracing::debug! early-return log is helpful for the "not initiated yet" case.
• The warning log message is informative and well-structured.
• Gating the check on !input.draining is correct — draining runners legitimately may not have an alloc index entry.

[pkg-pr-new]

More templates

• actor-actions
• actor-actions-vercel
• ai-agent
• ai-agent-vercel
• example-ai-and-user-generated-actors-freestyle
• chat-room
• chat-room-vercel
• example-cloudflare-workers
• example-cloudflare-workers-hono
• collaborative-document
• collaborative-document-vercel
• cross-actor-actions
• cross-actor-actions-vercel
• example-cursors
• example-cursors-raw-websocket
• example-cursors-raw-websocket-vercel
• example-cursors-vercel
• custom-serverless
• example-elysia
• example-experimental-durable-streams-ai-agent
• example-experimental-durable-streams-ai-agent-vercel
• geo-distributed-database
• geo-distributed-database-vercel
• hello-world
• hello-world-vercel
• example-hono
• hono-react
• hono-react-vercel
• example-kitchen-sink
• example-kitchen-sink-vercel
• multi-region-vercel
• multiplayer-game
• example-multiplayer-game-patterns
• example-multiplayer-game-patterns-vercel
• multiplayer-game-vercel
• native-websockets
• native-websockets-vercel
• next-js
• per-tenant-database
• per-tenant-database-vercel
• example-raw-fetch-handler
• example-raw-fetch-handler-vercel
• example-raw-websocket-handler
• example-raw-websocket-handler-proxy
• example-raw-websocket-handler-proxy-vercel
• example-raw-websocket-handler-vercel
• example-react
• example-react-vercel
• sandbox
• sandbox-coding-agent
• sandbox-coding-agent-vercel
• sandbox-vercel
• scheduling
• scheduling-vercel
• example-sqlite-drizzle
• example-sqlite-raw
• state
• state-vercel
• example-stream
• example-stream-vercel
• example-trpc

@rivetkit/cloudflare-workers

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/cloudflare-workers@4316

@rivetkit/framework-base

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/framework-base@4316

@rivetkit/next-js

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/next-js@4316

@rivetkit/react

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/react@4316

rivetkit

pnpm add https://pkg.pr.new/rivet-dev/rivet/rivetkit@4316

@rivetkit/sql-loader

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/sql-loader@4316

@rivetkit/sqlite-vfs

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/sqlite-vfs@4316

@rivetkit/traces

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/traces@4316

@rivetkit/workflow-engine

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/workflow-engine@4316

@rivetkit/virtual-websocket

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/virtual-websocket@4316

@rivetkit/engine-runner

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/engine-runner@4316

@rivetkit/engine-runner-protocol

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/engine-runner-protocol@4316

commit: a9c0244