eureka: Error when pushing commit
Hi
Thanks for sharing this program! I can see it being very useful in my workflow. Unfortunately I seem to be encountering a problem. Trying the latest release and git versions, I get this error message:
Adding and committing your new idea..
Added and committed!
Pushing your new idea..
thread 'main' panicked at 'called `Option::unwrap()` on a `None` value', /home/barbarossa/.cargo/registry/src/github.com-1ecc6299db9ec823/eureka-1.8.1/src/git.rs:88:47
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
thread 'main' panicked at 'Box<Any>', /home/barbarossa/.cargo/registry/src/github.com-1ecc6299db9ec823/git2-0.13.17/src/panic.rs:27:9
With RUST_BACKTRACE=1 I get:
Adding and committing your new idea..
Added and committed!
Pushing your new idea..
thread 'main' panicked at 'called `Option::unwrap()` on a `None` value', /home/barbarossa/.cargo/registry/src/github.com-1ecc6299db9ec823/eureka-1.8.1/src/git.rs:88:47
stack backtrace:
0: rust_begin_unwind
at /build/rust/src/rustc-1.49.0-src/library/std/src/panicking.rs:495:5
1: core::panicking::panic_fmt
at /build/rust/src/rustc-1.49.0-src/library/core/src/panicking.rs:92:14
2: core::panicking::panic
at /build/rust/src/rustc-1.49.0-src/library/core/src/panicking.rs:50:5
3: eureka::git::Git::get_callbacks::{{closure}}
4: git2::remote_callbacks::credentials_cb::{{closure}}
5: git2::panic::wrap
6: git2::remote_callbacks::credentials_cb
7: handle_auth
8: handle_response.constprop.0
9: http_stream_read
10: git_smart__recv_cb
11: git_smart__store_refs
12: git_smart__connect
13: git_remote_connect
14: git2::remote::Remote::connect_auth
15: eureka::git::Git::push
16: eureka::Eureka<FH,W,R>::run
17: eureka::main
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
thread 'main' panicked at 'Box<Any>', /home/barbarossa/.cargo/registry/src/github.com-1ecc6299db9ec823/git2-0.13.17/src/panic.rs:27:9
stack backtrace:
0: std::panicking::begin_panic
1: git2::remote::Remote::connect_auth
2: eureka::git::Git::push
3: eureka::Eureka<FH,W,R>::run
4: eureka::main
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
The repo is private, and I believe I have my credentials stored; so in theory, eureka should be pushing commits no problem. I think I might be missing something anyway, do you have any ideas?
About this issue
- Original URL
- State: open
- Created 3 years ago
- Comments: 24 (10 by maintainers)
Commits related to this issue
- Fix failure when a reference already exists When creating the target branch, if it already exists git2 will return an error with class reference and code exists. We should only return if the error is... — committed to Javier-varez/eureka by Javier-varez 3 years ago
- Hopefully fix git auth issue Hopefully fixes #81. I'm not sure what the problem is, and I'm unable to reproduce it, but this seems to be the recommended way to resolve credentials. — committed to simeg/eureka by simeg 3 years ago
So I had the same problem as above. I followed your suggestion of clone and using
fix-git-auth. It did not work. I get this other error message:Hello, I was having the same problem listed above,
I am using HTTPS for the remote instead of SSH.
I was finally able to fix it by deleting my old git credentials and replacing them with a fresh PAT.
I followed this tutorial to do that. https://www.nih-cfde.org/resource/setting-up-github-authentication/
@simeg Hi. Regarding this, is it possible to just create an option (might be on flags and on config file) to make eureka not push to origin repo? The idea is to let people push it themself to avoid this issue.
@simeg Thanks for your help! Seems related to my configuration… anyway, appreciate the help, I’m sure this thread would help others.
‘failed to acquire username/password from local configuration’, src/bin/eureka.rs:82:19