-
Notifications
You must be signed in to change notification settings - Fork 282
Open
Conversation
I'm running on a Synology NAS and it creates some directories starting with `@` and `#` that are used for metadata and integrity info. This patch ignores those
``` File "/volume1/@appstore/python/lib/python2.7/site-packages/gmv/gmvault_db.py", line 137, in _init_sub_chats_dir
raise Exception("Should get 2 elements in %s" % the_split)
Exception: Should get 2 elements in ['@eadir']```
@nabeelio
nabeelio
changed the title
(削除) Skip @eaDir directories (削除ここまで)
(追記) Skip @eaDir directories when run on a Synology NAS (追記ここまで)
May 28, 2017
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Uh oh!
There was an error while loading. Please reload this page.
I'm running on a Synology NAS and it creates some directories starting with
@and#that are used for metadata and integrity info. This patch ignores those in the_init_sub_chats_dir()method. I've been able to run through backing up all chats and its working through the emails now, without any errors. Maybe it'd be better to scan if it's starting with any special chars - I can modify this PR to do that, if you wish. Thanks!