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.
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
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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:
msr2data "[514 520]" _tmpl msr-514 global
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.
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