Uh oh!
There was an error while loading. Please reload this page.
src: define O_SYNC, O_DSYNC and O_DIRECT on Windows - #64707
Merged
Conversation
PickBasforce-pushed
the
win-fix-fs-constants
branch
2 times, most recently
from
July 24, 2026 08:20
16f53e6 to
d45f76dCompareSigned-off-by: Kirill Saied <sayed.kirill@gmail.com>
PickBasforce-pushed
the
win-fix-fs-constants
branch
from
July 24, 2026 08:28
d45f76d to
3171100CompareCodecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@## main #64707 +/- ##
==========================================
- Coverage 90.24% 90.12% -0.13%
==========================================
Files 739 741 +2 Lines 241676 242251 +575 Branches 45544 45621 +77 ==========================================
+ Hits 218102 218329 +227 - Misses 15101 15427 +326 - Partials 8473 8495 +22
🚀 New features to boost your workflow:
|
StefanStojanovic
approved these changes
Aug 18, 2026
nodejs-github-bot
commented
Aug 18, 2026
Collaborator
nodejs-github-bot
commented
Aug 19, 2026
Collaborator
nodejs-github-bot
commented
Aug 19, 2026
Collaborator
jasnell
approved these changes
Aug 20, 2026
Uh oh!
There was an error while loading. Please reload this page.
nodejs-github-bot
commented
Aug 20, 2026
Collaborator
Landed in 6d60352 |
aduh95 pushed a commit
that referenced
this pull request
Aug 25, 2026
Signed-off-by: Kirill Saied <sayed.kirill@gmail.com> PR-URL: #64707 Reviewed-By: Stefan Stojanovic <stefan.stojanovic@janeasystems.com> Reviewed-By: James M Snell <jasnell@gmail.com>
aduh95 pushed a commit
that referenced
this pull request
Aug 25, 2026
Signed-off-by: Kirill Saied <sayed.kirill@gmail.com> PR-URL: #64707 Reviewed-By: Stefan Stojanovic <stefan.stojanovic@janeasystems.com> Reviewed-By: James M Snell <jasnell@gmail.com>
1 task
sarayev added a commit
to aws-amplify/amplify-backend
that referenced
this pull request
Sep 1, 2026
## Summary Raises the `aws-cdk-lib` peer dependency floor from `^2.234.1` to `^2.254.0` across all packages and refreshes the lockfile (now resolves `aws-cdk-lib` to `2.267.0`). ## Why On Windows with recent Node.js releases, CDK asset fingerprinting crashes with `EINVAL` because `fs.openSync` is invoked with the `O_SYNC | O_DSYNC` flag combination, which Node rejects on that platform. This makes the Windows unit/coverage job fully red while Linux and macOS stay green. The crash was fixed upstream in aws-cdk and first released in `aws-cdk-lib` 2.254.0. Bumping the floor to `^2.254.0` pulls in the fix. - Upstream issue: aws/aws-cdk#38692 - Upstream fix (PR): aws/aws-cdk#37802 (released in `aws-cdk-lib` 2.254.0) - Related Node.js change: nodejs/node#64707 ## What changed - Bumped `aws-cdk-lib` from `^2.234.1` to `^2.254.0` in all 16 `packages/*/package.json` files (peer/dep/devDep as applicable). No other dependencies changed. - Refreshed `package-lock.json` — `aws-cdk-lib` now resolves to `2.267.0` (latest within the range), deduped across the workspace. - Updated `packages/create-amplify/src/default_packages.json` so the default `aws-cdk-lib` pin for new projects matches the lockfile (generated via `npm run update:create-amplify-deps`). - Added a changeset (patch bump for affected published packages). ## How tested - `npm install` + `npm run build` — clean. - Ran the unit/integration suites. All CDK-heavy suites pass (in-memory CDK synthesis integration tests, `auth-construct`, `backend-storage`, `backend-data`): 280/280. - No CDK-generated construct snapshots/logical IDs changed as a result of the bump, so no snapshot regeneration was needed. - `check:package-lock`, `check:package-json`, `check:api`, and prettier all pass. The only local failures were in `platform-core` config/telemetry tests that write to a real user-profile path; these fail identically with and without this change in the local sandboxed environment (permission-restricted `~` path) and are unrelated to the CDK bump. --------- Co-authored-by: sarayev <sarayev@amazon.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
src: define O_SYNC, O_DSYNC and O_DIRECT on Windows
These POSIX open-flag names have no macro in the Windows C runtime, so they were missing from
fs.constantson Windows and got silently dropped when passed tofs.open(). libuv already honors the underlying flags (FILE_FLAG_WRITE_THROUGHfor sync,FILE_FLAG_NO_BUFFERINGfor direct), so this just exposes the constants under their portable names wired to libuv's values.Portable code requesting synchronized or unbuffered I/O now works on Windows instead of losing the flag.