Weekly overview of the bug-hunting category- week 55, 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.
- 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
- Weekly overview of the bug-hunting category- week 54, 2018
Bug hunting contributions summary
- Week 55: January 10th - January 17th
- 20 Contributions, 19 scored higher than 0
- An average score of 50.39
- 10 unique contributors
- 1 Staff Pick
This week we had 20 contributions, more than we've had in the previous 3 weeks. Majority of the reports were submitted to the project repository of eSteem mobile V2.
19 out of the 20 reports were scored higher than 0.
Also, we had a staff pick from @blockchainstudio, that's 2 picks in 2 weeks for the super bug detector :) This time he found that building steem on Mac OS does not work, instead it returned the error -
Could NOT find zlib (missing: ZLIB_LIBRARIES).
Most MacOS version has dynamic library of
zlibby default, as you can see from
/usr/lib/libz.dylib(you can't even write in
/usr/libunless disabling SIP, which is not recommended), but no static library. But the build script keeps trying to find static library, libz.a in the same directory, even if you give export
He made a pull request that rectified this error. You can read the full report here - https://steemit.com/utopian-io/@blockchainstudio/missing-zlib-libraries-macos-steem-build.
Apart from the staff pick, there were also notable contributions from @tobias-g and @horpey. Tobias observed that the site https://knacksteem.org is not usable via http://. The site does not automatically redirect a user, it will instead cause cross-origin errors and the categories will not be loaded.
Horpey made 7 contributions to the eSteem application. In total, the project received 14 bug reports.
Weekly Average Score and number of Contributions
- The average score this week is 50.39.
- The average score is approximately 5% lower than the 2 week average of 53.04.
- This week's average is lower than the last 2 weeks average by 0.61.
- It is lower than last week's average of 61.42 by 11.03.
- 7 contributions were scored higher than the week's average.
Hunter Totals and Average
- This week we had 10 unique contributors.
- There were 11 reports from the top contributors. 7 contributions from @horpey and 4 from @blockchainstudio
- As it stands, @horpey is the category's top contributor with 9 finds. That is 9 finds since the start of the new year, he's closely followed by @blockchainstudio with 7.
Reports Reviewed By Reviewer
The category has received 26 contributions since the start of the year. The contributions received by the category in the past 2 weeks were assessed by 3 reviewers. 25 were rewarded and scored higher than 0.
- @fego has reviewed 17 contributions with an average score of 54.15.
- @tobias-g has reviewed 8 contributions with an average score of 51.5.
- @crokkon has reviewed 1 contribution, with an average score of 45.
Common Mistakes And How To Fix Them
Following the suggestions made by @tykee, I thought I'd borrow a leaf from the works of @favcau and @didic :). So in this section, I will be highlighting the common mistakes found this week, and I will be offering tips on how to avoid them in future contributions.
1. Contributions with scores below 25
Both the title and content of the submission post were lacking in information and the steps to bug reproduction were badly explained and, at times, impossible to follow.
The post title ought to include the app name and version number, as well as a brief description of the occurring issue. In other words, the title should be well detailed enough to provide an insight as to what the bug is about.
The steps should be clear and easy to follow. It is advised to have the steps arranged in an ordered list, that way it is easier for the PO to follow and reproduce the error step by step. Also, the video should only add value to the report and not totally replace the written steps or essential details of the bug.
2. Contributions scored 0
This particular feature has not been implemented yet, and because of this, this particular issue cannot be considered a bug within the application
A bug is a manifestation of an error in the functionality of a system and is a deviation from the expected behavior, usually traced back to a coding mistake. An unimplemented feature, on the other hand, has no expected behavior or user story. This is simply because the function is not defined, hence there is no clear idea of how the feature should behave.
- One way to avoid mistaking an unimplemented feature for a bug is to wait for the PO to acknowledge the issue as a bug since he's responsible for defining the functionalities.
- Another option is to go through the github repo to confirm that there is a code implementation of the expected behavior. If there is no code to support the particular action then it is yet to be implemented and is not a bug.
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:
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 :)