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
err:XPTY0004 expression to the left of a lookup operator needs to be a sequence of maps or arrays [at line 145, column 44, source: /db/apps/twitter/modules/twitter-downloader.xqm] In function: twitter-dl:download-last-json(xs:unsignedLong?)
Submitting a subsequent user-timeline() request in eXide returns the following response indicating why the download failed:
<hc:responsexmlns:hc="http://expath.org/ns/http-client"status="429"message="Too Many Requests"spent-millis="241">
<hc:headername="content-length"value="56"/>
<hc:headername="content-type"value="application/json;charset=utf-8"/>
<hc:headername="date"value="Fri, 10 Jun 2016 14:29:59 GMT"/>
<hc:headername="server"value="tsa_b"/>
<hc:headername="strict-transport-security"value="max-age=631138519"/>
<hc:headername="x-connection-hash"value="e5771896d2cb604eaf24fdb8620977ae"/>
<hc:headername="x-rate-limit-limit"value="180"/>
<hc:headername="x-rate-limit-remaining"value="0"/>
<hc:headername="x-rate-limit-reset"value="1465569208"/>
<hc:headername="x-response-time"value="7"/>
<hc:bodymedia-type="application/json"/>
</hc:response>
I wonder too if it might be more efficient to request more than 1 tweet at a time (as I understand the code), and store the json at the same time we store the xml, since now we have to submit duplicate requests.
The text was updated successfully, but these errors were encountered:
To reproduce the error I just got: clear the
import
directory, start http://localhost:8080/exist/apps/twitter/jobs/download-recent-twitter-json.xq. Errors out after 180 requests, with the following error:Submitting a subsequent
user-timeline()
request in eXide returns the following response indicating why the download failed:I wonder too if it might be more efficient to request more than 1 tweet at a time (as I understand the code), and store the json at the same time we store the xml, since now we have to submit duplicate requests.
The text was updated successfully, but these errors were encountered: