Closed philipstarkey closed 5 years ago
Original comment by Chris Billington (Bitbucket: cbillington, GitHub: chrisjbillington).
Thanks for the bug report! It was supposed to be completely backward compatible, so apologies that it broke for you. You shouldn't have to understand or do anything for it not to break. I'll see what I can do.
Original comment by Chris Billington (Bitbucket: cbillington, GitHub: chrisjbillington).
What Python version are you on? I think the issue is that different Python versions raise different errors when a file or directory does not exist, and I'm not catching the full range of possibilities when determining if the file exists or not.
Original comment by Chris Billington (Bitbucket: cbillington, GitHub: chrisjbillington).
Oh, yikes, the change in how the errors appear is my fault - I left debug code in the PR that raised the error instead of showing it in the output box. Basically if errors occur during config-file-loading they are displayed in the outputbox since the are probably about the config file. But during developing it hides actual errors so I turned that off and forgot to turn it back on again...
Great, it's definitely that I'm not catching the right exceptions. I'll read up on the exception hierarchy changes for OSErrors etc between Python 2 and 3 and make sure I'm catching the right exception. It will be an easy fix, just gotta make sure I'm covering all the bases. Will have it fixed soon!
Original comment by Chris Billington (Bitbucket: cbillington, GitHub: chrisjbillington).
This should be resolved by b2ca5d9ed415c65a82261761a447989efa586a61, could you check if it fixes it as expected?
Original comment by Chris Billington (Bitbucket: cbillington, GitHub: chrisjbillington).
Fixed in b2ca5d9ed415c65a82261761a447989efa586a61
Original report (archived issue) by David Meyer (Bitbucket: dihm, GitHub: dihm).
Updating to tag 2.4.0 I now get many file not found errors for the .next_sequence_index file when opening and closing runmanager. It also appears that the closing error is preventing runmanager from updating runmanager.ini.
Also, my shot output folder gets erased on load. I get the corresponding non-default output folder message, but the reset to default folder button is not available.
I'm guessing that part of this is just me not understanding how to work with the new sequence_index, but I also thought the idea was to not force people to immediately update to the new scheme so I'm not quite sure what is going on.
The opening runmanager traceback (which appears twice) is
Relevant labconfig is