fix: optimize e2e actor path

[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-4551 environment in rivet-frontend

Service	Status	Web	Updated (UTC)
kitchen-sink	❌ Build Failed (View Logs)	Web	Apr 5, 2026 at 11:39 am
frontend-cloud	❌ Build Failed (View Logs)	Web	Apr 4, 2026 at 4:00 am
frontend-inspector	❌ Build Failed (View Logs)	Web	Apr 4, 2026 at 4:00 am
mcp-hub	✅ Success (View Logs)	Web	Apr 4, 2026 at 3:59 am
website	❌ Build Failed (View Logs)	Web	Apr 4, 2026 at 3:59 am
ladle	❌ Build Failed (View Logs)	Web	Apr 4, 2026 at 3:59 am

[MasterPtato]

• chore: remove global epoxy contention #4554
• feat: native SQLite backend via napi-rs with KV channel protocol #4496
• feat: actor query in gateway #4553
• feat: add sleep and reschedule endpoints for actors #4556
• fix: optimize e2e actor path #4551 👈 (View in Graphite)
• feat(pb): actor v1 to v2 migration #4548
• feat(envoy-client): fully flesh out tunnel impl #4547
• feat: basic rivetkit impl #4544
• feat: basic envoy tunnel impl #4534
• chore: envoy client #4521 : 1 other dependent PR (#4531 )
• feat(pb): actors v3 #4463
• feat(ups): implement queue subs #4486
• feat(cache): add in flight deduping #4459
• fix(cache): clean up lib #4457
• fix(config): allow configuring topo dcs via map, fix pg ssl mode config #4456
• fix(api): dont 500 on cross dc response #4449
• chore: update byte units on frontend #4444
• fix: runner alloc idx logic, api auth for actor get #4443
• main

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

[claude]

PR Review: fix: optimize e2e actor path

Summary

This PR reduces end-to-end actor path latency through namespace operation caching, reqwest client pre-warming, tracing improvements, an envoy client shutdown race fix, and new Sleep/Reallocate actor signals.

---

Potential Bugs

1. Debug /foo endpoint left in test-envoy
engine/sdks/typescript/test-envoy/src/index.ts contains a new app.post route that looks like debug scaffolding. If intentional, rename it to something meaningful.

2. Race condition: abort handler fires before envoy is assigned
envoy is declared inside a setTimeout callback, but the SSE abort handler references envoy with a non-null assertion. If the client disconnects before the 0ms timeout fires, envoy will be undefined at abort time. The assertion silently skips the shutdown call, meaning the underlying process may not be cleaned up on early disconnect. The same pattern exists in /api/rivet/start.

3. LOG_TIMESTAMP default flip is a silent behavioral change
Previously timestamps were opt-in to enable. Now they are opt-out to disable. Any existing environment relying on the old default will silently start emitting timestamps. Since this is test-envoy the impact is limited, but it should be noted in the PR description.

---

Code Quality

4. TODO without issue reference in sleep signal handler
packages/core/pegboard/src/protocol/mod.rs has a TODO comment with no tracking issue. When an actor is signaled to sleep during Allocating/Starting/GoingAway, the sleep intent is silently dropped. Link a tracking issue if this is a known limitation.

5. Main::Reallocate silent drop while Reallocating
A second Reallocate signal during an in-progress reallocation is silently dropped. Consider adding a tracing::debug! to make the drop observable, and clarify that Reallocating is distinct from Allocating.

6. Leftover console.log in test script
scripts/tests/actor_e2e.ts has two bare console.log(new Date().toISOString()) calls that duplicate the surrounding console.time/console.timeEnd instrumentation. These look like debug artifacts.

---

Performance

Namespace caching (good): Both namespace_get_local and namespace_resolve_for_name_local are now cached via fetch_all_json/fetch_one_json. Cache misses when namespace is not found correctly avoid polluting the cache with negative results.

Reqwest pre-warming (good): Eagerly initializing clients in Pools::create() matches the CLAUDE.md guidance to reuse rivet_pools::reqwest::client().

---

Minor

7. RUST_LOG=warn removal from engine-rocksdb-release.sh
The release script no longer sets RUST_LOG=warn, which may make release builds noisier. Confirm this is intentional and not a debugging leftover.

8. pnpm-lock.yaml specifier mismatch for @types/bun
Lockfile records specifier: latest but package.json has a pinned version. The resolved version matches but the specifier mismatch could cause pnpm install to silently update on the next run. Regenerate the lockfile.

---

Convention Checks (CLAUDE.md)

• rivet.dev domain: no violations
• Structured logging: all new tracing:: calls use structured fields correctly
• No new Arc<Mutex> instances introduced
• Workspace dependencies: no new Cargo deps added outside workspace

---

Overall this is a solid performance improvement. Main items to address before merge: remove the /foo debug endpoint, clean up the console.log timestamp artifacts, and confirm the RUST_LOG removal is intentional. The sleep/reallocate signal edge cases and abort handler race are worth tracking issues even if not merge-blocking.

[NathanFlurry]

Merge activity

• Apr 5, 11:11 AM UTC: A user started a stack merge that includes this pull request via Graphite.
• Apr 5, 11:39 AM UTC: Graphite rebased this pull request as part of a merge.
• Apr 5, 11:40 AM UTC: @NathanFlurry merged this pull request with Graphite.