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

DanielXMoore / Civet / 24455043415
96%

Build:
DEFAULT BRANCH: main
Ran 15 Apr 2026 12:43PM UTC
Jobs 1
Files 42
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

15 Apr 2026 12:41PM UTC coverage: 95.378% (+0.001%) from 95.377%
24455043415

push

github

web-flow
auto import (#1956)

* auto import

* ci is much slower for timeouts

* increase completion timeout

* increase diagnostic timeout

* scoping tsconfig to decrease timeouts

* e2e test warmup

* add instrumented warmup to e2e tests for CI debugging

- warmup polls for auto-import readiness before tests run
- timing logs to stderr so we can see exactly what's slow on CI
- avoid opening valid.civet in warmup to not steal diagnostics event
- keep tsconfig types:[] and include to reduce TS program size

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

* fix e2e timeouts: proper warmup, increased CI timeouts

Root cause: each `executeCompletionItemProvider` with 1100 resolves takes
~7.5s on Windows CI, meaning only 1 attempt fits in an 8s poll timeout.

- Warmup opens consumer.civet (not valid.civet) to avoid stealing
  diagnostics event, polls cheaply for basic completions
- Poll timeouts based on CI data: 15s Linux, 30s Windows
- Mocha timeouts: 20s Linux, 45s Windows
- 1s poll interval for resolved completion calls
- Keep tsconfig types:[] and include to reduce TS program size
- Timing logs to stderr for CI debugging

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

* add auto-import debug logging for Windows CI investigation

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

* increase server test timeout for Windows CI

TSService startup can exceed mocha's 2000ms default on Windows CI.
Also keep e2e auto-import debug logging for this run.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

* fix auto-import on Windows: canonicalize TS code-action paths

Root cause: TS returns code-action file paths with forward slashes
(e.g. D:/a/Civet/...) but the LSP server uses OS-native backslash
paths on Windows. The === comparison in onCompletionResolve always
failed, so additionalTextEdits were never populated on Windows.

Fix: extract getCanonicalFileName to shared util and use it ... (continued)

4258 of 4641 branches covered (91.75%)

Branch coverage included in aggregate %.

20421 of 21234 relevant lines covered (96.17%)

47414.62 hits per line

Jobs
ID Job ID Ran Files Coverage
1 24455043415.1 15 Apr 2026 12:43PM UTC 42
95.38
GitHub Action Run
Source Files on build 24455043415
  • Tree
  • List 42
  • Changed 15
  • Source Changed 0
  • Coverage Changed 15
Coverage ∆ File Lines Relevant Covered Missed Hits/Line Branch Hits Branch Misses
  • Back to Repo
  • Github Actions Build #24455043415
  • 8fc3ef32 on github
  • Prev Build on main (#24435481162)
  • Next Build on main (#24487810047)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc