How Did an Opening Remark Become the Deliverable?

Описание и применение

Диспетчер, использующий только код выхода процесса, ошибочно принимал открывающий текст от AI как успешный результат, игнорируя статус ошибки сервиса. Исправление добавило проверку статуса ответа, предотвращая неверное принятие неполных результатов.

Задача

A dispatcher incorrectly treated an AI assistant’s opening narration as a successful result because it relied solely on the process exit code, ignoring the service’s error status.

Результат

The fix prevents accidental acceptance of incomplete or erroneous AI outputs, ensuring downstream stages receive accurate success/failure signals and can inspect partial results.

Рабочий процесс

• 1. Dispatcher starts a command‑line tool that calls the AI service.
• 2. Tool exits with code 0 and returns a response containing an error status and opening narration.
• 3. Old dispatcher writes the narration to the result file, treating it as success.
• 4. Updated dispatcher detects the error status, reports failure, and leaves a fallback marker while preserving any generated files.

Доказательства

The program collecting the result trusted another signal: a normal process exit.

Источник

After hitting a quota limit, Agy could return exit code zero while its terminal event reported ERROR and included opening narration.

Источник

The fix addresses precisely that mismatch: after hitting a quota limit, Agy could return exit code zero while its terminal event reported ERROR and included opening narration.

Источник