I’m getting this on one of my projects:
This was working a couple of weeks ago on for this project. Just opened it up again today and this happened.
I’m getting this on one of my projects:
This was working a couple of weeks ago on for this project. Just opened it up again today and this happened.
I ended up using gh auth login
and it worked fine. Thought maybe there would be a way to do it like IDX does it initially though.
That is interesting! If I understand this correctly…
The Github workflow worked when you opened the project initially a few weeks ago. When you opened the project today, the auth token expired. Instead of triggering the original Github auth flow, you had to use the command line.
Is that right?
That’s correct. … (adding dots to get to 20 characters).
@kirupac I just opened another project, it was in the “archived” state, and same thing happened. So maybe this is related to a project getting archived.
Oh that is a good data point to have! Let me share this with the team and see what we can do here.
It’s for sure due to archiving. Every time I load a workspace that has been archived this happens.
Actually, I just tried it this morning and it asked me for the GitHub auth flow again automatically. So maybe this got fixed?
And nope, it is not fixed. Just unarchived another project and had to gh auth login
to get it to work.
Still not fixed FYI…
Was this also on another unarchived project?
Yes. Every time. And I don’t know if it’s just me but things seem to get archived faster than before.
Good to know. We’ll mark this as something to investigate quickly.
Same here!
I spent some work and I really don’t want to copy paste everything!
Thanks for the tip!
This is happening in recent, non archived workspaces now.
Ok, happens every time I open a workspace now…
Oh no. Something must have gotten broken somewhere. Following up with the team on this.
Hey @treeder ,
The log “Skip silent fetch commands” indicates that this may be working by design, i.e. are you using the git.autofetch
setting by any chance as described here?
Will autofetch make something that used to work stop working all of a sudden?
The main problem is I can’t push new commits every time I reopen a workspace. This issue started a few days ago.
hm, interesting, so when you attempt to manually do a git pull/push, do you see this error in the log “Skip silent fetch commands”?
Also worth noting that the auth token is stored in your browser, so switching to a different browser/clearing browser storage would cause reauth to happen. Are you doing any of those by any chance?