-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
System.NullReferenceException when trying to push #3862
Comments
Please raise all issues you have. If we don't know them - we can't fix them. |
@RussKie They're hard to explain but i will definitely. But for now, this bug has higher priority for me. Any ideas? |
As an immediate work around - please try installing 2.49.x version and see if it works for you. |
Can you successfully perform other operations - e.g. pull, fetch, checkout? |
@RussKie previous versions work well. And as far as i tested, Yes, other operations work and the problem seems to be only related to push dialog window. Here's a screenshot but i'm not sure if it helps: |
The details under the exception tab would be more helpful.
…On Wed, Jul 19, 2017 at 9:31 AM Ali Mirlou ***@***.***> wrote:
@RussKie <https://github.com/russkie> previous versions work well. And as
far as i tested, Yes, other operations work and the problem seems to be
only related to push dialog window. Here's a screenshot but i'm not sure if
it helps:
[image: 1]
<https://user-images.githubusercontent.com/19661419/28369194-23fa6304-6cac-11e7-8a1c-2172bdf771a6.png>
I'm not really familiar with the debugging tools to provide you with more
info, is there a document for it?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#3862 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ADdhsR-7EfR-H5XFhjcFmWzelLXydoVcks5sPgUtgaJpZM4OcjU5>
.
|
@vbjay Unfortunately, this is where one of the graphical bugs are: |
Lol. Nice.
…On Wed, Jul 19, 2017, 3:29 PM Ali Mirlou ***@***.***> wrote:
@vbjay <https://github.com/vbjay> Unfortunately, this is where one of the
graphical bugs are:
[image: 1]
<https://user-images.githubusercontent.com/19661419/28385675-3acf1e94-6cde-11e7-899d-0f7c4229dea5.png>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#3862 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ADdhsWRf3uQxV3YRVVoMKy0LOLM-poYyks5sPlkcgaJpZM4OcjU5>
.
|
do you have at least one remote? just fixed a NPE in this function few days ago. |
@EbenZhang Yes, I have remotes. When will this fix be added to the builds? |
Same problem, happened when I init'ed a new fresh repo, staged and commited files, click Push button then NPE error. Version: 2.50.01 |
Upgrade git.
…On Tue, Jul 25, 2017, 7:55 PM Doğan Çelik ***@***.***> wrote:
Same problem, happened when I init'ed a new fresh repo, staged and
commited files, click Push button then NPE error. Version: 2.50.01
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#3862 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ADdhsdAnw387KCkVBygt07Ao1Rh8HXHVks5sRoCOgaJpZM4OcjU5>
.
|
@dogancelik have you set at least one remote before pushing? |
I was in a hurry so I didn't explain it well. Before 2.50
After 2.50
You don't even need Step 3. The error occurs because there is no remote. |
Awesome, thanks for the explanation and screenshots.
I'll try to replicate this
…On 26/07/2017 11:51 AM, "Doğan Çelik" ***@***.***> wrote:
I was in a hurry so I didn't explain it well.
This error occurs in *2.50.00* and *2.50.01*:
Before 2.50
1. I open an empty folder with GitExtensions browse folder-path
2. I click "Initialize repository"
3. I stage a single text file and commit with "Initial"
4. I click "Push", dialog opens
[image: 24903]
<https://user-images.githubusercontent.com/486818/28600915-d2564434-71bd-11e7-8533-b459ee4673b2.png>
After 2.50
1. I open an empty folder with GitExtensions browse folder-path
2. I click "Initialize repository"
3. I stage a single text file and commit with "Initial"
4. I click "Push", *exception error*
[image: 25001]
<https://user-images.githubusercontent.com/486818/28600916-d25b07bc-71bd-11e7-994c-b18c17a78586.png>
You don't even need Step 3.
In *2.49.03*, it works whether you commit a file or not.
The error occurs because there is no remote.
I didn't find the need to explain the issue as issue author already
explained it.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#3862 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AEMyXnk5Q7c46P_WMDu_TZMCJ_MFFb42ks5sRpuEgaJpZM4OcjU5>
.
|
This issue was fixed by @EbenZhang in 11d2763 |
I have the same problem... http://take.ms/yq7Eg |
@maxima Read Russkie's comment.
…On Tue, Aug 1, 2017 at 10:07 AM maxima ***@***.***> wrote:
I have the same problem... http://take.ms/yq7Eg
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#3862 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ADdhsRRXOqaCTgAlNn_tb9Q_VZdW_Vw9ks5sTzExgaJpZM4OcjU5>
.
|
I'm closing this. |
I cloned the current branch and the issue is still there for me. |
The master branch, the push menu opens but when I actually try to push to a remote server it crashes. |
An attempt to push when no remote defined would result in NRE. Check for remotes before pushing. If no remotes available, show an error message and a prompt to configure remotes. Fixes gitextensions#3862.
An attempt to push when no remote defined would result in NRE. Check for remotes before pushing. If no remotes available, show an error message and a prompt to configure remotes. Fixes gitextensions#3862.
An attempt to push when no remote defined would result in NRE. Check for remotes before pushing. If no remotes available, show an error message and a prompt to configure remotes. Fixes gitextensions#3862.
I'm running into a similar problem, too. It was proceeded by Git Extensions becoming completely unresponsive, and the only way I could get it shut down was a reboot. Task manager -> End task or even command line (as admin) taskkill /F didn't do a thing. After the reboot I get NullReferences whenever I try to pull from or push to origin. Below is the resulting error message. I can get the pull and push to go through by manually inputing my username and password, but the problem persists between pushes and pulls.
|
Nevermind, it seems the problem is with Git itself, and not with Git Extensions. The same problem arises when using Git from the command line. Thought the original problem of GE freezing up was definitely a problem with GE. :) |
Happens when trying to push, no matter how (Choosing push from Commands or toolbar, using push hotkey (ctrl+up), "Commit and Push" in commit window). Giving me "System.NullReferenceException: Object reference not set to an instance of an object." on "Void UpdateRemoteBranchDropDown() @ GitUI.CommandsDialogs.FormPush" by opening a crash report window.
The problem started after installing GitExtensions 2.50.01 (Git 2.10.0, Windows 10 version 1703 build 15063.483).
Redownloaded and reinstalled but no luck.
There are many graphical bugs too, some related to being incompatible with 4k resolution, which i don't know if i have to open issues for them or not.
The text was updated successfully, but these errors were encountered: