Procedures don't trigger view changes

[onx2]

Cross posting here for visibility and tracking. Original post: https://discord.com/channels/1037340874172014652/1472332044460622006

TL;DR; A procedure with the same db update as a reducer does not trigger a change to a view that uses that data.

[clockwork-labs-bot]

Root Cause Analysis

The bug: Procedures that modify tables via with_tx don't trigger view re-materialization. Subscribers to views see no updates until a subsequent reducer happens to call call_views_with_tx.

Why it happens:

• Reducer path: call_reducer_with_tx → call_views_with_tx() (re-materializes dirty views in the same tx) → commit_and_broadcast_event
• Procedure path: commit_mutable_tx (in instance_env.rs) → commit_and_broadcast_event — views are never re-materialized

The procedure commits transactions via the procedure_commit_mut_tx syscall, which runs inside the wasm instance. call_views_with_tx requires calling wasm view functions (__call_view__ / __call_view_anon__), which can't be done from within a host function... unless you use re-entrant wasm calls.

Correct fix — re-entrant view evaluation during procedure_commit_mut_tx:

1. In procedure_commit_mut_tx, check tx.view_for_update() for dirty views
2. For each dirty view, call __call_view__ / __call_view_anon__ re-entrantly via the Caller (wasmtime supports this — stack grows with nested call)
3. Process view results (ViewResult::Rows or ViewResult::RawSql), update view backing tables in the same tx
4. Commit the tx with both data writes and view updates together
5. Broadcast to subscribers

What's needed to implement this:

• Plumb ModuleDef (view definitions) and __call_view__ / __call_view_anon__ function handles into WasmInstanceEnv / InstanceEnv (currently these live in InstanceCommon in module_host_actor.rs)
• Replicate view result processing logic (currently in call_view_with_tx) for use within the syscall
• Handle V8 equivalently (V8 also supports re-entrant calls)
• Energy/timing accounting for view evaluation during procedure commits
• Error handling if a view function traps mid-commit

Key files:

• crates/core/src/host/instance_env.rs — commit_mutable_tx (L744-L775)
• crates/core/src/host/wasm_common/module_host_actor.rs — call_views_with_tx (L1319), call_view_with_tx (L1111), execute_view_calls (L1353)
• crates/core/src/host/wasmtime/wasmtime_module.rs — call_procedure (L521)
• crates/core/src/host/wasmtime/wasm_instance_env.rs — procedure_commit_mut_tx (L1593)
• crates/core/src/host/v8/syscall/common.rs — procedure_commit_mut_tx (L653)

[bfops]

Thank you for reporting this! We're working on looking into it.