Re: [cross-project-issues-dev] Facebook Open Academy for Fall 2015
OK everyone, here we go! Sign up for Fall 2015 on this form here: https://docs.google.com/forms/d/1zwiYbpB8dg6meA97J1gW32FkFZEGkEsyS1mlekd-eBY/viewform If you are going to apply, and haven't already, please let me know. I'll advocate for you to help your chances. Cheers! Andrew On 20/07/15 20:13, Andrew Ross wrote: Hey Everyone, (x-posted all over the place, feel free to forward to anyone who might be interested) Facebook Open Academy (FOA) is about to start up again for the fall. For those unfamiliar, here's a synopsis: FOA is a program that matches top students with open source projects. Students work roughly 8 to 10 hours per week to complete features, fix bugs, and generally participate in the project's community. Typically they do so working in groups of 4 or more. Mentors are expected to invest a few hours per week to mentor. The program also includes a face to face code sprint running for 3 days. We anticipate multiple code sprint locations this fall including ones in North America Europe. (Facebook generously reimburses mentors for travel costs) For what it's worth, I highly recommend the program. I will be following up soon with a link to the form to apply. If you are interested, please plan to complete the form, but also give me a heads up so I can advocate for you. Competition is fierce! Cheers! Andrew ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
[cross-project-issues-dev] Error reporter and third-party code
I've been watching the error reports trickling into the Sapphire inbox, but unfortunately none of them have been actionable so far. The issue is interaction with third-party code. Consider the following stack trace: java.lang.NullPointerException: HIDDEN at org.eclipse.jst.j2ee.model.ModelProviderManager.getModelProvider(ModelProvid erManager.java:101) at org.eclipse.jst.j2ee.model.ModelProviderManager.getModelProvider(ModelProvid erManager.java:281) at HIDDEN.HIDDEN(HIDDEN:-1) at HIDDEN.HIDDEN(HIDDEN:-1) at org.eclipse.sapphire.PossibleValuesService.initDataService(PossibleValuesSer vice.java:68) at org.eclipse.sapphire.services.DataService.init(DataService.java:54) at org.eclipse.sapphire.services.Service.initIfNecessary(Service.java:60) at org.eclipse.sapphire.services.ServiceContext.services(ServiceContext.java:21 7) at org.eclipse.sapphire.Property.services(Property.java:535) at org.eclipse.sapphire.Property.service(Property.java:505) at org.eclipse.sapphire.services.internal.PossibleValuesValidationService$Condi tion.applicable(PossibleValuesValidationService.java:82) at org.eclipse.sapphire.services.ServiceProxy.service(ServiceProxy.java:99) at org.eclipse.sapphire.services.ServiceContext.services(ServiceContext.java:17 6) There are three codebases interacting here: Sapphire, WTP and some unknown third-party plugin. Without knowing the hidden details in order to be able to initiate a discussion with the third-party, this error report is not actionable. This is not an isolated case or a minority of cases. Literally all reports received so far for Sapphire are like that. I know that there are other leaf projects with a similar issue. Now that we have a solution for capturing and hopefully handling errors that only involve eclipse.org code, let's have a serious discussion on how we can handle error reports involving third-party code. First question. Why are third-party stack frames hidden? Are the notes from when this was originally considered captured somewhere? I have contact info for many Sapphire adopters. If I knew who to contact, I could actually follow up on these error reports. Thanks, - Konstantin ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
