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.

Sign up for GitHub

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

Jump to bottom

Intermittent failure to detect a provider with trace support #3204

Closed
azf20 opened this issue Jan 31, 2022 · 2 comments
Closed

Intermittent failure to detect a provider with trace support #3204

azf20 opened this issue Jan 31, 2022 · 2 comments

Comments

@azf20
Copy link
Contributor

azf20 commented Jan 31, 2022 •
edited

Affected subgraphs fail to start, logs show:

Failed to start subgraph...
error: expected triggers adapter that matches deployment Qm.. with required capabilities: traces: ... was not found

Even though there was a configured provider with traces at the time. This coincided with receiving 50x errors from the RPC endpoint, which may be related.

This was recently observed indexing xDai on the Hosted service for nifty.ink, DAOstack, 1hive
@leoyvens
Copy link
Collaborator

If the provider is considered defective at startup due to returning too many errors, then this can happen even if it is present in the configuration.

@azf20 azf20 mentioned this issue Apr 13, 2023
Closed
@azf20
Copy link
Contributor Author

azf20 commented May 10, 2023

Duplicate of #3937

@azf20 azf20 marked this as a duplicate of #3937 May 10, 2023
@azf20 azf20 closed this as not planned Won't fix, can't repro, duplicate, stale May 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@azf20 @leoyvens