https://linen.dev logo
Join Slack
Powered by
i don't understand this error :thinking: (there ar...
# report-bugs
s
i don't understand this error thinking (there are no pending CI checks btw - all are green)
✅ 1
p
(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>
Hey Sifar could you share a link to the PR youre seeing this on
s
i did a 
gt submit
though... (so error disappeared)
hey, is there anyway i can DM you ? (to share the PR link)
p
you know you have a direct channel with us in slack, right? search 
ext-graphite....
s
ohh i didn't knw. sending there.
👍 1
j
We're also facing this issue btw. It's super annoying. Seems to have changed int he last week or so. We face flakiness at times (especially with GitHub lately) and now we're forced to manually resync. It's slowing us down quite a bit.
p
Happy to take a look, can you share a link to an example PR?
a
+1
p
(btw i just realized the slack channel might be named differnelty for me and you)
a
I was running into the error mentioned above on this stack - https://app.graphite.com/github/pr/bastionplatforms/monorepo/15627 I have since rebased the stack, which caused the error to go away. But hopefully this helps. If I run into the issue again I'll paste a link with the stack before rebasing
p
this is helpful thanks. Both times this failed on account of 
Failed CI (Meta Check)
 . the second time the failure was on the speculative-merge draft PR (#15678)
draft #15665 was the other time we saw failure for same reason
a
yeah i know why the speculative-merge draft PR failed CI
the issue is that I couldn't put it back in merge q without restacking
like @Jameel Al-Aziz mentioned, our CI can be a bit flaky, so ideally we'd be able to put it back in merge queue without having to go through the added time of restacking + rerunning CI
p
ah i see now 🤔 definitelty let me know the next one you hit live so i can look into closer, will in the meantime look into that merge blocking card to understand the circumstances around it
👍 1
j
Brett, this was a change on Graphite's side that is breaking workflows
this is not an issue on our end
We've been Graphite users for well over two years now and we only started seeing the "Merge queue failed on current head" message last week and it's completely broken our flow.
p
thanks
j
We used to be able to add a PR back on the merge queue after a flaky merge queue failure, now we cannot. That is a BUG.
p
okay i think i can turn this off for you for now, in the longer term we will re-enable it with an option to restack in the UI
👍 1
🙏 1
should be off now. Let me know if you continue to run into it
a
thank you, we will test it out and let you know
j
thank you Brett!
4 Views
Open in Slack
PreviousNext
Powered by