msr2data can return nonzero exit status after successfully producing output #18

Closed
opened 2026-08-27 11:27:09 +02:00 by salman · 1 comment
Owner

Nothing critical here, it mostly affects my interaction with msr2data safely.

msr2data sometimes returns a nonzero process exit code even though it successfully creates the requested output file.
This has been observed for both:

  • global MSR generation, e.g.
    msr2data "[514 520]" _tmpl msr-514 global
  • parameterdata export, e.g.
    msr2data 514 _tmpl new data -o 514_par.dat

In these cases, the generated global .msr is non-empty and structurally valid, or the requested .dat file is present and non-empty, but the shell exit status is not zero.

Nothing critical here, it mostly affects my interaction with msr2data safely. msr2data sometimes returns a nonzero process exit code even though it successfully creates the requested output file. This has been observed for both: - global MSR generation, e.g. msr2data "[514 520]" _tmpl msr-514 global - parameterdata export, e.g. msr2data 514 _tmpl new data -o 514_par.dat In these cases, the generated global .msr is non-empty and structurally valid, or the requested .dat file is present and non-empty, but the shell exit status is not zero.
Owner

I led Claude fix this, and make sure that this is now also consistently done for all musrfit executable which are typically called from the cli.
sha 32f2d3defa

I led Claude fix this, and make sure that this is now also consistently done for all musrfit executable which are typically called from the cli. sha 32f2d3defa64713
Sign in to join this conversation.
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: LMU/musrfit#18