-
Notifications
You must be signed in to change notification settings - Fork 19
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
0.9.0: --runonce doesn't work. #24
Comments
Looks like f385ae7 may have something to do with it. Thanks for the report, will look into this and release a new version if need be! |
No problem and thank YOU. |
Just wondering, was this closed because it's been fixed? If not, feel free to reopen it or I can create a new issue. Can take me a while to get around to things, but having an issue keeps it on my radar for when I have time to look! |
--run_once doesn't work either. I should've reported this sooner but I forgot. |
Alright, I do see where this issue is. I've got an initial fix over here, but I will need to modify the code with RLocks and such to make sure we don't cancel in-progress downloads (which right now, with that code, WILL HAPPEN A WHOLE LOT). I'll keep you posted and post in here once I've fixed it properly and merged that into master. |
Update on this fix? |
Just been sidetracked for a while with other stuff. I should be able to On 23 January 2016 at 11:00, jcook14 [email protected] wrote:
|
Thanks @DanielOaks for your time, it will fix a really annoying bug! |
No problem @0XE4, thanks for your comment! The recently released v0.9.2 should fix this issue properly. In other words: Windows .exe releases are not yet updated, need to setup a new Windows environment since the laptop I could run VMs on died a while ago. Hopefully should be updated in the next day or so. |
Script just keeps running. Windows version.
The text was updated successfully, but these errors were encountered: