Skip to content
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

QA Report #1033

Closed
c4-bot-6 opened this issue Dec 28, 2023 · 5 comments
Closed

QA Report #1033

c4-bot-6 opened this issue Dec 28, 2023 · 5 comments
Labels
bug Something isn't working grade-c QA (Quality Assurance) Assets are not at risk. State handling, function incorrect as to spec, issues with clarity, syntax sufficient quality report This report is of sufficient quality unsatisfactory does not satisfy C4 submission criteria; not eligible for awards

Comments

@c4-bot-6
Copy link
Contributor

See the markdown file with the details of this report here.

@c4-bot-6 c4-bot-6 added bug Something isn't working QA (Quality Assurance) Assets are not at risk. State handling, function incorrect as to spec, issues with clarity, syntax labels Dec 28, 2023
c4-bot-1 added a commit that referenced this issue Dec 28, 2023
c4-bot-10 added a commit that referenced this issue Dec 28, 2023
@c4-pre-sort
Copy link

0xSorryNotSorry marked the issue as sufficient quality report

@c4-pre-sort c4-pre-sort added the sufficient quality report This report is of sufficient quality label Jan 5, 2024
@Trumpero
Copy link

Trumpero commented Jan 30, 2024

[L-01]: bot report duplication (N-52) -> invalid
[L-02]: bot report duplication (D-47) -> invalid
[N-01]: NC
[N-02]: gas purpose - OOS
[N-03]: missing instances of bot reports-> NC
[N-04]: code style -> NC
[N-05]: code style -> NC
[N-06]: typo -> NC
[N-07]: code style -> NC
[N-08]: the returned params are already explain in comments -> invalid

@c4-judge c4-judge added grade-c unsatisfactory does not satisfy C4 submission criteria; not eligible for awards labels Jan 31, 2024
@c4-judge
Copy link
Contributor

Trumpero marked the issue as grade-c

@thenua3bhai
Copy link

thenua3bhai commented Feb 1, 2024

Hi @Trumpero Thanks for judging and listing all the insights about each finding it is really helpful as feedback.
I just want to say that in this QA report about
[L-01] and [L-02] findings name can be similar to bot but here in my report it covered different instances which were missed by bot and analyzer . I have also written a Note : Missed by bot report below each finding which was covered in bot but some instances missed in bot report so I only reported those instances. Since it will add value to the protocol and also fixing bot instances won't fix missed ones. So Please re-consider them if you find this appropriate
And [N-08] I reported this since function using both named return variables and also explicitly returning variables also so this can be confusing in reading that function whose value will be returned finally. So I reported that also.
Thanks

@Trumpero
Copy link

Trumpero commented Feb 5, 2024

@thenua3bhai
As per C4's judge guideline, trivial instances of bot reports shouldn't be considered separately unless they are complex cases
Additionally, this report has insufficient points to be a grade-b, even when L-01, L-02 and N-08 are accepted

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working grade-c QA (Quality Assurance) Assets are not at risk. State handling, function incorrect as to spec, issues with clarity, syntax sufficient quality report This report is of sufficient quality unsatisfactory does not satisfy C4 submission criteria; not eligible for awards
Projects
None yet
Development

No branches or pull requests

5 participants