Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 369920 - NPE after opening a change in Task Editor
Summary: NPE after opening a change in Task Editor
Status: RESOLVED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Mylyn (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 1.0   Edit
Assignee: Steffen Pingel CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 367588 (view as bug list)
Depends on:
Blocks: 374729
  Show dependency tree
 
Reported: 2012-01-27 08:01 EST by Tomasz Zarna CLA
Modified: 2012-05-23 06:37 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tomasz Zarna CLA 2012-01-27 08:01:57 EST
Mylyn Reviews Connector: Gerrit (Incubation)	0.9.0.I20120125-1403	 org.eclipse.mylyn.gerrit.feature.feature.group	Eclipse Mylyn

What steps will reproduce the problem?
1. Open bug 361548 in Task Editor
2. Go to commit 2 and open I08e1369e in Task Editor
3. Refresh the change (not sure if this is required)

-- Error Details --
Date: Fri Jan 27 13:57:32 CET 2012
Message: An internal error occurred during: "Caching Patch Set Content".
Severity: Error
Product: Eclipse SDK 3.8.0.v201201251800 (org.eclipse.sdk.ide)
Plugin: org.eclipse.core.jobs
Session Data:
eclipse.buildId=I20120125-1800
java.fullversion=JRE 1.6.0 IBM J9 2.4 Windows XP x86-32 jvmwi3260sr7-20091214_49398 (JIT enabled, AOT enabled)
J9VM - 20091214_049398
JIT  - r9_20091123_13891
GC   - 20091111_AA
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=pl_PL
Command-line arguments:  -os win32 -ws win32 -arch x86

Exception Stack Trace:
java.lang.NullPointerException
	at java.util.LinkedHashMap.get(LinkedHashMap.java:324)
	at com.google.gson.LruCache.getElement(LruCache.java:50)
	at com.google.gson.FieldAttributes.getAnnotations(FieldAttributes.java:155)
	at com.google.gson.FieldAttributes.getAnnotation(FieldAttributes.java:145)
	at com.google.gson.SerializedNameAnnotationInterceptingNamingPolicy.translateName(SerializedNameAnnotationInterceptingNamingPolicy.java:44)
	at com.google.gson.JsonObjectDeserializationVisitor.getFieldName(JsonObjectDeserializationVisitor.java:92)
	at com.google.gson.JsonObjectDeserializationVisitor.visitFieldUsingCustomHandler(JsonObjectDeserializationVisitor.java:98)
	at com.google.gson.ObjectNavigator.navigateClassFields(ObjectNavigator.java:158)
	at com.google.gson.ObjectNavigator.accept(ObjectNavigator.java:131)
	at com.google.gson.JsonDeserializationContextDefault.fromJsonObject(JsonDeserializationContextDefault.java:73)
	at com.google.gson.JsonDeserializationContextDefault.deserialize(JsonDeserializationContextDefault.java:51)
	at com.google.gson.Gson.fromJson(Gson.java:568)
	at org.eclipse.mylyn.internal.gerrit.core.client.JSonSupport.parseResponse(JSonSupport.java:205)
	at org.eclipse.mylyn.internal.gerrit.core.client.GerritService.invoke(GerritService.java:106)
	at $Proxy10.patchScript(Unknown Source)
	at org.eclipse.mylyn.internal.gerrit.core.client.GerritClient$7.execute(GerritClient.java:375)
	at org.eclipse.mylyn.internal.gerrit.core.client.GerritClient.execute(GerritClient.java:783)
	at org.eclipse.mylyn.internal.gerrit.core.client.GerritClient.getPatchScript(GerritClient.java:372)
	at org.eclipse.mylyn.internal.gerrit.core.client.GerritClient.getPatchSetContent(GerritClient.java:300)
	at org.eclipse.mylyn.internal.gerrit.ui.editor.GetPatchSetContentJob.run(GetPatchSetContentJob.java:54)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
Comment 1 Steffen Pingel CLA 2012-03-08 13:36:22 EST
Looks like it's this bug: http://code.google.com/p/google-gson/issues/detail?id=288. I have also seen this happen after we setup tests on ppc64 with a J9 JVM. 

We'll need to consume a newer release of GSon to fix this. It looks like GSon 2.1 has been approved already: https://dev.eclipse.org/ipzilla/show_bug.cgi?id=5923.
Comment 2 Steffen Pingel CLA 2012-03-22 09:19:31 EDT
*** Bug 367588 has been marked as a duplicate of this bug. ***
Comment 3 Steffen Pingel CLA 2012-05-23 06:37:56 EDT
We are now using GSon 2.1 which should have a fix for the described exception.