Hi Eric,

Sorry for the issue. Can you please press the Debug button in the
dialog and tell me some more about the `response` variable you should
see in the top context? For example what is the `response code` (401
or 403) or the `response content`? I would ask for the whole object,
but it also contains the request and that should contain your
credentials in the headers, which I don't want to see obviously. :-)
Could you please inspect whether the `response request` actually
contains authentication headers? I have seen in the past that
sometimes the WebClient does not send them when it should.

If you restart the context in the debugger (should be either
GitSmartHTTPProtocol>>#discoverReferencesForService: or
GitSmartHTTPProtocol>>#invokeReceivePackWithRefs:andPack:deleting:) to
repeat the request, does the same error occur again or does it work on
second try? If the WebClient shows further problems, you can also try
to restart the topmost SquitBrowser context that you find on the
stack.

About backing out: like Fabio said, the Git history is all on your
disk and you can still pull/push/... with the Git command line. To see
the files, you just have to checkout a commit (or reset --hard to see
the latest files on the branch). Then you will find everything in
filetree format (or Tonel if you configured it so). A converter exists
for Monticello->Squot (see
https://github.com/hpi-swa/Squot/#converting-monticello-history), but
not for the other way around, since Squot repositories are just
metadata-less filetree repositories. If someone really wants to build
a converter for the other direction, they could probably learn from
the existing converter and turn the read/write logic around. However,
I would rather like to find and fix your push issue.

Kind regards,
Jakob

Am Sa., 11. Juli 2020 um 08:43 Uhr schrieb Fabio Niephaus <lists at fniephaus.com>:
>
> Hi Eric:
>
> On Sat, Jul 11, 2020 at 2:07 AM Eric Gade <eric.gade at gmail.com> wrote:
> >
> > Hi all,
> >
> > I have a project I've been working on using Squot and the new Git tools and pushing to a repository I have on Github. The repository is private but works with my username and password. I have been successfully pushing commits to it for a couple of weeks from the same image. This includes commits that I made yesterday. But today, suddenly, I am no longer able to push to my remote. Instead, I get the error in the attached image.
> >
>
> Sorry to hear you're having issues pushing to remote from your image.
> I have no idea what's going on, maybe renew your access token and try
> again? What OS/VM/image are you using?
>
> > Note that I have not changed any Github settings or anything like that. So I'm not sure what has changed or what's going on. Any ideas?  Is anyone else having this issue? If I wish to find a way to "back out" of using Squot, is there some way to convert everything to Monticello (filetree) and just push it manually from my terminal?
> >
>
> No need to back out of using Squot just yet: when you added your
> project, the GitBrowser asked you for a local directory. Although
> Squot does not touch the working copy on the filesystem (the files
> that end up on GitHub), it does keep the repository metadata
> (everything in .git) in sync. So that means you can just push from
> your terminal from your filesystem repository. This use case is one of
> many reasons why Squot asks for a local directory.
>
> Hope this helps,
> Fabio
>
> > --
> > Eric
> >
>