ST3 appears to run/build the already saved version of a code file instead of the latest unsaved code

[nazariyg]

ST3 b3092, OS X.

This has to deal with ST automatically saving files before running/building them. ST appears to run the already saved version of code for a brief moment then save the latest code and run it again.

Got a partially copied file after running a Python script even though there was no copy making line in the latest version of the unsaved code before run/build, only in the previously saved file. As if the already saved code started to run, then was interrupted, and the new code was run. The new code ran as expected though.

[FichteFoll]

Could you perhaps provide example code for (easy) reproduction?

[keith-hall]

I've noticed something similar quite a lot when "building" syntax tests on Windows x64 (i.e. ST build 3125) - I guess there can be some kind of race condition where the build system is invoked before the file has finished being saved. In my case, the files are on a local disk (non-SSD). After getting confused for a few seconds, the workaround is to just run the build system again, or remember to explicitly save before building.

[keith-hall]

this may have been fixed in build 4067, according to the change log.