Leonel, Thank you for trying to replicate the issue - am guessing you replicated the "cleaning up of the cache issue", and not the "issue while using the cache itself"? I went ahead and refreshed the web2py repo (with your latest PR in it), and tried to test for these issues. I can confirm that the "cleaning" issue seems to be sorted out, except once in a while I see a message on the admin screen, while trying to clean the app, that "some files were not removed / cleaned". I do not have screenshot, will share the next time I come across it. The issue with the usage of the cache itself is now an issue that I have raised on github: https://github.com/web2py/web2py/issues/895
Please let me know if any more information will help in sorting out this issue. I'll see if I can take a look at the code, today, to track down this issue. On Wednesday, April 1, 2015 at 11:01:14 PM UTC+5:30, Leonel Câmara wrote: > > Kiran I had some trouble replicating with 2.10.2 but after putting 6 tabs > auto refreshing in the initial page and another tab in the admin cleaning I > started seeing the error both with the cache and session. I patched > app_cleanup so it would not throw an error when it encountered locked files > as these are files that are being used by other processes and cannot be > deleted, it's not a problem anyway since fileutils/w2p_pack ignores these > directories. > > Can you verify that this also fixes stuff for you: > https://github.com/web2py/web2py/pull/891 > -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
