-
Notifications
You must be signed in to change notification settings - Fork 82
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
(#120) TCC: advancing implementation #182
Conversation
… a 3rd method of the class.
Job #182 is now in scope, role is |
@amihaiemil weird... let me check the test failure in the build |
… a 3rd method of the class
@amihaiemil please review |
Codecov Report
@@ Coverage Diff @@
## master #182 +/- ##
=========================================
Coverage 73.93% 73.93%
Complexity 159 159
=========================================
Files 31 31
Lines 1013 1013
Branches 71 71
=========================================
Hits 749 749
Misses 232 232
Partials 32 32 Continue to review full report at Codecov.
|
@amihaiemil I'm actually a bit confused by this puzzle. It said that we needed to take into account when two methods are related because they both call a third one. So I implemented that. But through a cursory look at the PDF
So it seems like TCC was already implemented? WDYT? |
@amihaiemil I've read the paper and produced some notes. I'll be making some changes and let you know. Thank you for your patience |
Revised after these notes were taken: cqfn#120 (comment)
@amihaiemil please review |
Sorry, but I can't help you with details related to the metric itself. I don't know them. Here, I am paying more attention to the style, size, Java code in the PR etc and the puzzles. Basically, since these are sandbox projects, the goal is for the new guys to learn how the model works. If there's a bug in a metric (which is highly expected, since nobody is an expert in theoretical software metrics here), it's not the end of the world. Plus, we have the ARCH, who is supposed to look at the things with more substance :) |
@llorllale From my point of view, it looks good. Maybe, after the new puzzle is created by 0pdd, go there and link the notes that you've made here |
@rultor merge |
@amihaiemil Thanks for your request. @yegor256 Please confirm this. |
@amihaiemil my confusion stemmed from blindly following through with the puzzle's instructions. After reading the PDF for myself I realized that the instructions did not apply to TCC. So I wasted quite a lot of time on this one :) |
@yegor256 please merge |
@rultor merge |
@ypshenychka/z please review this job, as in §30 |
@ypshenychka Can you give the verdict here? |
@amihaiemil Don't worry. I will review as soon as the issue https://github.com/zerocracy/farm/issues/592 is resolved. |
@amihaiemil/z this job was assigned to you 5 days ago. It will be taken away from you soon, unless you close it, see §8. Read this and this, please. |
@llorllale According to our QA Rules:
Please provide more informative title and description. |
@ypshenychka would the following suffice?
|
According to our QA Rules:
Please correct your message by indicating an addressee in the beginning. |
@llorllale Sure. Please go ahead and edit title\description. |
@ypshenychka fixed title, description, and that unaddressed message you pointed out |
@amihaiemil According to our QA Rules:
No issues were found during code review. Please confirm that you'll try to find at least three problems while future reviews. |
@llorllale Great. Thanks. |
@ypshenychka right, I'll try to find more bugs in future tasks. But since these are sandbox projects, I am paying more attention to the methodology :) |
@amihaiemil thank you |
@0crat quality acceptable |
QA review completed: +15 points just awarded to @ypshenychka/z, total is +240 |
Order was finished, quality was "acceptable": +15 points just awarded to @amihaiemil/z, total is +730 |
as per #120
See the
bieman95.pdf
paper for more details.