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

Explorer not showing all registered transcoder nodes #434

dob opened this issue Jul 25, 2019 · 2 comments


Copy link

commented Jul 25, 2019

Describe the bug (required)
It looks like our explorer isn't showing all the transcoders for some reason. It lists only 23 active. After doing a comparison with Scout, I noticed these particular nodes are missing (in my view). Note also that Scout is missing some nodes, but it's not on us to debug their index:

Explorer is missing:

Scout is missing:

Expected behavior (required)
All registered nodes should be shown.

To Reproduce (required)
Steps to reproduce the behavior:

  1. Go to
  2. View the list of transcoders.
  3. Observe that the above mentioned nodes are missing.

Device (required):

  • Device: Macbook Pro, OS X, Chrome (and Brave)

Additional Context:

Adam had mentioned that the Graph node was updated recently. This may have introduced an issue.

@dob dob added the 🐛 bug label Jul 25, 2019


This comment has been minimized.

Copy link

commented Jul 25, 2019

Eli and I upgraded the Graph Node to the latest version yesterday, which seems to now paginate graphql query results (100 results per page). Currently, the explorer queries for all transcoders and then filters out those that are registered and active client-side. Since the latest Graph Node now paginates results, that means we're excluding some from the list. I've confirmed the two missing transcoders are on the second page of results.

I think I simple fix would be to include a filter on our transcoders query. ie:

  transcoders(where:{status: "Registered"}) {

This comment has been minimized.

Copy link

commented Jul 29, 2019

Fixed by #435

@iameli iameli closed this Jul 29, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
3 participants
You can’t perform that action at this time.