[bug-bash] edit and theme failures silently return exit 1 without a machine-readable stderr error

Fechada
  • Algo errado?
#278 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Um pull request relacionado já foi integrado.

  • #287 de @mkrueger — integrado

Avaliação

Dificuldade
3/5
Tempo estimado
1-2 dias
Facilidade para iniciantes
62/100
Tipo de issue
Bug
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
csharp
Domínio
cli

Direção de pesquisa

Start by tracing how command failures reach stderr and how --output json, --quiet, and -c affect error handling; compare the failing theme use, theme validate, and edit commands with the working not-a-real-command case. Run the PowerShell reproductions in the issue and capture stdout, stderr, and exit codes. Done when these failures emit explanatory structured JSON to stderr while retaining a nonzero exit code.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

bug bug-bash

Environment

Windows x64, CosmosDBShell 1.1.291-preview (db49321323).
No Cosmos DB connection or credentials are required.

Repro (PowerShell)

$package = "$env:USERPROFILE\.dotnet\tools\.store\cosmosdbshell\1.1.291-preview"
$shell = Join-Path $package 'cosmosdbshell.win-x64\1.1.291-preview\tools\net10.0\win-x64\CosmosDBShell.exe'
& $shell --version
$work = Join-Path ([IO.Path]::GetTempPath()) ("cosmos-errors-" + [guid]::NewGuid().ToString("N"))
New-Item -ItemType Directory -Path $work | Out-Null
Set-Location $work
& $shell --output json -c 'theme use missing-bug-bash-theme'
"Exit code: $LASTEXITCODE"

Actual:

  • Exit code: 1
  • stdout: empty
  • stderr: empty

The same silent failure reproduces with:

& $shell --output json -c 'theme validate .\missing-theme.toml'

Exact headless edit reproduction, including input redirection and output capture:

'bug-bash sample' | Set-Content -Encoding utf8 .\sample.txt
'' | & $shell --output json -c 'edit sample.txt' 1> .\edit.stdout.txt 2> .\edit.stderr.txt
$editExit = $LASTEXITCODE
[pscustomobject]@{
    ExitCode = $editExit
    StdoutBytes = (Get-Item .\edit.stdout.txt).Length
    StderrBytes = (Get-Item .\edit.stderr.txt).Length
}

Actual: ExitCode 1, StdoutBytes 0, StderrBytes 0. Interactive external editing
should be rejected with an explanation in this context, not fail silently.
The same edit result was also observed with --quiet and default -c mode.

Expected

Failures in machine mode emit an explanatory structured JSON error object to
stderr, consistent with the documented automation contract and other commands.
The existing exit code can remain nonzero.

For example:

{"status":"error","error":"Unknown theme ..."}

Working control

& $shell --output json -c 'not-a-real-command'

This correctly returns exit code 2 and a structured stderr error:

{"status":"error","error":"'not-a-real-command' is not recognized ..."}

cat with a missing file, filter with a missing expression, and invalid ftab
formats also emit structured diagnostics; the silence is not a harness-wide
capture problem.

Impact

Automation can detect failure but cannot explain it, surface remediation, or
collect useful bug reports. Empty stderr also makes rejected interactive editing
indistinguishable from an unexplained internal failure.

Validation

Reproduced with direct child-process execution, captured stdout and stderr,
and closed/redirected stdin. The edit failure reproduces with --output json,
--quiet, and default -c machine mode. Both invalid theme operations reproduce
without a database connection.

Linguagem predominante
C#
Estrelas
4
Forks
7
Merge médio
1d 15h
PRs com merge (30d)
33

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de Azure/CosmosDBShell

Todas as issues de Azure/CosmosDBShell

Issues semelhantes

Mais issues de C#

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.