-
Notifications
You must be signed in to change notification settings - Fork 1
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
Add handler for GET /pins?cids=baf1,...,bafN
#63
Comments
Add handler for GET /pins?cids=baf1,...,bafN closes #63
This is deployed to staging but currently throws an error if more than 1 CID is passed as the |
As discussed, the issue was due a timeout in the lambda. the deploy was set to a 10 second value. Moved it to 60 seconds to be sure. The pickup performance instead are really fast. |
@codeflyer the aws http gateway times out after 30s max waiting for a lambda to respond. We can probably set the lambda timeout to 31s. the request will have already been closed if it takes longer. |
we need to handle batch pin status requests where the list of CIDs to check are passed as a comma separated string of cids under the key
cids
in the URLSearchParamsit's used by the cron-pins scheduled task that runs regularly to poll cluster to see if the pins that were previously Queued are have changed state yet via the cluster client lib
cluster.statusAll
cluster.statusAll
- https://github.com/web3-storage/web3.storage/blob/272c83b860c5d15a48c05d3cedb2063b26ca8abe/packages/cron/src/jobs/pins.js#L174cluster.statusAll
- https://github.com/nftstorage/ipfs-cluster/blob/02a4c1d0f4cbe86557abd738be83bb2de25ccec0/src/index.js#L189The text was updated successfully, but these errors were encountered: