This has been happening often in `gt sync`. It alw...
# report-bugs
t
This has been happening often in
gt sync
. It always succeeds on retry.
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 Tyler, next time it happens can you please run
gt feedback --with-debug-context <message>
to send us your CLI logs?
👍 1
t
Sent!
p
I think this is a case of too many parallel GPG signing operations caused by your sync when you have a large number of branches. The GPG processes collectively exceeded available memory. One idea i can think of when you have a large number of branches locally and don't need to sync all at a given moment is to substitute
gt get
for the
gt sync
which will sync just the stack for the current PR and not other stacks.
t
Ooh nice tip. I forgot
gt get
works without an argument