-
-
Notifications
You must be signed in to change notification settings - Fork 266
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
0.8.0 issue with Authentication #934
Comments
Is your SSH key defined in WSL2 and added to GitHub or is your SSH key in Windows. If it's the latter, you have to configure your WSL2 environment by running the |
This is just a WIP writeup that covers all the steps I tried - windows, wsl, pre-compiled and compiled from source: http://freshbrewed-test.s3-website-us-east-1.amazonaws.com/2022/12/13/gitbug.html |
I tried: WSL https (my usual) with GH Public, Private and Azure DevOps private repos. I tried 0.8.0 and in WSL, also freshly compiled from main. |
I get the same error, under Ubuntu, pushing to a remote on github requiring username and password. Normal push and pull of repo works fine. |
I got same error with windows and Mac and Ubuntu. Do you have and path that
works with 0.8.0 I could try?
…On Wed, Nov 30, 2022, 6:08 PM KG ***@***.***> wrote:
I get the same error, under Ubuntu, pushing to a remote on github
requiring username and password. Normal push and pull of repo works fine.
—
Reply to this email directly, view it on GitHub
<#934 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABTDTVLTIG6DOEZYY27OCHDWK7UALANCNFSM6AAAAAASMKHZQM>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
I can replicate this issue ... |
git-bug 0.8.0 (haven't tried earlier releases) on MacOS and I also can't push/pull from remote with git-bug, while push/fetch/pull <--> remote works fine with git form the same repo using ssh keys. I tried to create
I'd be happy to troubleshoot further if I knew where to start. (Happy holidays btw :) |
@davidberglund the first I would try is to upgrade go-git (#947), as it seems there is improvement in that area: go-git/go-git#411 Unfortunately, it seems that this upgrade break things in git-bug, as well as coming with a CGO dependency ... If that doesn't help, maybe dig into go-git issues? |
#929 could be related |
I run the binary release. Is that with go-git 5.4.2? And is your suggestion that I try compiling git-bug from source with go-git 5.5.1? |
Go-git 5.4.2 doesn't have CGO, but the most recent do. Yes, try compiling with that last one and see if that fix this problem. Master is fairly unstable though, as it got a large refactor recently. |
I have the same issue after compiling from master. At least I didn't get any new problems AFAIK. |
Aha, my bad, I thought the tip was requiring 5.5.1, it referred to 5.4.2. I'll try again. |
Master doesn't have the updated go-git. |
Not very experienced with building go apps. How do I get passed or bypass the checksum mismatch that occurs upon running
I tried to run
|
It looks like something happened upstream. What if you checkout that dependabot PR and just |
That worked. I have the same authentication error with git-bug push/pull, though. |
Then it's likely an outstanding issue in go-git :-/ |
Ok, I think my main (tiny) contribution is going to be on this level as I'm not a go hacker. I'll keep subscribing to this issue at least. |
It's already useful! Maybe you could look for a matching issue in go-git, or open one? |
Also, could you confirm that there is no issue with git-bug v0.7.2 (try in a new repo to avoid data issue)? |
I can confirm that git-bug push/pull works fine with 0.7.2. and with the same repo + remote. |
Related? go-git/go-git#489 |
I've updated |
Are there some news about this issue? |
I had the following authentication error:
I fixed it by assigning a dedicated ssh config for the git repository's host like described here https://gist.github.com/rbialek/1012262 |
(the version is actually 0.8.0) |
I can confirm that binary taken from https://github.com/MichaelMure/git-bug/releases/tag/v0.8.0 fails to push or pull with error
Binary built from this tag works perfectly.
|
Which tag? |
0.8.0
…--
Mikhail :з
|
On Mon Feb 5, 2024 at 5:28 PM CET, Mike Kot (Михаил Кот) wrote:
0.8.0
So, they rewrote one with different commit? Awesome!
|
I had a similar problem. My issues were:
The solution to the first was to change the url with |
I setup 0.8.0 (Linux amd64) in WSL running Ubuntu 20.04 (focal) and git 2.25.1
I tried with an Org GH Repo, Personal GH repo and a freshly pulled AzDO repo.
I tried with 0.7.2 without issue.
I even tried migrating a working repo then using 0.8.0 and got the error again
The text was updated successfully, but these errors were encountered: