You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Uncaught error text in Slice.evalSandbox repeats the source location #45
The error text for an uncaught exception in Slice.evalSandbox repeats the source location on the stack frame line.
Repro (throw.js)
constr=Slice.evalSandbox('throw new Error("boom")');console.log(r.error);
slice run throw.js
Expected
Uncaught Error: boom (unknown at :2:7)
at <main> (unknown at :2:7)
Actual
Uncaught Error: boom (unknown at :2:7)
at <main> (unknown at :2:7) (unknown at :2:7)
The same text is returned in the error field of slice mcpslice_eval_ts.
Minor, but this text is shown directly to users and agents, and the line number :2 for a one-line snippet suggests the reported position includes an internal wrapper line, which may also be worth correcting.
Environment
Version: v0.10.6, commit c6b3e77
OS: Windows 11 x64, release build (cargo build --release)
Activity
siktec-lab commentedon Nov 10, 2026
Fixed in #46 (
2c3e16a):finish_boa_compartment_executionwhenraw_error stack frames already include(unknown at ...).SLICEBOA{wrappers so single-lineSlice.evalSandboxsnippets report line:1:instead of:2:.JSON.parseto returnUncaught SyntaxErroron malformed JSON.