Weekly overview of the bug-hunting category- week 63, 2019

This is a report on the weekly contributions to the bug hunting category. The post contains basic stats like the number of contributions received by the category, an excerpt on new contributors if there are any and a detailed comparison of the week's output with previous weeks.

Previous Reports

2018

• Weekly overview of the bug-hunting category- week 44, 2018
• Weekly overview of the bug-hunting category- week 45, 2018
• Weekly overview of the bug-hunting category- week 46, 2018
• Weekly overview of the bug-hunting category- week 47, 2018
• Weekly overview of the bug-hunting category- week 48, 2018
• Weekly overview of the bug-hunting category- week 49, 2018
• Weekly overview of the bug-hunting category- week 50, 2018
• Weekly overview of the bug-hunting category- week 51, 2018
• Weekly overview of the bug-hunting category- week 52, 2018
• Weekly overview of the bug-hunting category- week 53, 2018

2019

• Weekly overview of the bug-hunting category- week 54, 2019
• Weekly overview of the bug-hunting category- week 55, 2019
• Weekly overview of the bug-hunting category- week 56, 2019
• Weekly overview of the bug-hunting category- week 57, 2019
• Weekly overview of the bug-hunting category- week 58, 2019
• Weekly overview of the bug-hunting category- week 60/61, 2019
• Weekly overview of the bug-hunting category- week 62, 2019

Bug hunting contributions summary

Week 63: March 7th - March 14th

• 7 Contributions, 3 scored higher than 0
• An average score of 62
• 6 unique contributors
• No Staff Pick
• 2 new contributors - @diana01, @autofreak

The contributions

Contributor	URL	Project	Reviewer	Score
@harry-heightz	repost-option-is-available-on-my-own-posts	1ramp	tobias-g	48
@blockchainstudio	no-detailed-user-profile-cover-image-rep-location-about-on-reward-pages	steemit/condenser	fego	75
@tony-duke	remove-draft-button-on-steeditor-not-functioning	steeditor	fego	0
@mightypanda	performance-observable-are-not-unsubscribed-leading-to-higher-cpu-use	swapsteem	fego	63
@autofreak	app-crashes-when-share-csv-is-clicked-on	piggybudget-v-2-2	fego	0
@tony-duke	the-theme-feature-not-functioning-properly-on-steemwallet	steemwallet	fego	0
@diana01	bug-again-on-steemit-wallet	steemwallet	tobias-g	0

In the last week, we had 7 contributions to the bug-hunting category at utopian-io. There were no staff picks. Only 3 of the 7 contributions were scored above 0.

The highest scored contributions were by @blockchainstudio and @mightypanda. Mightypanda's observations showed that - Swapsteem code uses RxJS to subscribe to changes in data. RxJS in-turn use Observable which are Infinite Subscriptions.

This means that the code will execute even without a subscribe being called unlike http.get where call will only be made when you subscribe to it. This causes a performance and memory hog as you exit and re-enter a controller because you are subscribing to same service multiple times.here
Click here to look through the report for further information.

Blockchainstudio's report stated that while using the default steemit frontend, the user profile information (cover image, rep, location, about...) is not shown on curation/author reward pages. Rep is shown as 25, default.

He would go on to detail the reason behind this and would propose a fix.

You can read the full report and get details of the proposed fix by checking the contribution's link : https://steemit.com/utopian-io/@blockchainstudio/steemit-condenser-no-detailed-user-profile-cover-image-rep-location-about-on-reward-pages

Weekly Average Score and number of Contributions

Chart breakdown:

• The average score for this week is 62
• This week's average is higher than the 4-week average of 53.06 by 8.94.
• It is higher than last week's average of 53.13 by 8.87, that is 14.31%% higher. Overall we can say that the quality of contributions increased this week by 14% or more.

Hunter Totals and Average

• This week we had 6 unique contributors, 4 less than last week
• There were 2 reports from @tony-duke. 1 each from the other 5.
• @horpey is still the category's top contributor with 20 finds. That is 20 finds since the start of the year, he's closely followed by @harry-heightz and blockchainstudio with 16
• @blockchainstudio has a 4 week average of 80.4, making him the contributor with the highest average score.
• 2 of the contributions were scored higher than the week's average

Reports Reviewed By Reviewer

The category has received 116 contributions this year, 2019. 100 were rewarded and scored higher than 0. However, in the past 4 weeks, there were 39 bug reports scored higher than 0. These 39 were assessed by 2 reviewers.

Average review scores in the past 4 weeks

• @fego has reviewed 27 contributions with an average score of 52.93.
• @tobias-g has reviewed 12 contributions with an average score of 53.38.

Common Mistakes And How To Fix Them

I will be highlighting the common mistakes found this week, and I will be offering tips on how to avoid them in future contributions. The tips will depend solely on the scores received by the contributions in a particular week.

1. Contributions scored 0

The issue you reported is OS related and is therefore not the application's fault. The operating system does not support this particular feature

• My advice for cases like this is - wait for the PO to affirm your observations. I know most times the project owners are too busy and do not respond in reasonable time and so you are pushed to post on utopian without them first acknowledging whether an observed behavior is a bug or an intended. It can be frustrating but I'd still advise that hunters in the future should wait for the PO's thoughts, especially in cases where the details behind the implementation in question are sketchy.

2. Contributions with a score below 60

The contributor made no efforts to pinpoint the cause, or applied incorrect methods in searching for it.

• To avoid being scored in the questionnaire with this option, I will advise hunters to comb through the app's repo. Search the repo using a keyword related to the affected feature, it could be the name of the function itself. If found, analyze the block of code behind the function's implementation. Check for syntax and logical errors, document your findings.

Other News

---

While the new guidelines are yet to be implemented, bug-hunters and open source enthusiasts looking to help open source projects, please take a look at our whitelist of projects that you can submit bug reports for:

https://docs.google.com/spreadsheets/d/1S7ayFTEy5CBMyeJvFRgq5JUjlqZxFjWAWhhrBL0GC60/edit#gid=1954068373

---

If you wish to have your open source projects added to our whitelist you can contact us on our help channel at our discord server. You can also leave your questions and comments below :)

---

Thanks

@fego