-
Notifications
You must be signed in to change notification settings - Fork 4.7k
resolver: restore package_manager.log after resolve to avoid dangling stack pointer #31020
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
da598a4
resolver: restore package_manager.log after resolve to avoid dangling…
robobun 448fad0
[autofix.ci] apply automated fixes
autofix-ci[bot] 1d93629
also swap pm.log in transpile_source_code; use --install flag in test
robobun 4583009
ci: retrigger
robobun File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
59 changes: 59 additions & 0 deletions
59
test/js/bun/resolve/resolve-autoinstall-log-dangling.test.ts
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,59 @@ | ||
| import { expect, test } from "bun:test"; | ||
| import { bunEnv, bunExe, tempDir } from "harness"; | ||
|
|
||
| // When the runtime resolver's auto-install path lazily creates the | ||
| // PackageManager, it snapshots `resolver.log` into `pm.log`. If the | ||
| // PackageManager is created while the resolver log is pointed at a | ||
| // stack-local `Log` inside `resolveMaybeNeedsTrailingSlash`, `pm.log` must be | ||
| // restored to the VM log before returning, otherwise the next resolve at a | ||
| // different stack depth dereferences dead stack memory when the HTTP task | ||
| // fails and calls `manager.log_mut().add_error_fmt(...)`. | ||
| test("repeated failing auto-install resolves at varying stack depth don't read a dangling pm.log", async () => { | ||
| // Run from an empty dir so the resolver falls through to the auto-install | ||
| // path instead of stopping at the repo's own node_modules. | ||
| using dir = tempDir("resolve-autoinstall-log", {}); | ||
|
|
||
| const src = ` | ||
| const realm = new ShadowRealm(); | ||
| const variants = [ | ||
| () => realm.importValue("pkg-not-found-a", "x"), | ||
| () => (() => realm.importValue("pkg-not-found-b", "x"))(), | ||
| () => (() => (() => realm.importValue("pkg-not-found-c", "x"))())(), | ||
| () => { try { return realm.importValue("pkg-not-found-d", "x"); } finally {} }, | ||
| () => [realm.importValue("pkg-not-found-e", "x")][0], | ||
| () => import("pkg-not-found-f"), | ||
| () => (async () => realm.importValue("pkg-not-found-g", "x"))(), | ||
| ]; | ||
| for (let i = 0; i < 100; i++) { | ||
| for (const v of variants) { | ||
| try { | ||
| const p = v(); | ||
| if (p && p.catch) p.catch(() => {}); | ||
| } catch {} | ||
| } | ||
| } | ||
| Bun.gc(true); | ||
| console.log("ok"); | ||
| `; | ||
|
|
||
| await using proc = Bun.spawn({ | ||
| // Force the auto-install path (PackageManager lazy init inside the | ||
| // resolver) without hitting the network — the registry hostname is | ||
| // unroutable, so every enqueued manifest fetch fails fast and routes | ||
| // through `manager.log_mut()`. | ||
| cmd: [bunExe(), "--install=fallback", "-e", src], | ||
| cwd: String(dir), | ||
| env: { | ||
| ...bunEnv, | ||
| BUN_CONFIG_REGISTRY: "http://127.0.0.1:1", | ||
| }, | ||
| stdout: "pipe", | ||
| stderr: "pipe", | ||
| }); | ||
|
|
||
| const [stdout, stderr, exitCode] = await Promise.all([proc.stdout.text(), proc.stderr.text(), proc.exited]); | ||
|
|
||
| expect(stderr).toBe(""); | ||
| expect(stdout.trim()).toBe("ok"); | ||
| expect(exitCode).toBe(0); | ||
| }); |
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.