Subgraph is down

[benefacto]

index-3f0a3c7f.js:233 ApolloError: indexing_error
    at new a (index-3f0a3c7f.js:200:184)
    at g.toQueryResult (index-3f0a3c7f.js:206:11615)
    at g.useQuery (index-3f0a3c7f.js:206:7413)
    at useLazyQuery (index-3f0a3c7f.js:206:12360)
    at useCollectiveData (index-3f0a3c7f.js:233:70)
    at HomePage (index-3f0a3c7f.js:237:9757)
    at Xh (index-3f0a3c7f.js:38:20960)
    at dj (index-3f0a3c7f.js:40:3318)
    at Wk (index-3f0a3c7f.js:40:47416)
    at Vk (index-3f0a3c7f.js:40:42128)
(anonymous) @ index-3f0a3c7f.js:233
index-3f0a3c7f.js:237 undefined
index-3f0a3c7f.js:233 ApolloError: indexing_error
    at new a (index-3f0a3c7f.js:200:184)
    at index-3f0a3c7f.js:204:99107
    at b0 (index-3f0a3c7f.js:199:10095)
    at index-3f0a3c7f.js:199:10002
    at new Promise (<anonymous>)
    at Object.then (index-3f0a3c7f.js:199:9967)
    at Object.next (index-3f0a3c7f.js:199:10109)
    at notifySubscription (index-3f0a3c7f.js:199:2415)
    at onNotify (index-3f0a3c7f.js:199:2926)
    at a.next (index-3f0a3c7f.js:199:3560)

This is blocking additional development and @Joshua-Jack is working on resolving it.

[benefacto]

Fix did not resolve the issue. It might be worth getting the subgraph working locally to start pushing some of the features forward.

[L03TJ3]

@benefacto @sirpy is this just a local issue? is this a specific subgraph issue which should be reported to them?

[benefacto]

@benefacto @sirpy is this just a local issue? is this a specific subgraph issue which should be reported to them?

@L03TJ3 This was an issue with the hosted subgraph currently used in the latest preview environment. I just rechecked and it looks like it's back up again, though, but I'm not aware of what change @Joshua-Jack may have made to bring it up again.

[benefacto]

I spoke too soon. It looks like the indexing errors are now not occurring on the main page but on the subpages. Main collective page loads: But click on any collective and you'll note that indexing_error is still occurring. Further debugging within the subgraph is needed (this is not an Apollo side issue):

[benefacto]

indexing errors are now not occurring on the main page

Indexing errors are back on the main page again:

[Joshua-Jack]

Error: transaction 1938d4396ef2cbfca8e646ad6b14c40f9a87bca9abe947c1e9122ad1a8bda42c: Mapping aborted at generated/schema.ts, line 944, column 7, with message: Cannot return null for a required field. wasm backtrace: 0: 0x4415 - !src/mappings/pool/handleRewardClaim in handler handleRewardClaim at block #22527608 (280b04ab821ddba7745bc205dedd32bf3df0a62af35292cdce0edd6de8992815)

To view more details about this indexing error, please view the documentation.

[benefacto]

Deployment steps:

1. prepare script
2. prepare:celo (includes an auth key secret that should probably be removed)
3. build:copyabi or yarn codegen to pull updated ABIs

[benefacto]

Next steps:

• @sirpy may publish the subgraph publicly so that the errors are accessible to more than the account who owns it
• @benefacto to debug the subgraph errors as needed or otherwise proceed on other work (which a working subgraph should unblock)

[benefacto]

This issue should now be resolved with the new, indexed subgraph. Feel free to verify at the latest preview deployment: https://good-collective-7ssf2sna9-gooddollarteam.vercel.app/

[vldkhh]

@benefacto it still reproduces for me. You can see the link above in the picture

[benefacto]

@benefacto it still reproduces for me. You can see the link above in the picture

@vldkhh The image you attached does not bear relevance to this ticket. This image signifies different errors which may or may not be affecting the app and might warrant further investigation. Since you can navigate to the donation page, this signifies that the subgraph is back up as expected. The latest preview environment is here and corresponds to the latest deployment on this pull request (all preview links can be accessed there).

[krisbitney]

What is the status of this? @vldkhh

[vldkhh]

@krisbitney fixed

[krisbitney]

Awesome