windows builds fail very intermittently on various issues

Repository metrics

Stars

132 stars (132 stars)

PR merge metrics

PR metrics pending (PR metrics pending)

Description

node:internal/fs/promises:623
  return await PromisePrototypeThen(
         ^

Error: EBUSY: resource busy or locked, copyfile 'D:\a\greenwood\greenwood\www\assets\link.png' -> 'D:\a\greenwood\greenwood\public\assets\link.1200825667.png'
    at async Object.copyFile (node:internal/fs/promises:623:10) {
  errno: -4082,
  code: 'EBUSY',
  syscall: 'copyfile',
  path: 'D:\\a\\greenwood\\greenwood\\www\\assets\\link.png',
  dest: 'D:\\a\\greenwood\\greenwood\\public\\assets\\link.1200825667.png'
}

Node.js v22.19.0

Contributor guide

Research direction

Investigate the EBUSY error on Windows during file copy. Check if the source file is locked by another process (e.g., antivirus, editor) or if there is a race condition. Consider adding retry logic or using a different copy method that handles Windows file locking.

Tech stack

javascript

Domain

build system

Issue type

Bug

DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.

2

Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.

1-3 hours

Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.

Active

ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.

Clear

Prerequisites

GitNode.js

Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.

65