-
Notifications
You must be signed in to change notification settings - Fork 149
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
Validate behaviour of DirectFileStore
in the presence of existing files
#109
Comments
See Lawrence's comment on file locking as a potential way of knowing which files are still owned by living processes. Valid warning from Brian that it may not work in all OSes, plus we can't just delete "some" files, but this may be an idea to start building a solution around |
Similar to #143, and for the same reasons outlined in this comment, I'm taking this out of the v0.10.0 milestone. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We (GoCardless) run our services in containers, which means a clean file system every time we boot the app.
We should look at what the behaviour is like for people who have file systems that persist between versions of the app. If so, we should look at what mitigations we can implement to make
DirectFileStore
work by default.Any edge-cases should be added to the
DirectFileStore
’s docs.The text was updated successfully, but these errors were encountered: