This message was deleted.
# report-bugs
s
This message was deleted.
c
oh hm, I skipped something
j
@Alyssa Baum, can you take a look please?
👍 1
c
oh this is weird
every other one fails.
well, it seems like it's corrected itself, now that I've rewritten the history of the problem branch
a
Taking a look, what branch was checked out when you were running
c
I think the first time I saw it is when I was on
main
and did a
gt sr
j
The first issue should be fixed in a CLI version we released today
let is know if you still see the second issue
c
nice. will do
the repo is public if you want to look at that. https://github.com/lavamoat/lavamoat
I'm still having this problem
.git/refs/gt-fetch-head
is completely empty fwiw
in my
.git/config
, this is the data for the branch:
Copy code
[branch "boneskull/policy-schema"]
      remote = origin
      rebase = true
  github-pr-owner-number = "LavaMoat#LavaMoat#620"
  github-pr-base-branch = "LavaMoat#LavaMoat#main"
      merge = refs/heads/boneskull/policy-schema
the above
gt downstack get --force
works every other time I run it. I feel like you might want a debug log
unless you have it already
cc @Alyssa Baum
this looks suspicious to me:
Copy code
2023-08-30T17:49:18.734Z: Finished git fetch --no-write-fetch-head -f origin boneskull/policy-schema:refs/gt-fetch-head/boneskull/policy-schema
{
  "code": 0,
  "signal": null,
  "stdout": "",
  "stderr": "From <https://github.com/LavaMoat/LavaMoat>\n - [deleted]             (none)     -> refs/gt-fetch-head/boneskull/policy-schema\n"
}
a
Taking a look
j
Yeah, that output in the debug log does seem rather suspicious. Does it consistently show up as deleted every other time? (i.e. that's the cause it's failing every other time)
c
@Jacob Gold yes
still having this problem with v0.22.10