Bletchley Park Lv 1
This workaround may save trouble: switch to clients in 'main' rather than 'devprev'. The currently existing tmp files will not be deleted, but no new ones should appear.
This workaround may save trouble: switch to clients in 'main' rather than 'devprev'. The currently existing tmp files will not be deleted, but no new ones should appear.
BP is absolutely correct, I came home from partying and found ALL of my clients done, ie. QUIT. When I looked at Foldit partition, I saw that it was AGAIN at 20 gigs of space, i.e there was NO MORE available for the clients in questions. I DON"T consider this to be DECENT behavior on the part of the client or for the programmers creating that clients, you create problem, NO-ONE goes home until problem is PROPERLY fixed, if the military behaved this way, there would be NO victories for the HOME team… Either you are dedicated or you are NOT. So simple, it sounds like idiocy, it's NOT, it is the truth. This is a programmer created issue, I EXPECT a programmer to fix it, BEFORE HE/SHE GOES HOME.. You don't like my attitude, get a different job.
Just so you know, there will need to at LEAST a 24 hour period, and most likely a 48 hour period to compensate for this problem. Some of you might consider it fun to play around with DevPrev users, Those people need to be released from their duties..
It all comes back to QA ( Quality Assurance ). Personally I want to know why releases are being made without proper QA. It doesn't take much knowledge of a HD ( hard drive ) to figure out that a particular release is TAKING FAR TO MUCH SPACE. Right now, as much as I love this game for many, many reasons, I have NO love of the people creating it, which is an ABSOLUTE SHAME.
** How to switch to the main group: **
STOP all running clients. There will be a software update after you change to the main group. For that, all clients must be stopped and exited.
find the foldit directory. Most windows PCs will have a foldit directory that contains specific files, you can use the windows explorer search function to locate those files.
Search for a file called "all.macro", this will get you to the foldit directory.
In the foldit directory, locate the file named "options.txt" and edit it in Notepad
Search for the line that startes with the text "update_group"
It will either have : "main" or : "devprev" following it on the same line.
If it has "main", you are done. You are not affected.
If you have "devprev", change it to "main" and save the options.txt file.
restart your FIRST client. Do NOT start multiple clients yet, you will receive a software update.
let the program update itself and restart itself.
After it restarts, you may start new clients.
In due time the Foldit team will have to release a fix for the devprev version and a tool to remove the possibly thousands of .tmp files on your system.
Good luck, Bletchley park.
Sorry BP, I appreciate your response, it is ' good enough ' for most people, however Foldit admin has made this issue paramount. I will not be changing to Main for ANYBODY's sake. Fix the DevPrev and NEVER let it happen again. That is called QA. Your response it good enough for those that want to continue their runs, however it doesn't solve the REAL issues. I spent 20 hears in the Navy as a Team player, I expect the same from those that pretend to be interested in the results from Foldit.
Thank you BP.
What I've tended to do is go from open->done when the bug is fixed and checked in. I will try to mark feedback some other way if marking as done is causing problems
When the fix goes out to DevPrev it should go from done->resolved and then to closed once it has been regressed.
The fix has a flag added to the options.txt which will sweep the folders for the temporary files and delete them.
The bug came up because of the different code path that Windows has to take for autosave. Most of my testing is done in Linux where the bug didn't show up. When I tested the fix on a Windows machine, I didn't notice the temp file buildup. I didn't run through extensive quicksaves/autosaves which would cause a significant amount of the temp files to accumulate.
Again, sorry about all the autosave issues. The bug reports helped track down what exactly was happening quickly.
Bugs suck; however the reason that devpre exists is to help catch the bugs before the new code incorporated in Main. "Devpre" is part of the Q&A of Foldit. Those of us running Devpre are doing so to help vet the code and yes we will get eaten by bugs. We need to report the bugs but we shouldnt be surprised when we get hit by them that is the reason we are running Devpre.
I am concerned that on machines where many gigabytes of files have accumulated, the client may take several minutes to delete them, and may appear hung in the meantime. (I know deleting them manually through file manager takes a long time; idk if doing it programmatically will too). I wonder if the developers can test whether that will happen, and post a warning about it for people accepting the update when it comes out.
I am also dismayed that no notice about this bug and the need to switch to main until it's resolved has been added to the news or the front page, given how serious the consequences can be.