Skip to content

fix: unece --output prints stderr confirmation, §2.2 parity (v0.5.30)#40

Merged
SoundMatt merged 1 commit into
mainfrom
fix/unece-stderr-confirmation
Jun 13, 2026
Merged

fix: unece --output prints stderr confirmation, §2.2 parity (v0.5.30)#40
SoundMatt merged 1 commit into
mainfrom
fix/unece-stderr-confirmation

Conversation

@SoundMatt

Copy link
Copy Markdown
Owner

Summary

  • cfusa unece --output <file>: now prints "UN R.155 gap report written to <file>" to stderr after writing. stdout stays empty per §2.2.

Parity

go-FuSa: TestRunUNECE_OutputFile (which uses t.Errorf for the stderr assertion — confirmed required)

Test plan

  • All 34 test suites pass (verified locally: 100% pass)
  • cfusa unece --output /tmp/u.json creates file and prints "UN R.155" to stderr
  • stdout is empty when --output is given (§2.2)

cmd_unece: when --output is given, print "UN R.155 gap report written to
<file>" to stderr after writing. stdout stays empty per §2.2.

Parity with go-FuSa TestRunUNECE_OutputFile.

Signed-off-by: Matt Jones <matt@jellybaby.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Signed-off-by: Matt Jones <47545907+SoundMatt@users.noreply.github.com>
Comment thread cmd/cfusa/cmd_unece.c

if (output && out != stdout) fclose(out);
if (output && out != stdout) {
fclose(out);
@SoundMatt SoundMatt merged commit a451780 into main Jun 13, 2026
10 checks passed
@SoundMatt SoundMatt deleted the fix/unece-stderr-confirmation branch June 13, 2026 23:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants