Graphite Community

Screenshot 2023-08-11 at 2.27.46 PM.png

Are you trying `get` a branch with an ancestor that has already been merged? I think there is a bug in that case that we haven't squashed yet.

We should add a request-id here for debugging like we did for `submit` — cc <@U05597DUYDD> /<@U05D5ADT4K1>

<@U02RREE9GKH> yep, just checked - that does seem true

<@U02RREE9GKH> happening again on a different branch - things have been merged to master since the branch was created, but it wasnt branched off of some other previously merged stack/branch - its just a handufl of commits out of date. Seems weird

I added some more logging over the weekend, let me see what might be happening

At the time you originally ran this command, had it not been submitted by someone using Graphite?

I'm seeing that we didn't have a record of the depdencies of this branch until about half an hour ago (~10PM UTC)

ah, yeah the author is not using `gt`. I used to be able to grab arbitrary PRs, regardless of creation source (`git` vs `gt`)

Hmm, I don't remember us ever supporting that via `downstack get` but I think it shouldn't be hard to add

I suspect it may never have been officially supported, but it definitely worked for a long-ish period of time

yeah, at least now you'll know why it's failed — let me know if you do see this unexpectedly again though!