Issues

The nightly is red

nightly-failure

#4062

· github-actions opened

on Sep 18, 2026

MCP: `grep_usage`/`outline` resolve a relative `directory`/`glob` against the daslang checkout, not the project the server runs in - `Found 0 matches` from any external project

#4008

· lookibed opened

on Sep 11, 2026

DAP: `evaluate` reports a failed evaluation as `success: true` with the diagnostic in `body.result`, and fills `type` only when the evaluation failed

#4007

· lookibed opened

on Sep 11, 2026

DAP: `evaluate` of any non-identifier expression is answered twice - the second response carries `body: null`, and the bridge hands the client that one

#4006

· lookibed opened

on Sep 11, 2026

v0.6.4-RC2: standalone -ctx is unusable: a required module's initialized global fails emission, the emitted InitGlobalVar does not link, and a context that does link never runs its initializers

#3967

· lookibed opened

on Sep 8, 2026

dasllama-server: GC frame-attribution exception leaves JIT server alive but unresponsive

#3940

· borisbat opened

on Sep 5, 2026

interpreter: 'can't delete locked array' after reading an element of a scoped array<array<string>> - lock leak in a fused at permutation, host-dependent

#3923

· borisbat opened

on Sep 2, 2026

auto-inline: an annotated block literal inlines anyway, and the splice drops its annotations

#3752

· borisbat opened

on Aug 16, 2026

heap_collect(true, false) mid-loop frees strings still live in the caller's frame — use-after-free through Release-fused frames

#3734

· borisbat opened

on Aug 14, 2026

Compiler SIGSEGV instead of a diagnostic on a stranded lpipe() after return

#3728

· aleksisch opened

on Aug 14, 2026

JIT: %json~ literal containing an array builds as {} (+ heap corruption at exit in the minimal repro); context-dependent

#3690

· borisbat opened

on Aug 11, 2026

test_sha_256 fails full-AOT with error[50101] on a clean build — likely missing AOT registration

#3627

· borisbat opened

on Aug 4, 2026

Navigation Menu

All issues

The nightly is red

MCP: `grep_usage`/`outline` resolve a relative `directory`/`glob` against the daslang checkout, not the project the server runs in - `Found 0 matches` from any external project

DAP: `evaluate` reports a failed evaluation as `success: true` with the diagnostic in `body.result`, and fills `type` only when the evaluation failed

DAP: `evaluate` of any non-identifier expression is answered twice - the second response carries `body: null`, and the bridge hands the client that one

v0.6.4-RC2: standalone -ctx is unusable: a required module's initialized global fails emission, the emitted InitGlobalVar does not link, and a context that does link never runs its initializers

dasllama-server: GC frame-attribution exception leaves JIT server alive but unresponsive

interpreter: 'can't delete locked array' after reading an element of a scoped array<array<string>> - lock leak in a fused at permutation, host-dependent

auto-inline: an annotated block literal inlines anyway, and the splice drops its annotations

heap_collect(true, false) mid-loop frees strings still live in the caller's frame — use-after-free through Release-fused frames

Compiler SIGSEGV instead of a diagnostic on a stranded lpipe() after return

JIT: %json~ literal containing an array builds as {} (+ heap corruption at exit in the minimal repro); context-dependent

test_sha_256 fails full-AOT with error[50101] on a clean build — likely missing AOT registration

Search results