This repository has been archived by the owner on Oct 25, 2024. It is now read-only.
Add note regarding file system support to README #56
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| for file systems that support atomic segment writes (like YAFFS). Most | ||
| conventional file systems don't support this; if the power goes out while | ||
| writing a segment, the segment will contain garbage and the file will be | ||
| corrupt. We'll add journaling support so this class can be used with more |
There was a problem hiding this comment.
so this class should probably be clarified since it is outside of QueueFile.
|
As far as the roadmap, this issue is mentioned in #5 but I do not believe anyone has begun any work to change the behavior. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
After an unclean termination of a service, QueueFile failed to peek and remove, yet the enqueue functionality continued to work. I tweaked the header value for first element position to bypass the corrupt entry. In looking at the code, I see comments making it quite clear this can happen, yet the README does not.
Is journaling, as noted in the comments, something on the roadmap?