-
Notifications
You must be signed in to change notification settings - Fork 285
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
gmvault stops syncing after 20k emails #107
Comments
@dukaras this problem might have been solved in the new version which should be released within the next 2-3 weeks. I can give you a test distribution for you to validate that it will work in the new release. |
Sounds great! I would be up for using the new version immediately and Thanks, 888.848.0786 x. 102 (f) 402.507.4477 On Tue, Feb 12, 2013 at 9:41 AM, Guillaume Aubert
|
Ok I will prepare one and let you know when it is ready. |
Great! Thanks for your help! 888.848.0786 x. 102 (f) 402.507.4477 On Tue, Feb 12, 2013 at 10:27 AM, Guillaume Aubert <notifications@github.com
|
@dukaras A test version is available here: https://www.dropbox.com/s/lc2eqirl3ugwsnf/gmvault_installer_v1.7.2.5.exe |
Hi. It did fail again...but did make it a few emails further than previously. Pushing email body with id 1409651859965224046. result_uid = 62401 Pushing email body with id 1409651901046922005. result_uid = 62402 Pushing email body with id 1409652580799355841. result_uid = 62403 Pushing email body with id 1409652663228496484. result_uid = 62404 label = \Sent Pushing email body with id 1409653413750659076. result_uid = 62405 label = \Important Pushing email body with id 1409653504756165905. result_uid = 62406 label = \Important Pushing email body with id 1409653721665527692. result_uid = 62407 Pushing email body with id 1409653744479829264. result_uid = 62408 label = \Important Pushing email body with id 1409653798407284045. result_uid = 62409 label = \Important Pushing email body with id 1409653803268416767. result_uid = 62410 Pushing email body with id 1409653819132883426. result_uid = 62411 Pushing email body with id 1409653890783218805. result_uid = 62412 label = \Important Pushing email body with id 1409654192588381895. .ubject = Reminder: Alexander Liaugminas - DI & LI Options @ Tue Aug 7 10amBefore to Append email contents result_uid = 62413 Pushing email body with id 1409654261765708367. result_uid = 62414 label = \Sent Pushing email body with id 1409654299927921995. result_uid = 62415 Pushing email body with id 1409654312376329145. result_uid = 62416 Pushing email body with id 1409654450513162101. result_uid = 62417 Labels creation tentative for emails with ids <itertools.ifilter object at Error when reaching Gmail server. Wait 1 seconds and retry up to 2 times. After Enabling compression Error when reaching Gmail server. Wait 2 seconds and retry up to 2 times. After Enabling compression Error when reaching Gmail server. Wait 4 seconds and retry up to 2 times. === Exception traceback === === End of Exception traceback === usage: gmvault [-h] [-v] {sync,restore,check} ... optional arguments: subcommands: Examples: a) Get help for each of the individual commands #> gmvault sync -h gmvault-shell> 888.848.0786 x. 102 (f) 402.507.4477 On Tue, Feb 12, 2013 at 2:13 PM, Guillaume Aubert
|
Ok I need to check Guillaume On 12 February 2013 23:01, dukaras notifications@github.com wrote:
|
@dukaras, it has to do with the * in *TextSummer2012 which prevents the label to be applied properly. I will fix the issue tonight and prepare a new version for testing and let you know. |
You're awesome! Thanks for your help! On Wed, Feb 13, 2013 at 3:48 AM, Guillaume Aubert
|
@dukaras, here is the new version fixing your restore option: I have changed the strategy to apply labels so I hope I have not broken Let me know and send me the output in debug mode if you encounter an issue. All the best, On 13 February 2013 18:39, dukaras notifications@github.com wrote:
|
Thanks for all of your help! Everything ended up working just as we had 888.848.0786 x. 102 (f) 402.507.4477 On Wed, Feb 13, 2013 at 2:28 PM, Guillaume Aubert
|
Very Good, happy to help. Thank you for reporting the issue. Please make On 14 February 2013 20:42, dukaras notifications@github.com wrote:
|
Awesome! 888.848.0786 x. 102 (f) 402.507.4477 On Thu, Feb 14, 2013 at 1:56 PM, Guillaume Aubert
|
For some reason the sync stops at the same email every time. I've tried removing the files surrounding the error file out of the db file. Below is the error we keep running into. Any help would be huge! Thanks.
gmvault-shell>gmvault restore m*********@*****.com --resume
Use gmvault-db located in C:\Users\thewigginsfam/gmvault-db.
Authentication performed with Gmail XOAuth token.
Get XOAuth credential from C:\Users\thewigginsfam/.gmvault/m*********@*****.com.oauth.
Successfully read oauth credentials.
Connect to Gmail server.
Start emails restoration.
Restore emails in gmail account m*********@*****.com.
Read email info from C:\Users\thewigginsfam/gmvault-db gmvault-db.
Total number of elements to restore 27792.
Restart from gmail id 1409591944533445131.
Got all emails id left to restore. Still 8002 emails to do.
Restore email with id 1409643729574629424.
Restore email with id 1409647096567623480.
Restore email with id 1409647274694757166.
Restore email with id 1409649168282750055.
Restore email with id 1409649945293138772.
Restore email with id 1409650909582787065.
Restore email with id 1409651093528651387.
Restore email with id 1409651206258229273.
Restore email with id 1409651361803404856.
Restore email with id 1409651475481262825.
Error when reaching Gmail server. Wait 1 seconds and retry up to 2 times.
Disconnecting from Gmail Server and sleeping ...
Reconnecting to the from Gmail Server.
Get XOAuth credential from C:\Users\thewigginsfam/.gmvault/m*********@*****.com.oauth.
Error when reaching Gmail server. Wait 2 seconds and retry up to 2 times.
Disconnecting from Gmail Server and sleeping ...
Reconnecting to the from Gmail Server.
Get XOAuth credential from C:\Users\thewigginsfam/.gmvault/m*********@*****.com.oauth.
Error when reaching Gmail server. Wait 4 seconds and retry up to 2 times.
Error: UID command error: BAD ['Could not parse command'].
=== Exception traceback ===
Traceback (most recent call last):
File "gmv\gmv_cmd.pyc", line 645, in run
File "gmv\gmv_cmd.pyc", line 531, in _restore
File "gmv\gmvault.pyc", line 1396, in restore
File "gmv\gmvault.pyc", line 1747, in restore_emails
error: UID command error: BAD ['Could not parse command']
=== End of Exception traceback ===
usage: gmvault [-h] [-v] {sync,restore,check} ...
optional arguments:
-h, --help show this help message and exit
-v, --version show program's version number and exit
subcommands:
{sync,restore,check} valid subcommands.
sync synchronize with a given gmail account.
restore restore gmvault-db to a given email account.
check Check and clean the gmvault-db disk database.
Examples:
a) Get help for each of the individual commands
> gmvault sync -h
> gmvault restore --help
> gmvault check -h
gmvault-shell>gmvault restore m*********@*****.com --resume
Use gmvault-db located in C:\Users\thewigginsfam/gmvault-db.
Authentication performed with Gmail XOAuth token.
Get XOAuth credential from C:\Users\thewigginsfam/.gmvault/m*********@*****.com.oauth.
Successfully read oauth credentials.
Connect to Gmail server.
Start emails restoration.
Restore emails in gmail account m*********@*****.com.
Read email info from C:\Users\thewigginsfam/gmvault-db gmvault-db.
Total number of elements to restore 27790.
Restart from gmail id 1409591944533445131.
Got all emails id left to restore. Still 8000 emails to do.
Restore email with id 1409643729574629424.
Restore email with id 1409647096567623480.
Restore email with id 1409647274694757166.
Restore email with id 1409649168282750055.
Restore email with id 1409649945293138772.
Restore email with id 1409650909582787065.
Restore email with id 1409651093528651387.
Restore email with id 1409651206258229273.
Restore email with id 1409651361803404856.
Restore email with id 1409651747023992527.
Error when reaching Gmail server. Wait 1 seconds and retry up to 2 times.
Disconnecting from Gmail Server and sleeping ...
Reconnecting to the from Gmail Server.
Get XOAuth credential from C:\Users\thewigginsfam/.gmvault/m*********@*****.com.oauth.
Error when reaching Gmail server. Wait 2 seconds and retry up to 2 times.
Disconnecting from Gmail Server and sleeping ...
Reconnecting to the from Gmail Server.
Get XOAuth credential from C:\Users\thewigginsfam/.gmvault/m*********@*****.com.oauth.
Error when reaching Gmail server. Wait 4 seconds and retry up to 2 times.
Error: UID command error: BAD ['Could not parse command'].
=== Exception traceback ===
Traceback (most recent call last):
File "gmv\gmv_cmd.pyc", line 645, in run
File "gmv\gmv_cmd.pyc", line 531, in _restore
File "gmv\gmvault.pyc", line 1396, in restore
File "gmv\gmvault.pyc", line 1747, in restore_emails
error: UID command error: BAD ['Could not parse command']
=== End of Exception traceback ===
usage: gmvault [-h] [-v] {sync,restore,check} ...
optional arguments:
-h, --help show this help message and exit
-v, --version show program's version number and exit
subcommands:
{sync,restore,check} valid subcommands.
sync synchronize with a given gmail account.
restore restore gmvault-db to a given email account.
check Check and clean the gmvault-db disk database.
Examples:
a) Get help for each of the individual commands
> gmvault sync -h
> gmvault restore --help
> gmvault check -h
gmvault-shell>gmvault restore m*********@*****.com --resume
Use gmvault-db located in C:\Users\thewigginsfam/gmvault-db.
Authentication performed with Gmail XOAuth token.
Get XOAuth credential from C:\Users\thewigginsfam/.gmvault/m*********@*****.com.oauth.
Successfully read oauth credentials.
Connect to Gmail server.
Start emails restoration.
Restore emails in gmail account m*********@*****.com.
Read email info from C:\Users\thewigginsfam/gmvault-db gmvault-db.
Total number of elements to restore 27788.
Restart from gmail id 1409591944533445131.
Got all emails id left to restore. Still 7998 emails to do.
Restore email with id 1409643729574629424.
Restore email with id 1409647096567623480.
Restore email with id 1409647274694757166.
Restore email with id 1409649168282750055.
Restore email with id 1409649945293138772.
Restore email with id 1409650909582787065.
Restore email with id 1409651093528651387.
Restore email with id 1409651206258229273.
Restore email with id 1409651859965224046.
Restore email with id 1409651901046922005.
Restore email with id 1409652580799355841.
Restore email with id 1409652663228496484.
Restore email with id 1409653413750659076.
Error when reaching Gmail server. Wait 1 seconds and retry up to 2 times.
Disconnecting from Gmail Server and sleeping ...
Reconnecting to the from Gmail Server.
Get XOAuth credential from C:\Users\thewigginsfam/.gmvault/m*********@*****.com.oauth.
Error when reaching Gmail server. Wait 2 seconds and retry up to 2 times.
Disconnecting from Gmail Server and sleeping ...
Reconnecting to the from Gmail Server.
Get XOAuth credential from C:\Users\thewigginsfam/.gmvault/m*********@*****.com.oauth.
Error when reaching Gmail server. Wait 4 seconds and retry up to 2 times.
Error: UID command error: BAD ['Could not parse command'].
=== Exception traceback ===
Traceback (most recent call last):
File "gmv\gmv_cmd.pyc", line 645, in run
File "gmv\gmv_cmd.pyc", line 531, in _restore
File "gmv\gmvault.pyc", line 1396, in restore
File "gmv\gmvault.pyc", line 1747, in restore_emails
error: UID command error: BAD ['Could not parse command']
=== End of Exception traceback ===
usage: gmvault [-h] [-v] {sync,restore,check} ...
optional arguments:
-h, --help show this help message and exit
-v, --version show program's version number and exit
subcommands:
{sync,restore,check} valid subcommands.
sync synchronize with a given gmail account.
restore restore gmvault-db to a given email account.
check Check and clean the gmvault-db disk database.
Examples:
a) Get help for each of the individual commands
> gmvault sync -h
> gmvault restore --help
> gmvault check -h
gmvault-shell>^A
The text was updated successfully, but these errors were encountered: