Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 311317 - Unhandled event loop exception / NPE at revalidateImpl pushing to RO urls
Summary: Unhandled event loop exception / NPE at revalidateImpl pushing to RO urls
Status: CLOSED DUPLICATE of bug 304182
Alias: None
Product: EGit
Classification: Technology
Component: UI (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows Vista
: P3 minor (vote)
Target Milestone: 0.8.0   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-02 12:49 EDT by Chris West (Faux) CLA
Modified: 2010-05-02 13:01 EDT (History)
0 users

See Also:

Attachments
Example error log generated (3.62 KB, text/plain)
2010-05-02 12:50 EDT, Chris West (Faux) CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Chris West (Faux) CLA 2010-05-02 12:49:50 EDT 
Build Identifier: I20100413-1521

EGit 0.7.1.

Team -> Push to..'s second page (Push Ref Specifications) causes an Unhandled event loop exception to be logged if the remote URL is read-only.

org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.NullPointerException)
[...]
Caused by: java.lang.NullPointerException
..org.eclipse.egit.ui.internal.components.RefSpecPage.revalidateImpl(RefSpecPage.java:259)
..org.eclipse.egit.ui.internal.components.RefSpecPage.access$2(RefSpecPage.java:228)
[...]

Full stack attached.

Nothing seems immediately wrong with the UI, although the push will eventually fail (obviously).  Actual URL tested: git://git.goeswhere.com/git/dollar.git

Reproducible: Always

Steps to Reproduce:
1. Clone a project from a read-only location, e.g.
> git remote -v
origin  git://git.foo.com/git/bar.git (fetch)
origin  git://git.foo.com/git/bar.git (push)
2. Team -> Push to..
3. Ensure "origin: git://git.foo.com/git/bar.git" is selected as the target.
4. Next.
5. Observe the error log.
Comment 1 Chris West (Faux) CLA 2010-05-02 12:50:39 EDT 
Created attachment 166735 [details]
Example error log generated
Comment 2 Chris West (Faux) CLA 2010-05-02 13:01:33 EDT 
Like bug 311315, also fixed as of 0.8.0.201004301514.

*** This bug has been marked as a duplicate of bug 304182 ***