By the reason of issue with Wrong History object calculation for P3A I missed the moment when many users had reached the limit of synced objects per chain on the server. Their devices received OVER_QUOTA error on commit and Sync stopped to work.
This PR increases limit of synced objects on the server from 50k to 75k and among others PRs must improve the situation.
Test plan
Configure Browser sync against the local server limit 50000, enable history and bookmarks;
Create 50000 history entries, ensure the server is overfilled
Open brave://inspect/#extensions , click inspect near the Brave extension, paste
for (i=0;i<50001;++i) chrome.history.addUrl({url: 'https://search.brave.com/search?q='+i+'&source=web'}, function() {})
into the console
Shotdown server, close browser
Change server limit to 75k, rebuild and start server
Launch browser
Ensure server accepts the records from the client
Screenshots
|Description|Screenshot
--|--|--
1|Normal History commits, not yet reached the 50k limit|
2|TRANSIENT_ERROR, reached server limit|
3|Re-built server with increased to 75k objects limit, re-started browser|
Resolves https://github.com/brave/go-sync/issues/198
Description
By the reason of issue with Wrong History object calculation for P3A I missed the moment when many users had reached the limit of synced objects per chain on the server. Their devices received
OVER_QUOTAerror on commit and Sync stopped to work.This PR increases limit of synced objects on the server from 50k to 75k and among others PRs must improve the situation.
Test plan
inspectnear the Brave extension, pasteinto the console
Screenshots
|Description|Screenshot
--|--|-- 1|Normal History commits, not yet reached the 50k limit|
2|TRANSIENT_ERROR, reached server limit|
3|Re-built server with increased to 75k objects limit, re-started browser|