HarperFast / HarperFast/harper

Windows CI shard 2/6 native abort() during component load with file watchers

Open
#2,234 1 comment 0 reactions 1 assignee Claimed by @kriszyp View on GitHub
area:ci area:components bug
Dominant language
JavaScript
Stars
89
Forks
10
Avg merge
2d 6h
Merged PRs (30d)
200

Description

## Problem

Windows integration shard 2/6 terminates Harper with a native libuv abort while component file watchers start. The CI health probe then reports `ECONNREFUSED` because the Harper process has exited, not because startup is slow or a test assertion failed.

## Evidence

In the `harper-server-logs-windows-shard-2` artifact from [CI run 32218666106](https://github.com/HarperFast/harper/actions/runs/32218666106), the Harper process's `stderr.log` ends with:

```text
Assertion failed: !_wcsnicmp(filename, dir, dirlen), file src\win\fs-event.c, line 72
```

This is libuv's `uv__relative_path`, reached from `uv_fs_event_start` when a file watch starts. `hdb.log` places the abort during component load as that component's file watchers start. This is Harper's own stderr; child-process output is tagged separately in `hdb.log`.

The failure is branch-attributable: 11/11 commits on `kris/deploy-peer-rollback` fail this shard, while `main` is 12/12 clean on the same shard.

## Follow-up

No Windows environment is available to bisect this further. This needs a Windows-capable reproduction and fix; it is intentionally not being addressed in PR #2066.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.