This message was deleted.
# report-bugs
s
This message was deleted.
p
Is this specifically in the review queue, on the PR page or both?
b
I’m noticing it on the review queue.
p
Looking into this!
b
Thank you!
j
Can you send me an example PR org/repo/number? Note that if the PR was in a stack, but its base branch was merged, and it hasn't yet had its base change to the trunk branch, then we might be basing this on GitHub's (now inaccurate) calculation
that one is based on
main
, but shows as waiting for reviewers in the list, even though it’s been approved. @Jacob Gold
I can wait on merging it until tomorrow so you can dig into its current state
j
Thanks!
b
Checking in — if I merge this PR, will you still be able to debug this state?
j
Just looked and I think we got everything we need, so you're good to merge. This class of issue is interesting as we didn't change anything here recently — github seems to have changed some logic around one of their api response fields. The good news is that we were planning on doing more of these calculations on our end, but I'm not sure quite when that change is going to roll out.
b
Awesome, I’ll merge then. FWIW, I’ve noticed this happening for about as long as I’ve been using Graphite, so it might be a long-standing issue that I’m hitting for some reason
It’s confusing though — since it’s not a more widely reported issue on this Slack, maybe it’s something about me or the repo.