Fix shellTracker incorrectly reporting short-lived commands as running #380

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

bhouston merged 1 commit into main from fix-shelltracker-status-379

Mar 25, 2025

Merged

Fix shellTracker incorrectly reporting short-lived commands as running #380

Fix shellStart bug with incorrect shellId tracking

Annotations

10 errors

Process completed with exit code 2.

Object is possibly 'undefined'.

Property 'shellId' does not exist on type '{ exitCode: number; mode: "sync"; stdout: string; stderr: string; error?: string | undefined; } | { mode: "async"; stdout: string; stderr: string; shellId: string; error?: string | undefined; }'.

Object is possibly 'undefined'.

Property 'exitCode' does not exist on type '{ exitCode: number; mode: "sync"; stdout: string; stderr: string; error?: string | undefined; } | { mode: "async"; stdout: string; stderr: string; shellId: string; error?: string | undefined; }'.

Object is possibly 'undefined'.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Fix shellTracker incorrectly reporting short-lived commands as running #380

Uh oh!

Uh oh!

Fix shellTracker incorrectly reporting short-lived commands as running #380

Uh oh!

Annotations

The logs for this run have expired and are no longer available.

Re-running jobs...