• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

wegamekinglc / calc-flow / 32910460747
94%

Build:
DEFAULT BRANCH: main
Ran 26 Aug 2026 12:23AM UTC
Jobs 3
Files 110
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

25 Aug 2026 11:22PM UTC coverage: 91.294% (+0.04%) from 91.25%
32910460747

push

github

web-flow
feat: compile symbolic row expressions (#194)

* feat: compile symbolic row expressions

Lower row-local symbolic programs to strict project-v3 expression
nodes with deterministic fusion and CSE: literal, field, arithmetic,
comparison, boolean, where, coalesce, log/exp/sqrt/abs/clip/cast, and
select/filter/with_columns resolve into one fused node per output,
with shared non-trivial subexpressions materialized once through
tiered CSE nodes. The Rust graph compiler keeps final port, schema,
and topology validation; generated node IDs and plan fingerprints are
deterministic and carry strict JSON only.

Stream compilation now rejects read-only queries that call volatile
built-in functions, so the expression/sql operator deterministic and
replay-safe capability claims stay truthful (SCE-04 handoff). The
portable timestamp[us, UTC] spelling is accepted in port schemas.

Stateful rolling, cross-section, event-window, array, and
static-parameter declarations fail loudly with the frozen
unknown_primitive_version issue code in both modes; a stream
aggregate or SQL window is never silently made batch-local. Batch and
stream outputs are verified equivalent across 1/7/1000-row
segmentation, and execution performs zero symbolic Python calls.

Co-authored-by: multica-agent <github@multica.ai>

* docs: reconcile symbolic compilation docs with SCE-05 behavior

PR #194 review confirmed two wording errors in docs/python-api.md:
array outputs are rejected with unknown_primitive_version in batch
mode but earlier, at analysis, with unbounded_state in stream mode
(SCE-03 stream-safety rule), and the volatile guard resolves against
the built-in default function registry, not a runtime registry. The
same review confirmed the capability paragraph was stale: volatile
built-in SQL functions such as random() in read-only SELECTs are now
rejected at stream compile time, not outside validation.

The sweep also reconciled lagging surfaces: introduction.md and
api-reference.md still ... (continued)

531 of 553 new or added lines in 9 files covered. (96.02%)

10 existing lines in 1 file now uncovered.

65318 of 71547 relevant lines covered (91.29%)

3318.94 hits per line

Uncovered Changes

Lines Coverage ∆ File
11
95.4
python/calc_flow/symbolic/lower.py
8
96.1
-3.9% crates/calc-flow/src/expression.rs
2
93.08
0.38% crates/calc-flow/src/pipeline/stream.rs
1
98.9
python/calc_flow/symbolic/optimizer.py

Coverage Regressions

Lines Coverage ∆ File
10
80.13
-3.15% crates/calc-flow-python/src/runtime.rs
Jobs
ID Job ID Ran Files Coverage
1 rust - 32910460747.1 26 Aug 2026 12:57AM UTC 84
91.26
GitHub Action Run
2 studio - 32910460747.2 26 Aug 2026 12:23AM UTC 5
89.41
GitHub Action Run
3 python - 32910460747.3 26 Aug 2026 12:23AM UTC 21
92.74
GitHub Action Run
Source Files on build 32910460747
  • Tree
  • List 110
  • Changed 10
  • Source Changed 6
  • Coverage Changed 10
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • Github Actions Build #32910460747
  • 9e818368 on github
  • Prev Build on main (#32910275980)
  • Next Build on main (#32990284741)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE TRIAL · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc