:hedgehog: PostHog is the leading platform for building self-driving products. Our developer tools – AI observability, analytics, session replay, flags, experiments, error tracking, logs, and more – capture all the context agents need to diagnose problems, uncover opportunities, and ship fixes. Steer it all from Slack, web, desktop, or the MCP.
hogvm
A Rust implementation of the Hog virtual machine, at behavioral parity with the Node reference VM
(@posthog/hogvm, common/hogvm/typescript). Parity is enforced by tests/parity.rs (the full
program corpus, diffed against committed Node output) and tests/stl_parity.rs (per-STL cases).
Execution modes
sync_execute— synchronous, boolean/value-returning evaluation. This is what the production consumers use (cymbalerror-tracking rule evaluation,cohort-stream-processor), and it is at parity with the reference VM, except underwith_boolean_text_equality, which the cohort evaluator turns on to match ClickHouse.execute_resumable/resume— the suspendable-coroutine model for CDP hog functions (destinations): on a registered async function (fetch,sleep, …) the VM suspends and returns a serializableVmSnapshot; the host performs the side effect and resumes.
Node interop status (VmSnapshot / VMState)
The snapshot JSON is designed to be byte-compatible with the reference VM's VMState so a snapshot
can round-trip through either VM. Rust↔Rust round-trips are covered by tests/async_resume.rs.
Exchanging state with the live Node VM has known encoding gaps — tracked in
#67272, surfaced in review of
#66631:
- Tuples aren't flattened like Node. Rust encodes tuples as
{"__hogTuple__": true, "items": [...]}; Node'sgetVMStateflattens them to bare arrays. A live tuple in a snapshot therefore doesn't survive a cross-VM round-trip. - JSON number int/float ambiguity. Rust deserializes an integer-valued JSON number (
5) as an integer; Node always yields a float. - Cumulative timeout not preserved across resume.
drive_resumablerestarts the step counter each resume and hardcodessync_duration: 0; Node bounds cumulative work by wall-clock across resumes. - Header-inclusive ip for module chunks. A snapshot taken while suspended inside an STL hog
module (e.g. an async call within an
arrayMapcallback) would resume at the wrong ip in Node.
None of these affect the sync path — they only matter when exchanging VMState with the Node VM,
which is the live-Node cross-check follow-up.