Issues

Overlay PATH lookup picks a file the current user can't execute (e.g. root-owned 0700), so the start fails with "Permission denied" where the shell runs the next match (net7+)

ktsu-dev/RunCommand#143 · opened

on Nov 4, 2026

1

net5.0/net6.0/netstandard builds pick a non-executable file earlier on the overlay PATH, so the command fails with "Permission denied" instead of running the executable copy later on

ktsu-dev/RunCommand#139 · opened

on Nov 4, 2026

1

Windows: with PATH in the overlay, a bare name like `npm` now resolves to `npm.cmd`, so cmd.exe re-parses the arguments and `&`, `|`, `%` in them run as commands

ktsu-dev/RunCommand#138 · opened

on Nov 4, 2026

1

On .NET Core 3.x and .NET 5–7, cancelling a command leaves its child processes running, though README says the whole process tree is terminated on .NET Core 3.0+

ktsu-dev/RunCommand#134 · opened

on Nov 2, 2026

1

A cancelled ExecuteAsync throws while an output delegate is still running, so the caller's catch block (or the next run on the same handler) runs at the same time as it: a gap in the #95 fix

ktsu-dev/RunCommand#125 · opened

on Oct 29, 2026

1

Synchronous Execute(..., Elevation.Elevated) deadlocks on a UI thread in the netstandard2.0/2.1 builds

ktsu-dev/RunCommand#113 · opened

on Oct 6, 2026

1

ExecuteAsync doesn't return after the command exits while a background child it started still holds stdout/stderr: `sh -c "echo x; sleep 1000 &"` blocks for the sleep's lifetime

ktsu-dev/RunCommand#100 · opened

on Sep 29, 2026

1

Navigation Menu

Repository navigation

Issues

Overlay PATH lookup picks a file the current user can't execute (e.g. root-owned 0700), so the start fails with "Permission denied" where the shell runs the next match (net7+)

net5.0/net6.0/netstandard builds pick a non-executable file earlier on the overlay PATH, so the command fails with "Permission denied" instead of running the executable copy later on

Windows: with PATH in the overlay, a bare name like `npm` now resolves to `npm.cmd`, so cmd.exe re-parses the arguments and `&`, `|`, `%` in them run as commands

On .NET Core 3.x and .NET 5–7, cancelling a command leaves its child processes running, though README says the whole process tree is terminated on .NET Core 3.0+

A cancelled ExecuteAsync throws while an output delegate is still running, so the caller's catch block (or the next run on the same handler) runs at the same time as it: a gap in the #95 fix

Synchronous Execute(..., Elevation.Elevated) deadlocks on a UI thread in the netstandard2.0/2.1 builds

ExecuteAsync doesn't return after the command exits while a background child it started still holds stdout/stderr: `sh -c "echo x; sleep 1000 &"` blocks for the sleep's lifetime

Issues

Issues

Issues

Overlay PATH lookup picks a file the current user can't execute (e.g. root-owned 0700), so the start fails with "Permission denied" where the shell runs the next match (net7+)

net5.0/net6.0/netstandard builds pick a non-executable file earlier on the overlay PATH, so the command fails with "Permission denied" instead of running the executable copy later on

Windows: with PATH in the overlay, a bare name like npm now resolves to npm.cmd, so cmd.exe re-parses the arguments and &, |, % in them run as commands

On .NET Core 3.x and .NET 5–7, cancelling a command leaves its child processes running, though README says the whole process tree is terminated on .NET Core 3.0+

A cancelled ExecuteAsync throws while an output delegate is still running, so the caller's catch block (or the next run on the same handler) runs at the same time as it: a gap in the #95 fix

Synchronous Execute(..., Elevation.Elevated) deadlocks on a UI thread in the netstandard2.0/2.1 builds

ExecuteAsync doesn't return after the command exits while a background child it started still holds stdout/stderr: sh -c "echo x; sleep 1000 &" blocks for the sleep's lifetime

Windows: with PATH in the overlay, a bare name like `npm` now resolves to `npm.cmd`, so cmd.exe re-parses the arguments and `&`, `|`, `%` in them run as commands

ExecuteAsync doesn't return after the command exits while a background child it started still holds stdout/stderr: `sh -c "echo x; sleep 1000 &"` blocks for the sleep's lifetime