Skip to content
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

GraphQL: indexing_error should only be returned if the subgraph has non-fatal errors feature enabled #3663

Closed
evaporei opened this issue Jun 13, 2022 · 3 comments · Fixed by #3662
Assignees

Comments

@evaporei
Copy link
Contributor

An example was brought up by @itsjerryokolo with this subgraph https://thegraph.com/hosted-service/subgraph/astox/main, where it was synced up to chain head, but the errors wouldn't display in the playground, even with the subgraphError: allow.

Screenshot 2022-05-30 at 11 46 53 AM

This function is incomplete as described by @leoyvens

pub(crate) fn has_non_fatal_errors(
, it returns true even if the subgraph doesn't use the non-fatal errors feature enabled.

@leoyvens
Copy link
Collaborator

Actually we should return indexing_error for a subgraph failed with a deterministic error, even if non-fatal errors is disabled. So maybe the code is already behaving as expected, and the function just needs to be renamed and clarified.

@azf20
Copy link
Contributor

azf20 commented Jun 21, 2022

@leoyvens in that case is this about renaming, rather than a functionality issue?

@leoyvens
Copy link
Collaborator

Yes at this point this is just tracking the refactor in #3662.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants