-
Notifications
You must be signed in to change notification settings - Fork 43
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
Prevent sending deletions when pending changes reach 200 documents #228
Comments
Hi @jleandroperez i am seeing a huge amount of these errors logged when i am doing a complete dump of core data and then loading new objects, is there any way to make these warnings appear less frequently, it really bogs down the console, and the error logs. |
@gazzer82 just in case i'm not following you... are you getting lots of 'Error 503' right after a massive delete operation?. If so, we'll be adding logic to prevent that shortly. There's no other way to avoid those console errors (for now) rather than disabling logging. (Sorry about that, we'll tackle this issue soon!) |
@jleandroperez yeah just after a massive delete in core data, the syncing of that causes a lot of message to be logged, which seems to slow the application down somewhat (OSX). In fact, simperium seems really rather chatty even when i have the verbose logging disabled, is that intentional? |
@gazzer82 now that you mention it (after checking!) verbose = off is translated into 'Info' LogLevel (Ref.: https://github.com/Simperium/simperium-ios/blob/develop/Simperium/Simperium.m#L638). Let's change the default level to 'SPLogLevelsWarn'. #242 |
Closed via this pull request |
Reference: Issue #180
The text was updated successfully, but these errors were encountered: