Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Martinize2 cannot write the output files for debug #311

Closed
jbarnoud opened this issue Sep 23, 2020 · 1 comment
Closed

Martinize2 cannot write the output files for debug #311

jbarnoud opened this issue Sep 23, 2020 · 1 comment

Comments

@jbarnoud
Copy link
Collaborator

If an error occurs that causes an exception, the deferred files are never written and there is no way to cause them to be from the command line. This makes debugging more difficult.

A solution would be to have a flag in the DeferredFileWriter singleton to cause the files to be written right away. That flag could be set with a -debug or -no-defer option in the command line.

@pckroon
Copy link
Member

pckroon commented Sep 24, 2020

Related #298
Yes, good argument. For now though, your files will survive in your temporary directory.
It may also be a good idea to have the write-{canon,repair,graph} bypass the deferred writer. (Or better, have the writer write them immediately so the backup mechanism works).

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

No branches or pull requests

2 participants