-
Notifications
You must be signed in to change notification settings - Fork 119
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
web3 pinning service returns invalid PinStatus object #1221
Labels
kind/bug
A bug in existing code (including security flaws)
need/triage
Needs initial labeling and prioritization
topic/psa
Comments
SgtPooki
added
kind/bug
A bug in existing code (including security flaws)
need/triage
Needs initial labeling and prioritization
labels
Apr 5, 2022
@mbommerez FYI - would be great to do alongside the rest of the PSA cleanup! |
Can we re-open this until it's deployed on to the web3.storage pinning service endpoint?
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
kind/bug
A bug in existing code (including security flaws)
need/triage
Needs initial labeling and prioritization
topic/psa
I am working on ipfs/pinning-services-api-spec#64 and ipfs-shipyard/pinning-service-compliance#4. While attempting to delete all existing pins, I ran into an error with web3.storage's pinning service because the PinResults returned has the property
requestId
instead ofrequestid
.Check the spec at https://ipfs.github.io/pinning-services-api-spec/#tag/pins/paths/~1pins/get:
Compliance report:
Request - GET: https://api.web3.storage/pins?status=failed%2Cpinned%2Cpinning%2Cqueued
Headers
Body
Response - OK (200)
Headers
Body
The text was updated successfully, but these errors were encountered: