This message was deleted.
# report-bugs
s
This message was deleted.
šŸ‘€ 1
b
If I had to guess, Graphite might think these PRs are still merging because CI on
main
was broken when they tried to merge. Is this a known issue? (example PR)
And if it is a known issue, is there a way to get them out of the list?
Ping in case my message slipped by, @Pranathi Peri
p
Hi sorry about that! Let me look into it!
@Ben Jaffe, could you send a screenshot of what the filter conditions on this section are?
It's possible that the "last updated" condition could be very large in this scenario
Also, is this just a "merging" section or both "merging/recently merged?"
b
Also I noticed that the alt text for the merged icon says ā€œMergedā€ in the list.
p
I see, I think the merging/rebasing filters could be a bit buggy - looking at a fix! Thanks for reporting this!
b
Thank you!
p
We killed some jobs last night so this may be fixed!! Let me know if it's still an issue
b
Alas, no… they’re still showing up
@Pranathi Peri Reviving this — is there something I can do to get those old PRs out of the Merging section? The top two are currently merging, but the rest have been there for weeks. I believe they all had CI failures when they landed on
main
, which might be a clue.
p
cc @Jacob Gold
a
IIUC @Ben Jaffe you only want to see the currently "merging" PRs there? And not merged ones?
Or is the issue that a PR failed to merge, and now is stuck in the merging section?
b
Actually, not quite either. The PRs that are stuck have successfully merged, and graphite knows this (at least in the status icon)
Almost all of them had CI failures
but they merged just fine (we had a CI outage, and the PRs were safe to merge). So it seems like they’re in a weird state on the Graphite side and not getting unstuck. Here’s the section settings, for completeness.
a
Ah, and these should be filtered our from the
merging
section?
b
Yes, I’d expect them to not show up because they sucessfully merged.
a
Yes that is reasonable
Let me take a look
b
thank you!
j
what are their PR numbers?
b
3405, 3404, 3403, 3337, 3327, 3201
a
@Ben Jaffe what is your github handle?
j
ah, I think I have a fix for this
graphite 1
try refreshing!
b
@Aryaman benjaffe
@Jacob Gold OMG YOU ARE MY HERO!
It worked!
What was the issue?
j
we had some bad rows in the db 😬
b
I’m very grateful, thank you.
I have one remaining issue with all this state around people approving PRs, but they don’t change from ā€œWaiting for reviewersā€ to ā€œApprovedā€, but I’m guessing that’s unrelated to this
Does ā€œReview status is: Approvedā€ mean one or more approval?
a
You should see improvements in the accuracy of the sections coming soon.
b
oh okay awesome!
I’ll wait then šŸ˜„
graphite 1
j
I believe for approval status the issue is related to the GitHub API returning an incorrect calculation of whether the PR is accepted — we're improving our own derivations of this sort of thing šŸ™‚
ā¤ļø 1