Anyone else seeing an error occur in BSync after the 600 calls/hour API limit change? I cannot even get BO and BL to sync anymore due to exceeding the limit from normal day-to-day activity. I've alerted Lawrence to the issue, just wondering if any others are experiencing issues.
Big B
Comments
BrickSync uses a single socket with HTTP pipelining (up to 8 requests in queue). The requests appear to be processed serially by BrickOwl, each taking 200-250ms. BrickSync then pipelines another request as soon as a reply is received, keeping the "in-flight" queue full. So, I had expected at most 300 calls per minute.
I can look into adding a rate limit though.
I think I had originally assumed people would have a dozen (or so) unknown BOIDs, at least for a couple days, until the information is submitted and added to the catalog.
I now know the reality is different :), hundreds of IDs can remain unmatched for years, stuff like minifig parts (torso, etc.) or stickered parts. These failing lookups should probably have an incrementing timer so it's not attempted again for a while.
INFO: Resolving BOIDs for all unknown BLIDs.
WARNING: BrickOwl HTTP Error - Saving server reply (288+0 bytes) at path "data/errors-2017-06-05/00000.txt".
WARNING: Bad reply from server, trying again shortly...
WARNING: BrickOwl HTTP Error - Saving server reply (288+0 bytes) at path "data/errors-2017-06-05/00001.txt".
WARNING: Bad reply from server, trying again shortly...
ERROR: Too many connection errors, giving up.
ERROR: Fatal error encountered.
ERROR: Exiting now.
It's probably related to the API key or its permissions.
Thinking about it, isn't that one needed to resolve ID's for example?
HTTP/1.0 429 Too Many Requests
Edit your BrickSync configuration file (bricksync/conf/bricksync.conf.txt), change this:
brickowl.pipelinequeue = 8;
to that:
brickowl.pipelinequeue = 1;
We'll need a better solution though...
However, I'm running some owlsubmitblid and on some BOID/BLID pairs I keep getting this each time:
14:50:57 WARNING: BrickOwl HTTP Error - Saving server reply (766+51 bytes) at path "data/errors-2017-06-07/00004.txt".
14:50:57 WARNING: Bad reply from server, trying again shortly...
14:50:57 WARNING: BrickOwl HTTP Error - Saving server reply (766+51 bytes) at path "data/errors-2017-06-07/00005.txt".
14:50:57 WARNING: Bad reply from server, trying again shortly...
14:50:57 ERROR: Too many connection errors, giving up.
whereas on others it works fine.
And check the error report to make sure the problem isn't something else.