Fork/feat/swap pgboss for graphile worker by arielweinberger · Pull Request #474 · vercel/workflow

arielweinberger · 2025-12-01T20:03:07Z

No description provided.

changeset-bot · 2025-12-01T20:03:10Z

⚠️ No Changeset found

Latest commit: fc8d436

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

vercel · 2025-12-01T20:03:16Z

@arielweinberger is attempting to deploy a commit to the Vercel Labs Team on Vercel.

A member of the Team first needs to authorize it.

vercel · 2025-12-01T20:10:51Z

+ if (runner) {
+ await runner.stop();
+ runner = null;
+ }
+ if (workerUtils) {
+ await workerUtils.release();
+ workerUtils = null;


Suggested change
if(runner){
awaitrunner.stop();
runner=null;
}
if(workerUtils){
awaitworkerUtils.release();
workerUtils=null;
try{
if(runner){
awaitrunner.stop();
runner=null;
}
}finally{
if(workerUtils){
awaitworkerUtils.release();
workerUtils=null;
}
The stop() method has a resource leak: if runner.stop() throws an exception, the workerUtils.release() cleanup code will never execute, leaving database connections open.
View Details
Analysis
Resource leak in queue.stop() when runner.stop() throws
What fails: The stop() method in packages/world-postgres/src/queue.ts (lines 170-179) does not guarantee workerUtils.release() cleanup if runner.stop() throws an exception. If an exception occurs during runner.stop(), workerUtils.release() never executes, leaving database connections open indefinitely.
How to reproduce: Any exception thrown by runner.stop() (e.g., "Runner is already stopped" if called on an already-stopped instance, or network errors during graceful shutdown) will skip the workerUtils.release() call.
// Current code - if runner.stop() throws, cleanup is skippedasyncstop(){if(runner){awaitrunner.stop();// If this throws, next line doesn't executerunner=null;}if(workerUtils){awaitworkerUtils.release();// Unreachable if runner.stop() throwsworkerUtils=null;}}
Result: Database connections managed by workerUtils remain open, causing a resource leak.
Expected:workerUtils.release() should execute regardless of whether runner.stop() succeeds or fails. Per graphile-worker documentation, release() is critical for cleaning up database connections, LISTEN/NOTIFY listeners, signal handlers, and job batch operations.
Fix: Use try-finally to ensure cleanup always occurs:
asyncstop(){try{if(runner){awaitrunner.stop();runner=null;}}finally{if(workerUtils){awaitworkerUtils.release();workerUtils=null;}}}

arielweinberger · 2025-12-01T20:03:07Z

No description provided.

changeset-bot · 2025-12-01T20:03:10Z

⚠️ No Changeset found

Latest commit: fc8d436

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

vercel · 2025-12-01T20:03:16Z

@arielweinberger is attempting to deploy a commit to the Vercel Labs Team on Vercel.

A member of the Team first needs to authorize it.

vercel · 2025-12-01T20:10:51Z

+ if (runner) {
+ await runner.stop();
+ runner = null;
+ }
+ if (workerUtils) {
+ await workerUtils.release();
+ workerUtils = null;


Suggested change
if(runner){
awaitrunner.stop();
runner=null;
}
if(workerUtils){
awaitworkerUtils.release();
workerUtils=null;
try{
if(runner){
awaitrunner.stop();
runner=null;
}
}finally{
if(workerUtils){
awaitworkerUtils.release();
workerUtils=null;
}
The stop() method has a resource leak: if runner.stop() throws an exception, the workerUtils.release() cleanup code will never execute, leaving database connections open.
View Details
Analysis
Resource leak in queue.stop() when runner.stop() throws
What fails: The stop() method in packages/world-postgres/src/queue.ts (lines 170-179) does not guarantee workerUtils.release() cleanup if runner.stop() throws an exception. If an exception occurs during runner.stop(), workerUtils.release() never executes, leaving database connections open indefinitely.
How to reproduce: Any exception thrown by runner.stop() (e.g., "Runner is already stopped" if called on an already-stopped instance, or network errors during graceful shutdown) will skip the workerUtils.release() call.
// Current code - if runner.stop() throws, cleanup is skippedasyncstop(){if(runner){awaitrunner.stop();// If this throws, next line doesn't executerunner=null;}if(workerUtils){awaitworkerUtils.release();// Unreachable if runner.stop() throwsworkerUtils=null;}}
Result: Database connections managed by workerUtils remain open, causing a resource leak.
Expected:workerUtils.release() should execute regardless of whether runner.stop() succeeds or fails. Per graphile-worker documentation, release() is critical for cleaning up database connections, LISTEN/NOTIFY listeners, signal handlers, and job batch operations.
Fix: Use try-finally to ensure cleanup always occurs:
asyncstop(){try{if(runner){awaitrunner.stop();runner=null;}}finally{if(workerUtils){awaitworkerUtils.release();workerUtils=null;}}}

arielweinberger · 2025-12-01T20:03:07Z

No description provided.

changeset-bot · 2025-12-01T20:03:10Z

⚠️ No Changeset found

Latest commit: fc8d436

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

vercel · 2025-12-01T20:03:16Z

@arielweinberger is attempting to deploy a commit to the Vercel Labs Team on Vercel.

A member of the Team first needs to authorize it.

vercel · 2025-12-01T20:10:51Z

+ if (runner) {
+ await runner.stop();
+ runner = null;
+ }
+ if (workerUtils) {
+ await workerUtils.release();
+ workerUtils = null;


Suggested change
if(runner){
awaitrunner.stop();
runner=null;
}
if(workerUtils){
awaitworkerUtils.release();
workerUtils=null;
try{
if(runner){
awaitrunner.stop();
runner=null;
}
}finally{
if(workerUtils){
awaitworkerUtils.release();
workerUtils=null;
}
The stop() method has a resource leak: if runner.stop() throws an exception, the workerUtils.release() cleanup code will never execute, leaving database connections open.
View Details
Analysis
Resource leak in queue.stop() when runner.stop() throws
What fails: The stop() method in packages/world-postgres/src/queue.ts (lines 170-179) does not guarantee workerUtils.release() cleanup if runner.stop() throws an exception. If an exception occurs during runner.stop(), workerUtils.release() never executes, leaving database connections open indefinitely.
How to reproduce: Any exception thrown by runner.stop() (e.g., "Runner is already stopped" if called on an already-stopped instance, or network errors during graceful shutdown) will skip the workerUtils.release() call.
// Current code - if runner.stop() throws, cleanup is skippedasyncstop(){if(runner){awaitrunner.stop();// If this throws, next line doesn't executerunner=null;}if(workerUtils){awaitworkerUtils.release();// Unreachable if runner.stop() throwsworkerUtils=null;}}
Result: Database connections managed by workerUtils remain open, causing a resource leak.
Expected:workerUtils.release() should execute regardless of whether runner.stop() succeeds or fails. Per graphile-worker documentation, release() is critical for cleaning up database connections, LISTEN/NOTIFY listeners, signal handlers, and job batch operations.
Fix: Use try-finally to ensure cleanup always occurs:
asyncstop(){try{if(runner){awaitrunner.stop();runner=null;}}finally{if(workerUtils){awaitworkerUtils.release();workerUtils=null;}}}

arielweinberger · 2025-12-01T20:03:07Z

No description provided.

changeset-bot · 2025-12-01T20:03:10Z

⚠️ No Changeset found

Latest commit: fc8d436

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

vercel · 2025-12-01T20:03:16Z

@arielweinberger is attempting to deploy a commit to the Vercel Labs Team on Vercel.

A member of the Team first needs to authorize it.

vercel · 2025-12-01T20:10:51Z

+ if (runner) {
+ await runner.stop();
+ runner = null;
+ }
+ if (workerUtils) {
+ await workerUtils.release();
+ workerUtils = null;


Suggested change
if(runner){
awaitrunner.stop();
runner=null;
}
if(workerUtils){
awaitworkerUtils.release();
workerUtils=null;
try{
if(runner){
awaitrunner.stop();
runner=null;
}
}finally{
if(workerUtils){
awaitworkerUtils.release();
workerUtils=null;
}
The stop() method has a resource leak: if runner.stop() throws an exception, the workerUtils.release() cleanup code will never execute, leaving database connections open.
View Details
Analysis
Resource leak in queue.stop() when runner.stop() throws
What fails: The stop() method in packages/world-postgres/src/queue.ts (lines 170-179) does not guarantee workerUtils.release() cleanup if runner.stop() throws an exception. If an exception occurs during runner.stop(), workerUtils.release() never executes, leaving database connections open indefinitely.
How to reproduce: Any exception thrown by runner.stop() (e.g., "Runner is already stopped" if called on an already-stopped instance, or network errors during graceful shutdown) will skip the workerUtils.release() call.
// Current code - if runner.stop() throws, cleanup is skippedasyncstop(){if(runner){awaitrunner.stop();// If this throws, next line doesn't executerunner=null;}if(workerUtils){awaitworkerUtils.release();// Unreachable if runner.stop() throwsworkerUtils=null;}}
Result: Database connections managed by workerUtils remain open, causing a resource leak.
Expected:workerUtils.release() should execute regardless of whether runner.stop() succeeds or fails. Per graphile-worker documentation, release() is critical for cleaning up database connections, LISTEN/NOTIFY listeners, signal handlers, and job batch operations.
Fix: Use try-finally to ensure cleanup always occurs:
asyncstop(){try{if(runner){awaitrunner.stop();runner=null;}}finally{if(workerUtils){awaitworkerUtils.release();workerUtils=null;}}}

arielweinberger · 2025-12-01T20:03:07Z

No description provided.

changeset-bot · 2025-12-01T20:03:10Z

⚠️ No Changeset found

Latest commit: fc8d436

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

vercel · 2025-12-01T20:03:16Z

@arielweinberger is attempting to deploy a commit to the Vercel Labs Team on Vercel.

A member of the Team first needs to authorize it.

vercel · 2025-12-01T20:10:51Z

+ if (runner) {
+ await runner.stop();
+ runner = null;
+ }
+ if (workerUtils) {
+ await workerUtils.release();
+ workerUtils = null;


Suggested change
if(runner){
awaitrunner.stop();
runner=null;
}
if(workerUtils){
awaitworkerUtils.release();
workerUtils=null;
try{
if(runner){
awaitrunner.stop();
runner=null;
}
}finally{
if(workerUtils){
awaitworkerUtils.release();
workerUtils=null;
}
The stop() method has a resource leak: if runner.stop() throws an exception, the workerUtils.release() cleanup code will never execute, leaving database connections open.
View Details
Analysis
Resource leak in queue.stop() when runner.stop() throws
What fails: The stop() method in packages/world-postgres/src/queue.ts (lines 170-179) does not guarantee workerUtils.release() cleanup if runner.stop() throws an exception. If an exception occurs during runner.stop(), workerUtils.release() never executes, leaving database connections open indefinitely.
How to reproduce: Any exception thrown by runner.stop() (e.g., "Runner is already stopped" if called on an already-stopped instance, or network errors during graceful shutdown) will skip the workerUtils.release() call.
// Current code - if runner.stop() throws, cleanup is skippedasyncstop(){if(runner){awaitrunner.stop();// If this throws, next line doesn't executerunner=null;}if(workerUtils){awaitworkerUtils.release();// Unreachable if runner.stop() throwsworkerUtils=null;}}
Result: Database connections managed by workerUtils remain open, causing a resource leak.
Expected:workerUtils.release() should execute regardless of whether runner.stop() succeeds or fails. Per graphile-worker documentation, release() is critical for cleaning up database connections, LISTEN/NOTIFY listeners, signal handlers, and job batch operations.
Fix: Use try-finally to ensure cleanup always occurs:
asyncstop(){try{if(runner){awaitrunner.stop();runner=null;}}finally{if(workerUtils){awaitworkerUtils.release();workerUtils=null;}}}

arielweinberger · 2025-12-01T20:03:07Z

No description provided.

changeset-bot · 2025-12-01T20:03:10Z

⚠️ No Changeset found

Latest commit: fc8d436

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

vercel · 2025-12-01T20:03:16Z

@arielweinberger is attempting to deploy a commit to the Vercel Labs Team on Vercel.

A member of the Team first needs to authorize it.

vercel · 2025-12-01T20:10:51Z

+ if (runner) {
+ await runner.stop();
+ runner = null;
+ }
+ if (workerUtils) {
+ await workerUtils.release();
+ workerUtils = null;


Suggested change
if(runner){
awaitrunner.stop();
runner=null;
}
if(workerUtils){
awaitworkerUtils.release();
workerUtils=null;
try{
if(runner){
awaitrunner.stop();
runner=null;
}
}finally{
if(workerUtils){
awaitworkerUtils.release();
workerUtils=null;
}
The stop() method has a resource leak: if runner.stop() throws an exception, the workerUtils.release() cleanup code will never execute, leaving database connections open.
View Details
Analysis
Resource leak in queue.stop() when runner.stop() throws
What fails: The stop() method in packages/world-postgres/src/queue.ts (lines 170-179) does not guarantee workerUtils.release() cleanup if runner.stop() throws an exception. If an exception occurs during runner.stop(), workerUtils.release() never executes, leaving database connections open indefinitely.
How to reproduce: Any exception thrown by runner.stop() (e.g., "Runner is already stopped" if called on an already-stopped instance, or network errors during graceful shutdown) will skip the workerUtils.release() call.
// Current code - if runner.stop() throws, cleanup is skippedasyncstop(){if(runner){awaitrunner.stop();// If this throws, next line doesn't executerunner=null;}if(workerUtils){awaitworkerUtils.release();// Unreachable if runner.stop() throwsworkerUtils=null;}}
Result: Database connections managed by workerUtils remain open, causing a resource leak.
Expected:workerUtils.release() should execute regardless of whether runner.stop() succeeds or fails. Per graphile-worker documentation, release() is critical for cleaning up database connections, LISTEN/NOTIFY listeners, signal handlers, and job batch operations.
Fix: Use try-finally to ensure cleanup always occurs:
asyncstop(){try{if(runner){awaitrunner.stop();runner=null;}}finally{if(workerUtils){awaitworkerUtils.release();workerUtils=null;}}}

arielweinberger · 2025-12-01T20:03:07Z

No description provided.

changeset-bot · 2025-12-01T20:03:10Z

⚠️ No Changeset found

Latest commit: fc8d436

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

vercel · 2025-12-01T20:03:16Z

@arielweinberger is attempting to deploy a commit to the Vercel Labs Team on Vercel.

A member of the Team first needs to authorize it.

vercel · 2025-12-01T20:10:51Z

+ if (runner) {
+ await runner.stop();
+ runner = null;
+ }
+ if (workerUtils) {
+ await workerUtils.release();
+ workerUtils = null;


Suggested change
if(runner){
awaitrunner.stop();
runner=null;
}
if(workerUtils){
awaitworkerUtils.release();
workerUtils=null;
try{
if(runner){
awaitrunner.stop();
runner=null;
}
}finally{
if(workerUtils){
awaitworkerUtils.release();
workerUtils=null;
}
The stop() method has a resource leak: if runner.stop() throws an exception, the workerUtils.release() cleanup code will never execute, leaving database connections open.
View Details
Analysis
Resource leak in queue.stop() when runner.stop() throws
What fails: The stop() method in packages/world-postgres/src/queue.ts (lines 170-179) does not guarantee workerUtils.release() cleanup if runner.stop() throws an exception. If an exception occurs during runner.stop(), workerUtils.release() never executes, leaving database connections open indefinitely.
How to reproduce: Any exception thrown by runner.stop() (e.g., "Runner is already stopped" if called on an already-stopped instance, or network errors during graceful shutdown) will skip the workerUtils.release() call.
// Current code - if runner.stop() throws, cleanup is skippedasyncstop(){if(runner){awaitrunner.stop();// If this throws, next line doesn't executerunner=null;}if(workerUtils){awaitworkerUtils.release();// Unreachable if runner.stop() throwsworkerUtils=null;}}
Result: Database connections managed by workerUtils remain open, causing a resource leak.
Expected:workerUtils.release() should execute regardless of whether runner.stop() succeeds or fails. Per graphile-worker documentation, release() is critical for cleaning up database connections, LISTEN/NOTIFY listeners, signal handlers, and job batch operations.
Fix: Use try-finally to ensure cleanup always occurs:
asyncstop(){try{if(runner){awaitrunner.stop();runner=null;}}finally{if(workerUtils){awaitworkerUtils.release();workerUtils=null;}}}

arielweinberger · 2025-12-01T20:03:07Z

No description provided.

changeset-bot · 2025-12-01T20:03:10Z

⚠️ No Changeset found

Latest commit: fc8d436

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

vercel · 2025-12-01T20:03:16Z

@arielweinberger is attempting to deploy a commit to the Vercel Labs Team on Vercel.

A member of the Team first needs to authorize it.

vercel · 2025-12-01T20:10:51Z

+ if (runner) {
+ await runner.stop();
+ runner = null;
+ }
+ if (workerUtils) {
+ await workerUtils.release();
+ workerUtils = null;


Suggested change
if(runner){
awaitrunner.stop();
runner=null;
}
if(workerUtils){
awaitworkerUtils.release();
workerUtils=null;
try{
if(runner){
awaitrunner.stop();
runner=null;
}
}finally{
if(workerUtils){
awaitworkerUtils.release();
workerUtils=null;
}
The stop() method has a resource leak: if runner.stop() throws an exception, the workerUtils.release() cleanup code will never execute, leaving database connections open.
View Details
Analysis
Resource leak in queue.stop() when runner.stop() throws
What fails: The stop() method in packages/world-postgres/src/queue.ts (lines 170-179) does not guarantee workerUtils.release() cleanup if runner.stop() throws an exception. If an exception occurs during runner.stop(), workerUtils.release() never executes, leaving database connections open indefinitely.
How to reproduce: Any exception thrown by runner.stop() (e.g., "Runner is already stopped" if called on an already-stopped instance, or network errors during graceful shutdown) will skip the workerUtils.release() call.
// Current code - if runner.stop() throws, cleanup is skippedasyncstop(){if(runner){awaitrunner.stop();// If this throws, next line doesn't executerunner=null;}if(workerUtils){awaitworkerUtils.release();// Unreachable if runner.stop() throwsworkerUtils=null;}}
Result: Database connections managed by workerUtils remain open, causing a resource leak.
Expected:workerUtils.release() should execute regardless of whether runner.stop() succeeds or fails. Per graphile-worker documentation, release() is critical for cleaning up database connections, LISTEN/NOTIFY listeners, signal handlers, and job batch operations.
Fix: Use try-finally to ensure cleanup always occurs:
asyncstop(){try{if(runner){awaitrunner.stop();runner=null;}}finally{if(workerUtils){awaitworkerUtils.release();workerUtils=null;}}}

arielweinberger added 6 commits November 30, 2025 23:16

feat: graphile worker
d77a73d

noop logger
0514450

with debug logs
981ae87

commit sha
c836d99

edit
685a4f4

feat: silent worker
fc8d436

arielweinberger closed this Dec 1, 2025

vercelBot reviewed Dec 1, 2025
View reviewed changes

arielweinberger added 6 commits November 30, 2025 23:16

feat: graphile worker
d77a73d

noop logger
0514450

with debug logs
981ae87

commit sha
c836d99

edit
685a4f4

feat: silent worker
fc8d436

arielweinberger closed this Dec 1, 2025

vercelBot reviewed Dec 1, 2025
View reviewed changes

arielweinberger added 6 commits November 30, 2025 23:16

feat: graphile worker
d77a73d

noop logger
0514450

with debug logs
981ae87

commit sha
c836d99

edit
685a4f4

feat: silent worker
fc8d436

arielweinberger closed this Dec 1, 2025

vercelBot reviewed Dec 1, 2025
View reviewed changes

arielweinberger added 6 commits November 30, 2025 23:16

feat: graphile worker
d77a73d

noop logger
0514450

with debug logs
981ae87

commit sha
c836d99

edit
685a4f4

feat: silent worker
fc8d436

arielweinberger closed this Dec 1, 2025

vercelBot reviewed Dec 1, 2025
View reviewed changes

arielweinberger added 6 commits November 30, 2025 23:16

feat: graphile worker
d77a73d

noop logger
0514450

with debug logs
981ae87

commit sha
c836d99

edit
685a4f4

feat: silent worker
fc8d436

arielweinberger closed this Dec 1, 2025

vercelBot reviewed Dec 1, 2025
View reviewed changes

arielweinberger added 6 commits November 30, 2025 23:16

feat: graphile worker
d77a73d

noop logger
0514450

with debug logs
981ae87

commit sha
c836d99

edit
685a4f4

feat: silent worker
fc8d436

arielweinberger closed this Dec 1, 2025

vercelBot reviewed Dec 1, 2025
View reviewed changes

arielweinberger added 6 commits November 30, 2025 23:16

feat: graphile worker
d77a73d

noop logger
0514450

with debug logs
981ae87

commit sha
c836d99

edit
685a4f4

feat: silent worker
fc8d436

arielweinberger closed this Dec 1, 2025

vercelBot reviewed Dec 1, 2025
View reviewed changes

arielweinberger added 6 commits November 30, 2025 23:16

feat: graphile worker
d77a73d

noop logger
0514450

with debug logs
981ae87

commit sha
c836d99

edit
685a4f4

feat: silent worker
fc8d436

arielweinberger closed this Dec 1, 2025

vercelBot reviewed Dec 1, 2025
View reviewed changes

-if(runner){
-awaitrunner.stop();
-runner=null;
-}
-if(workerUtils){
-awaitworkerUtils.release();
-workerUtils=null;
+try{
+if(runner){
+awaitrunner.stop();
+runner=null;
+}
+}finally{
+if(workerUtils){
+awaitworkerUtils.release();
+workerUtils=null;
+}

Uh oh!

Conversation

arielweinberger commented Dec 1, 2025

Uh oh!

changeset-botBot commented Dec 1, 2025

⚠️ No Changeset found

Uh oh!

vercelBot commented Dec 1, 2025

Uh oh!

vercelBotDec 1, 2025

Choose a reason for hiding this comment

Analysis

Resource leak in queue.stop() when runner.stop() throws

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

Conversation

arielweinberger commented Dec 1, 2025

Uh oh!

changeset-botBot commented Dec 1, 2025

⚠️ No Changeset found

Uh oh!

vercelBot commented Dec 1, 2025

Uh oh!

vercelBotDec 1, 2025

Choose a reason for hiding this comment

Analysis

Resource leak in queue.stop() when runner.stop() throws

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

Conversation

arielweinberger commented Dec 1, 2025

Uh oh!

changeset-botBot commented Dec 1, 2025

⚠️ No Changeset found

Uh oh!

vercelBot commented Dec 1, 2025

Uh oh!

vercelBotDec 1, 2025

Choose a reason for hiding this comment

Analysis

Resource leak in queue.stop() when runner.stop() throws

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

Conversation

arielweinberger commented Dec 1, 2025

Uh oh!

changeset-botBot commented Dec 1, 2025

⚠️ No Changeset found

Uh oh!

vercelBot commented Dec 1, 2025

Uh oh!

vercelBotDec 1, 2025

Choose a reason for hiding this comment

Analysis

Resource leak in queue.stop() when runner.stop() throws

Uh oh!