-
-
Notifications
You must be signed in to change notification settings - Fork 288
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
IO Error accessing file in cache #106
Comments
Platform? Call stack?
Which PR are you referring to? |
At the moment however I'm running a lower version and haven't upgraded yet as I need to test what happens to existing caches with the new version. I experienced the IO problem in the latest nuget version when I checked to see if it was an old bug. Because of the way I collect errors from users, this is the best I can give but I don't think it helps. Have you ever seen System.IO.__Error in WinIOError? I can reproduce it in my code by running my app which writes the cache, then delete the cache from the hard disk and rerun the app. Users of the app are however getting the error just by running the app. Thanks again for looking at this.
|
Paul, do you require any more information from me? |
lol if you can reproduce it in your code then get me a real call stack :) |
In general, Akavache doesn't break user data between versions (at all, even between major versions). If there is a change to the on-disk data it gets handled silently by the library. |
Hey,
I keep getting IOErrors from Akavache where it says the file is being accessed by another process. I am wondering if it is a threading issue with my code, is this something you have seen before? Should Akavache be dealing with these exceptions and retrying if it happens? On a separate note, with the new version you seem to have changed from SecretCache to BlobCache if the storage is in roaming. The pr suggests that you can override this to put it back to SecretCache but I have been unable to find how, is it possible?
Thanks in advance
Adam
The text was updated successfully, but these errors were encountered: