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

Alan-Jowett / LexonGraph / 27157335045
82%

Build:
DEFAULT BRANCH: main
Ran 08 Jun 2026 06:08PM UTC
Jobs 1
Files 13
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

08 Jun 2026 06:07PM UTC coverage: 84.891% (+0.2%) from 84.697%
27157335045

push

github

web-flow
Add real in-phase progress counts to streaming status (#72)

* Add real in-phase progress counts to streaming status

Extend the streaming indexer status observer to report explicit phase total, completed, and remaining counts with phase-specific semantics. Update spec traceability and validation coverage for the observer contract.

Traceability: REQ-STREAM-INDEXER-022, REQ-STREAM-INDEXER-023, REQ-STREAM-INDEXER-039; DSG-STREAM-INDEXER-017, DSG-STREAM-INDEXER-029; VAL-STREAM-INDEXER-023, VAL-STREAM-INDEXER-036.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Address PR feedback on progress counts

Align the spec text to the planning-oriented status phases, preserve the item_count compatibility field, wire planning-pass progress into heartbeat updates, and rename the VAL-036 verification test for traceability.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Refine planning progress count semantics

Keep PlanningPass counts honest by treating live measurable progress as stage-scoped rather than aggregating overlapping recursive work into misleading pass-wide partial counts. Also compute remaining_unit_count with checked subtraction so invalid states are surfaced instead of silently saturated.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Tighten progress count invariant assertions

Require remaining_unit_count to be present whenever phase_total_unit_count is known, and require it to be absent when the total is unknown.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Preserve legacy item_count observer semantics

Keep item_count stable as a compatibility field instead of deriving it generically from the new progress counts. In particular, BottomUpAssembly continues to report the input item cardinality for the layer while the *_unit_count fields remain the canonical progress contract.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

... (continued)

214 of 215 new or added lines in 1 file covered. (99.53%)

327 existing lines in 1 file now uncovered.

6405 of 7545 relevant lines covered (84.89%)

165.24 hits per line

Uncovered Changes

Lines Coverage ∆ File
1
80.18
0.92% crates/lexongraph-streaming-indexer/src/lib.rs

Coverage Regressions

Lines Coverage ∆ File
327
80.18
0.92% crates/lexongraph-streaming-indexer/src/lib.rs
Jobs
ID Job ID Ran Files Coverage
1 27157335045.1 08 Jun 2026 06:08PM UTC 13
84.89
GitHub Action Run
Source Files on build 27157335045
  • Tree
  • List 13
  • Changed 1
  • Source Changed 1
  • Coverage Changed 1
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • Github Actions Build #27157335045
  • 9f977ca7 on github
  • Prev Build on main (#27151036135)
  • Next Build on main (#27171287755)
  • Delete
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