The <app.graphite.dev> web app chronically display...
# report-bugsz
Zach S
10/31/2025, 2:11 PMThe app.graphite.dev web app chronically displays the wrong number of unresolved comments in large stacks.
That is, when I have a stack with upwards of 3 or 4 PRs, I often see "1/2 <Unresolved Comments>" or "2/3 <Unresolved Comments>" next to PRs in the stack but then when I click on the PR, I don't see any unresolved comments and then indeed the list view shows all resolved.
I don't want to get too into the weeds, but if I leave that PR open for a few seconds longer, I notice the list view toggle back and forth every 30s or so between the correct and incorrect comment count.
We use multiple AI code review bots (including Graphite's) and most of our PRs have 2+ human reviewers. It's very plausible that there could be new comments, and it's important that I follow up on all of them. These incorrect counts end up wasting a lot of my time.
I'll comment with more diagnosis if interested but this is a definite bug and wastes a lot of my time.
p
Pylon
10/31/2025, 2:11 PM(If applicable) To help us repro, please send the following if you haven't already:
- PR links, screenshots, and/or debug output if applicable
- Repro steps
- Does this happen consistently? Just to you or others on your team also?
- Is this a regression? Is the problem new?
- If you're having an issue with the CLI, please send us debug logs using
gt feedback --with-debug-context <any message>z
Zach S
10/31/2025, 2:13 PMTo me, it seems like you have two competing sync timers, one for the list of PRs, and one for the currently-open PR.
If I had to guess, I'd say the sync operation for the currently-open PR is getting the correct information, and the sync operation for the PR list is getting the stale information.
Zach S
10/31/2025, 2:13 PMNote that a hard refresh does not solve this - I guess some server-side caching is happening.
Zach S
10/31/2025, 2:22 PMOkay from my browser network tab I can see which routes are problematic:
When I load a given PR in the stack, this route loads the correct information:
<https://app.graphite.dev/api/v1/graphite/github-pr/><my org>/<my repo>/<pr number> Copy code
"unresolvedThreadCount": 0,
"totalThreadCount": 2,
"branch": "MY BRANCH NAME",<https://app.graphite.dev/api/v1/graphite/pr-stack/><SOME LONG UID> Copy code
"unresolvedThreadCount": 1,
"totalThreadCount": 2,
"branch": "MY BRANCH NAME",Zach S
10/31/2025, 2:23 PMThere's a famous saying:
There are 2 hard problems in computer science: cache invalidation, naming things, and off-by-1 errors.It must be some kind of cache invalidation error
p
Pylon
10/31/2025, 3:08 PMhey Zach, apologies for the rough experience here and thank you providing all those details. I will append them in an internal tracking issue for this.
To help with that could you please use the
Send feedbackGFz
Zach S
10/31/2025, 3:10 PMOkay I submitted that as feedback in the graphite app @Gareth Brickman
👍 1
m
Matthew Smith
10/31/2025, 4:25 PMsame here
Matthew Smith
10/31/2025, 4:25 PMthis is game breaking for mke
p
Pylon
10/31/2025, 4:28 PMhey Matthew, we're investigating this. Please also send in-app feedback for your impacted stack and we'll add to our internal tracking issue.
m
Matthew Smith
10/31/2025, 4:29 PMsendt feedback via CLI and sent you a loom below
z
Zach S
10/31/2025, 4:29 PMThis is mega bad @Gareth Brickman
The "merge" buttons literally don't let you merge when there are unresolved comments including when graphite thinks there are unresolved comments.
Forcing us to play whack-a-mole with this webapp bug to merge possibly time-sensitive changes
m
Matthew Smith
10/31/2025, 4:29 PMye see my loom below
Matthew Smith
10/31/2025, 4:29 PMconvinced my whole team to test this and now its a big issue
p
Pylon
10/31/2025, 4:30 PMI understand, we are escalating it and will keep you updated.
Pylon
10/31/2025, 6:16 PMhey Zach and Matthew, thanks for bearing with us and apologies for the inconvenience. The team has confirmed this is a caching issue on our end and they're investigating a long-term fix to it.
In the near-term, selecting the individual PRs in the stack is expected to force the cache to update with the correct status, as Zach has indicated. Please let me know if any PR's status isn't updated or reverts to an incorrect one.
z
Zach S
11/12/2025, 9:09 PMHi @Gareth Brickman I'm experiencing this today 2025-11-12 FYI
p
Pylon
11/12/2025, 9:21 PMhey Zach, affirmative. There hasn't been a permanent fix deployed for it yet so the workaround above is still necessary in these cases.
z
Zach S
11/12/2025, 9:51 PMBummer! Hopefully there's some progress on it.