NPE in AssignmentEntityProvider (attachments) when browse server clicked
GENERAL
TESTING
GENERAL
TESTING
Description
We had a report of a NPE in AssignmentEntityProvider. This was triggered in the browse server and the trace was.
Caused by: java.lang.NullPointerException at org.sakaiproject.assignment.entityproviders.AssignmentEntityProvider$SimpleAssignment.<init>(AssignmentEntityProvider.java:247) at org.sakaiproject.assignment.entityproviders.AssignmentEntityProvider.getAssignmentsForSite(AssignmentEntityProvider.java:672) ... 35 more
This looks like code involved in getting the name of an attachment, and is likely for some type of broken attachments. The vm's check that the properties are valid before displaying them, so the entity provider should also do that. I'm going to add in some debugging code (which maybe should be info) to help track down these problem attachments as I'm not sure where they're coming from and it's not super easy in a course with a ton of assignments.
We had a report of a NPE in AssignmentEntityProvider. This was triggered in the browse server and the trace was.
Caused by: java.lang.NullPointerException
at org.sakaiproject.assignment.entityproviders.AssignmentEntityProvider$SimpleAssignment.<init>(AssignmentEntityProvider.java:247)
at org.sakaiproject.assignment.entityproviders.AssignmentEntityProvider.getAssignmentsForSite(AssignmentEntityProvider.java:672)
... 35 more
This looks like code involved in getting the name of an attachment, and is likely for some type of broken attachments. The vm's check that the properties are valid before displaying them, so the entity provider should also do that. I'm going to add in some debugging code (which maybe should be info) to help track down these problem attachments as I'm not sure where they're coming from and it's not super easy in a course with a ton of assignments.