Closed xenDev closed 6 years ago
I have not seen the exact error but certain x64 builds of python were throwing errors related to fstransact. What version of oythin are you using? We can try running the test suite first and see if it gives us any clues. Other wise making a repeatable failing test and using git bisect could shed some light.
I'm experiencing the exact same error on Windows 10 w/ Python 2.7.11 64-bit .
Thanks for reaching out. Unfortunately this project is no longer actively maintained, so I'm going to move it into archive mode:
https://rfk.id.au/blog/entry/archiving-open-source-projects/
I get the following error after 2 or 3 updates using esky. Once it is in this state, I can't get out of this state without restarting the computer. I am running on Windows 10.
My updater is pretty vanilla.
Has anyone seen this?
C:\U\s\Documents> Traceback (most recent call last): File "arxspan-live-edit-host.py", line 10, in
File "eskyinit.pyc", line 981, in run_startup_hooks
File "eskyinit.pyc", line 366, in cleanup
File "eskyinit.pyc", line 402, in _cleanup_actions
File "eskyinit.pyc", line 360, in cleanup
File "eskyinit.pyc", line 787, in install_version
File "eskyinit.pyc", line 819, in _unpack_bootstrap_env
File "esky\fstransact\win32txf.pyc", line 117, in move
File "esky\fstransact\win32txf.pyc", line 126, in _move
File "esky\fstransact\win32txf.pyc", line 24, in wrapper
WindowsError: [Error 6714] The current transaction context associated with the thread is not a valid handle to a transaction object.