rmosolgo / rmosolgo/graphql-ruby

[PRO] Subscription Topics dashboard index appears to be out of date

Open
#5,259 9 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Ruby
Stars
5.4k
Forks
1.4k
Avg merge
23h 19m
Merged PRs (30d)
28

Description

Describe the bug

Sometimes when I click on a topic that I see listed in the dashboard, the list of subscriptions is blank. Then when i navigate back out to the index and refresh, that subscription is gone. It seems to be the act of viewing the topic refreshes the data or something?

https://github.com/user-attachments/assets/a34872f6-1c47-4bf0-808c-e0772d8cc90f

I am pretty sure these aren't just churning out while i'm looking at the page, because I can go back several pages and click on one to reproduce the behavior.

NOTE: we're using the Ably integration.

Versions

graphql version: graphql-pro (1.29.2)
rails (or other framework): 7.2.1

Steps to reproduce

  1. Click on various topics in the subscription index.
  2. Sometimes when you get onto the topics page, the page will be blank and have no subscriptions listed.

Expected behavior

The topic should not be listed if there are no longer subscribers

Actual behavior

The topic is appearing in the list despite having no subscribers (I think!)

Additional context

This may not be a huge problem, but I want to have confidence that the system is working properly and it's not attempting to send messages to old/unused topics.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the issue by opening several entries in the subscription topics index, then inspect the topic detail page and the Ably integration involved in loading subscriptions. Compare the index data with the detail result after refreshing. Done means topics with no subscribers no longer remain listed, with regression coverage for the observed mismatch.

Written by the indexing model from the issue text.

Assessment

Tech stack
graphql, rails, ruby
Domain
api, backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.