Skip to content
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

"nixnote api rate limit exceeded" - Never resets #484

Open
donw9876 opened this issue May 23, 2019 · 5 comments
Open

"nixnote api rate limit exceeded" - Never resets #484

donw9876 opened this issue May 23, 2019 · 5 comments

Comments

@donw9876
Copy link

donw9876 commented May 23, 2019

Running version 2.0 on Mint 18.2 from the default Ubuntu repository. I syncd my notes from my existing Evernote account OK, but once the API limit boost apparently expired, I absolutely cannot sync the app with Evernote "ever" again. Every attempt, whether manual, automatic interval, or sync at shutdown, always fails. It appears to be the first internal attenpt, and I am NOT hammering the sync button. The "experimental restart on sync failure" just makes the Evernote server increase the wait time to try syncing. I'm done with this and deinstalling. Nice idea but this client is BROKEN for practical purposes, my searches for a fix have yielded nothing except repeating the symptoms I'm experiencing, and the program does not appear to be currently maintained, so this program is useless to me.

[code]
DEBUG 2019-05-23 12:31:43.099 ( communication/communicationmanager.cpp @ 159 ) Inside CommunicationManager::getUserInfo
ERROR 2019-05-23 12:31:43.358 ( communication/communicationmanager.cpp @ 178 ) EDAMSystemException
ERROR 2019-05-23 12:31:43.360 ( communication/communicationmanager.cpp @ 1192 ) EDAMSystemException Error Code: 19

ERROR 2019-05-23 12:31:43.360 ( communication/communicationmanager.cpp @ 1194 ) EDAMSystemException Rate Limit: 1722

INFO 2019-05-23 12:31:43.360 ( nixnote.cpp @ 1880 ) "API rate limit exceeded. Please try again in 29 minutes."
[/code]

@robert7
Copy link

robert7 commented May 26, 2019

It used to work well for me, but I'll recheck..

@robert7
Copy link

robert7 commented May 26, 2019

but did you check the new version?
The current version is 2.1.3 or 2.1.4 (development) - for 2.1+ see https://github.com/robert7/nixnote2
This repository is currently not maintained (as the maintainer is not reachable).

@donw9876
Copy link
Author

Robert7, thank you for the kick in the pants to pursue this issue. The version I installed originally (which had the continual sync problem) was labeled as version 2, from the Ubuntu standard repository.

I followed the link you provided and installed the PPA indicated. This allowed me to install (as shown in the program about box: 2019052621162.1.3ubuntu16.04.1.

I think I read that the sync boost only lasts 24 hours, and it has now been well past that. Sync now succeeds every time attempted.

All I need is sync of text notes, and even the smallest update failed previously with version 2. This works.

Thank you.

@donw9876
Copy link
Author

donw9876 commented Jun 1, 2019

A few more days on... surely the initial sync boost has terminated. Syncing is now error-free for the simple cases that I've tried. (I'm seeing a different annoying behavior with some notes being stuck "in conflict" for no apparent reason and sync doesn't address it completely. But it is a separate issue I'll work on confirming.)

@robert7
Copy link

robert7 commented Jun 6, 2019

Regarding the "upload limit" ... the limit is imposed on Evernote Server side... so Nixnote can't do much with it anyway.. just wait until the limit is lifted and retry (there is a retry loop in Nixnote, but it may not be perfect). I guess, the limit is per hour, if you cause too much traffic to your account in particular hour, then you need to wait until you can send further requests to server.

But in my case, if I'm not doing some mass note changes, I never hit the limit. So in the "daily business" you shouldn't experience it.

The conflict happens, if particular note is changed both on local side and on the cloud side. This usually happens if you modify same note with 2 instances of Evernote clients. If you only use one client with particular note, conflict should not happen.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants