Classify multiple bugs at a time in the code to find bug-fixing commits

[marco-c]

We are classifying one bug at a time in

bugbug/scripts/regressor_finder.py

Line 264 in 2222232

if defect_model.classify(bug)[0] == "defect":

, we could instead collect the bugs in a list and then classify them in one go.

The script can be easily tested by running python -m scripts.regressor_finder bug_fixing.

[Rishabhc711]

Hi! I read about the issue and I have seen the code. So all you are doing here is classifying the different bugs from the list that have fixed some commits. Classifying them in one go would require us to sort them first. What more insights can you provide me on this?

[marco-c]

Hello! We don't need to sort them, we can classify them in any order.
You have an example classification of multiple items (commits in this case, but you can apply the same to bugs) here:

bugbug/scripts/generate_landings_risk_report.py

Line 277 in 4bd7312

probs = self.regressor_model.classify(commit_list, probabilities=True)

.

[Abhishek5002443]

Hey this is my first time on Github and I am looking for my first contribution. Can you please tell me, what will I need to do exactly in this request?

[marco-c]

Hello @Abhishek5002443, the description of what needs to be done is above. First of all follow #1092. Then, once everything is set-up, follow the pointers I gave above, try to understand that code, and then try to implement what was requested above. If you get stuck, feel free to ask questions.

[willT97]

Hi I had a go fixing this issue, making the defect model classify in one go. Should the regression model also classify bugs at the same time?

[marco-c]

Hi I had a go fixing this issue, making the defect model classify in one go. Should the regression model also classify bugs at the same time?

If possible yes, can you file a new issue for that?

[willT97]

If possible yes, can you file a new issue for that?

Ok will do, created the new issue #2007 .

[5aumy4]

Hello everyone!, I have a little past experience with open source contribution. Can I work on this bug?

[marco-c]

@5aumy4 please read the introduction first; there is already a PR open to fix this issue, so you'd need to choose another issue to work on.