Closed daniels closed 6 years ago
@daniels , thanks for the detailed report! Wouldn't be surprised is this is also the underlying problem of the issue reported here that I didn't fully resolve: https://github.com/scriptotek/alma-slipsomat/issues/31#issuecomment-366377159
There's some design decisions made early on that I regret, so I've started on a refactoring to make things less intertwingled.
Hi,
I just noticed that after running
defaults
,pull
wouldn't retrieve files I knew were changed in Alma.Looking at the diff of status.json after the defaults command, the modified date was changed for these files, but the checksum was not and the modified files had not been fetched. Subsequently running
pull
would first crash slipsomat (possibly not related, but happened both on the first run and when I reproduced the issue) and after restarting,pull
reported that "0 of 113 files contained new modifications".Reverting these lines in status.json solved the issue for me, and of course there is a workaround in always running
pull
beforedefaults
.Just in case the crash is related, here are the last few lines of the output: