Re: Crowdsourced triage Scapegoat compiler plugin warnings

2017-07-13 Thread Sean Owen
Possibly, but it will take some degree of sophistication and understanding of Spark to evaluate these. I'd want committers or at least Spark developers to look at this rather than users. On Thu, Jul 13, 2017, 15:00 Jorge Sánchez wrote: > It might be worth sharing this with the user list, there m

Re: Crowdsourced triage Scapegoat compiler plugin warnings

2017-07-13 Thread Jorge Sánchez
It might be worth sharing this with the user list, there must be people willing to collaborate who are not on the dev list. 2017-07-13 10:00 GMT+01:00 Sean Owen : > I don't think everything needs to be triaged. There are a ton of useful > changes that have been identified. I think you could just

Re: Crowdsourced triage Scapegoat compiler plugin warnings

2017-07-13 Thread Sean Owen
I don't think everything needs to be triaged. There are a ton of useful changes that have been identified. I think you could just pick some warning types where they've all been triaged and go fix them. On Thu, Jul 13, 2017 at 9:16 AM Hyukjin Kwon wrote: > Hi all, > > > Another gentle ping for he

Re: Crowdsourced triage Scapegoat compiler plugin warnings

2017-07-13 Thread Holden Karau
I'm happy to help out in the places I'm more familiar with some starting next week. I suspect things probably just fell to the wayside for some folks during the 2.2.0 release. On Thu, Jul 13, 2017 at 1:16 AM, Hyukjin Kwon wrote: > Hi all, > > > Another gentle ping for help. > > Probably, let me

Re: Crowdsourced triage Scapegoat compiler plugin warnings

2017-07-13 Thread Hyukjin Kwon
Hi all, Another gentle ping for help. Probably, let me open up a JIRA and proceed this after a couple of weeks if no one is going to do this although I hope someone takes this. Thanks. 2017-06-18 2:16 GMT+09:00 Sean Owen : > Looks like a whole lot of the results have been analyzed. I suspect

Re: Crowdsourced triage Scapegoat compiler plugin warnings

2017-06-17 Thread Sean Owen
Looks like a whole lot of the results have been analyzed. I suspect there's more than enough to act on already. I think we should wait until after 2.2 is done. Anybody prefer how to proceed here -- just open a JIRA to take care of a batch of related types of issues and go for it? On Sat, Jun 17, 2

Re: Crowdsourced triage Scapegoat compiler plugin warnings

2017-06-17 Thread Hyukjin Kwon
Gentle ping to dev for help. I hope this effort is not abandoned. On 25 May 2017 9:41 am, "Josh Rosen" wrote: I'm interested in using the Scapegoat Scala compiler plugin to find potential bugs and performance problems in Spark. Scapegoat has a useful built

Crowdsourced triage Scapegoat compiler plugin warnings

2017-05-24 Thread Josh Rosen
I'm interested in using the Scapegoat Scala compiler plugin to find potential bugs and performance problems in Spark. Scapegoat has a useful built-in set of inspections and is pretty easy to extend with custom ones. For example, I added an inspection to spot