You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just been re-importing my gmail and hit the limits again with errors thrown - though this time from well inside the imap libraries. But the errors could still be caught and nice error messages given to users - definitely in the second case below. Might want to retry in the first case. Might have a go at this myself sometime.
First while indexing I got
/usr/lib/ruby/1.9.1/openssl/buffering.rb:235:in `syswrite': closed stream (IOError)
from /usr/lib/ruby/1.9.1/openssl/buffering.rb:235:in `do_write'
from /usr/lib/ruby/1.9.1/openssl/buffering.rb:318:in `print'
from /usr/lib/ruby/1.9.1/net/imap.rb:1168:in `put_string'
from /usr/lib/ruby/1.9.1/net/imap.rb:1140:in `block in send_command'
from /usr/lib/ruby/1.9.1/monitor.rb:201:in `mon_synchronize'
from /usr/lib/ruby/1.9.1/net/imap.rb:1135:in `send_command'
from /usr/lib/ruby/1.9.1/net/imap.rb:667:in `close'
from /home/hamish/dev/heliotrope/lib/heliotrope/imap-dumper.rb:246:in `finish!'
from /home/hamish/dev/heliotrope/bin/heliotrope-import:178:in `ensure in '
from /home/hamish/dev/heliotrope/bin/heliotrope-import:178:in `'
Then when trying to restart I got
/usr/lib/ruby/1.9.1/net/imap.rb:1099:in `get_tagged_response': Account exceeded command or bandwidth limits. (Failure) (Net::IMAP::NoResponseError)
from /usr/lib/ruby/1.9.1/net/imap.rb:1153:in `block in send_command'
from /usr/lib/ruby/1.9.1/monitor.rb:201:in `mon_synchronize'
from /usr/lib/ruby/1.9.1/net/imap.rb:1135:in `send_command'
from /usr/lib/ruby/1.9.1/net/imap.rb:419:in `login'
from /home/hamish/dev/heliotrope/lib/heliotrope/imap-dumper.rb:148:in `load!'
from /home/hamish/dev/heliotrope/bin/heliotrope-import:127:in `'
The text was updated successfully, but these errors were encountered:
Hello again
Just been re-importing my gmail and hit the limits again with errors thrown - though this time from well inside the imap libraries. But the errors could still be caught and nice error messages given to users - definitely in the second case below. Might want to retry in the first case. Might have a go at this myself sometime.
First while indexing I got
Then when trying to restart I got
The text was updated successfully, but these errors were encountered: