-
Notifications
You must be signed in to change notification settings - Fork 5k
postgres: fix do_run error-path leaks (poll_ref hang + query/statement refs) #32464
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
+86
−74
Merged
Changes from 3 commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
ecb375a
postgres: release the speculative query ref on every do_run error exit
alii 8fe4fd2
postgres: ref poll_ref only after do_run enqueues the request
alii 7d0f2e8
test(sql): use real postgres container for the poll_ref regression test
alii df97fee
test(sql): surface stderr in the poll_ref fixture failure diff
alii f2b76ba
test(sql): move the poll_ref regression into sql-onconnect-onclose-throw
alii 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
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
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,37 @@ | ||
| // PostgresSQLQuery.do_run refs the connection's poll_ref KeepAlive. KeepAlive | ||
| // is a two-state flag, not a counter, so when this query is the only in-flight | ||
| // work the call flips Inactive -> Active. When do_run then returns early with | ||
| // a synchronous error (bad binding, signature-generation failure, OOM during | ||
| // enqueue, ...) the poll_ref must not be left Active: nothing else on the | ||
| // connection will touch it until the next server message, so the event loop | ||
| // stays pinned and the process never exits. | ||
| // | ||
| // The fixture connects to a real Postgres, lets the connection go idle, then | ||
| // issues a query whose binding is rejected synchronously before anything is | ||
| // written. It must print the rejection and exit on its own. | ||
|
|
||
| import { expect, test } from "bun:test"; | ||
| import { bunEnv, bunExe, describeWithContainer } from "harness"; | ||
| import path from "node:path"; | ||
|
|
||
| describeWithContainer("postgres", { image: "postgres_plain" }, container => { | ||
| test("postgres: synchronous do_run failure does not pin the event loop", async () => { | ||
| await container.ready; | ||
| const url = `postgres://bun_sql_test@${container.host}:${container.port}/bun_sql_test`; | ||
|
|
||
| await using proc = Bun.spawn({ | ||
| cmd: [bunExe(), path.join(import.meta.dir, "sql-postgres-run-error-pollref-fixture.ts")], | ||
| env: { ...bunEnv, DATABASE_URL: url }, | ||
| stdout: "pipe", | ||
| stderr: "pipe", | ||
| }); | ||
|
|
||
| const [stdout, stderr, exitCode] = await Promise.all([proc.stdout.text(), proc.stderr.text(), proc.exited]); | ||
| void stderr; | ||
|
Check warning on line 30 in test/js/sql/sql-postgres-run-error-pollref.test.ts
|
||
|
|
||
| expect(stdout).toBe("rejected:ERR_INVALID_ARG_TYPE\n"); | ||
| // exited on its own, not killed by the runner's timeout | ||
| expect(proc.signalCode).toBeNull(); | ||
| 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.