You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
main build red: conflict markers left in native_module.rs after diagnostics_channel tail APIs #3864
21246c8c9 hotfix: remove unresolved conflict markers from #3818/#3829 merges (#3863)
cargo build --release -p perry -p perry-runtime -p perry-stdlib is still red. The earlier cjs_default_export_value hunk appears fixed, but another conflict marker remains in crates/perry-runtime/src/object/native_module.rs around namespace keys:
error: expected one of `!`, `(`, `+`, `::`, `<`, `>`, or `as`, found `"punycode"`
--> crates/perry-runtime/src/object/native_module.rs:1329:9
|
1328 | <<<<<<< HEAD
| - expected one of 7 possible tokens
1329 | "punycode" => Some(PUNYCODE_NAMESPACE_KEYS),
| ^^^^^^^^^^ unexpected token
This still blocks current-main Node API parity evidence; I am continuing the compatibility sweep on the last buildable main and labeling evidence accordingly until origin/main builds again.
I am taking this with #3868 as a focused native-module surface cleanup. Planned scope: remove the remaining committed conflict-marker hunk in native_module.rs, preserve both punycode and timers namespace keys, and verify the repaired base while also fixing the related node:sys default alias identity path.
Implemented in #3874. The PR removes the remaining committed conflict-marker hunk in native_module.rs, preserves both punycode and timers namespace keys, and verifies that the release build succeeds plus the diagnostics_channel tail fixtures from #3858 still pass.
Activity
andrewtdiz commentedon May 31, 2026
Update after the hotfix on current
origin/main:cargo build --release -p perry -p perry-runtime -p perry-stdlibis still red. The earliercjs_default_export_valuehunk appears fixed, but another conflict marker remains incrates/perry-runtime/src/object/native_module.rsaround namespace keys:Source excerpt:
This still blocks current-main Node API parity evidence; I am continuing the compatibility sweep on the last buildable main and labeling evidence accordingly until
origin/mainbuilds again.andrewtdiz commentedon May 31, 2026
I am taking this with #3868 as a focused native-module surface cleanup. Planned scope: remove the remaining committed conflict-marker hunk in
native_module.rs, preserve bothpunycodeandtimersnamespace keys, and verify the repaired base while also fixing the relatednode:sysdefault alias identity path.andrewtdiz commentedon May 31, 2026
Implemented in #3874. The PR removes the remaining committed conflict-marker hunk in
native_module.rs, preserves bothpunycodeandtimersnamespace keys, and verifies that the release build succeeds plus the diagnostics_channel tail fixtures from #3858 still pass.