[Bug] Datasources for IPFS Metadata: Not found on polling Log Error

[emmajane1313]

Bug report

My subgraph uses custom datasource handlers for handling IPFS JSON metadata: https://github.com/DIGITALAX/OpenAction-Contract-Library/blob/main/print-library/src/ds-handlers.ts

Each ipfs file is a small text file less than 1.5KB. All attempts from the subgraph to fetch the IPFS data and have it handled through the datasource handlers are failing with this logged error: not found on polling, object_id: Qmf4YYZJBaHayVu4zoJ9qjTr7c7frB5A3WvRW9Cw4aZMW8 (object_id changes according to ipfs hash).

The file size is very small and indexes straight away on my infura gateway.

I was suggested to move to datasources a few weeks back to avoid these timeout issues.

I waited for 24 hours yesterday to see if it would succeed with time. It didn't. So i redeployed all contracts and a new subgraph to see if that would change anything. The timeout errors are still persisting.

Relevant log output

not found on polling, object_id: Qmf4YYZJBaHayVu4zoJ9qjTr7c7frB5A3WvRW9Cw4aZMW8` (object_id changes according to ipfs hash).

IPFS hash

QmdwMQ4qbkuBtMA7agbkBRfmYmV2VtP1RHtFGJxx7mQyKj

Subgraph name or link to explorer

https://thegraph.com/hosted-service/subgraph/digitalax/print-library

Some information to help us out

• [ ] Tick this box if this bug is caused by a regression found in the latest release.
• [X] Tick this box if this bug is specific to the hosted service.
• [X] I have searched the issue tracker to make sure this issue is not a duplicate.

OS information

None

[azf20]

Hey @emmajane1313 - the polling should retry after some time if it times out, do you see that some files are never found? Where are these files pinned?

[emmajane1313]

It eventually gets pinned but it takes up to 3 days. Is that expected?

The pinned files are stringified jsons (nft metadata basically), for example : ipfs://QmXQtfNCjXuVTNGnNXZ7mESA9h5iAaQNFkHCbqYQEPS4Af

[mubarak117136]

hey, I am facing same issue. Subgraph log:

1. Create data source, params: QmWSTue85CLBBkatmA9hR4qwF1UafSedkj9HM9BhG44Fqc
2. not found on polling, object_id: QmWSTue85CLBBkatmA9hR4qwF1UafSedkj9HM9BhG44Fqc

but this hash is available on https://ipfs.io/ipfs/QmWSTue85CLBBkatmA9hR4qwF1UafSedkj9HM9BhG44Fqc

github repository for full source code: https://github.com/mubarak117136/subgraph-test

i am pretty new here, any suggestion is lifesaver for me. thanks

[azf20]

hey @emmajane1313 thanks, that isn't expected, we are taking a look - @mubarak117136 do you have a subgraph deployed where you are also facing this issue?

[V1d0r]

Was there any update on this issue?

I'm seeing similar logs and behaviour for recently pinned IPFS files. Example:

Apr 15 10:22:07.077 DEBG not found on polling, object_id: QmRHGcHrteDW5MHsqQJA9ujbmKg33R3YkJZhbXoaKRc5LE, sgd: 25, subgraph_id: QmPyUMKPobzB3z6siQz6nXMvEem3KqqvdFdHBQBMTgrUDv, component: SubgraphInstanceManager Apr 15 10:22:07.117 DEBG not found on polling, object_id: QmPe8Yd2eEL2aXpGHPwwWYchdPvsfFt7QUpqnEcVXEKgs6, sgd: 25, subgraph_id: QmPyUMKPobzB3z6siQz6nXMvEem3KqqvdFdHBQBMTgrUDv, component: SubgraphInstanceManager

[ifavo]

I'm also running into this issue, somehow some IDs can be load while others are not. They are however available and pinned on multiple systems. Anyone has any ideas or suggestions on how to debug this?