-
Notifications
You must be signed in to change notification settings - Fork 338
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
456-fix-error-codes #475
base: latest
Are you sure you want to change the base?
456-fix-error-codes #475
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's unclear to me why you've chosen to implement a file-specific error code instead of using the error code functionality already present in the library.
Please rework this change to use the library's existing error code functions (defined in src/error.c
and used extensively throughout the project).
hello, I change my pull request according to your comment. Is it ok? |
Please remove the |
8085731
to
ef3e531
Compare
Hello, |
You'll need to get the tests passing, of course. From the one that I looked at you'll probably need to do a few rounds of tweaks and rebuilds. |
Sorry, this is my first time working with tests. I edit them and all tests passed. Is it ok this way? |
I'm sorry for inconvenience, in the previous edit here on github, not all the edits I have made have been changed. Can you please run the control again? I edited it now. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## latest #475 +/- ##
==========================================
- Coverage 90.40% 90.07% -0.34%
==========================================
Files 47 47
Lines 4388 4421 +33
Branches 588 595 +7
==========================================
+ Hits 3967 3982 +15
- Misses 286 295 +9
- Partials 135 144 +9 ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please see the first round of requested changes below, in addition to correcting the header check in the static analysis run that failed.
Requested changes have been done. |
I dont understant it. I set expect true but in errors is that it expect false. How it is possible? |
No, it's assigned so that you know who is reviewing it and responsible for giving you feedback when needed. I haven't run the tests myself - are they passing when you run them locally? Have you tried adding some print statements or running the test using a debugger (e.g. |
add errors to facility functions #456
Error handling code was created for the following functions: