No such file or directory error thrown when pushing a .c extension file with a 'newline at the end'.

[Shashankss1205]

Description

I am not sure if this is a linting error or a different error or my lack of understanding but Please guide me out of this problem.
Encountered an error when adding a newline at the end of c files and pushing it to the Repository, while contributing to some feature changes.

Please take a look at this and help me sort this out.
Thank You!!

Related Issues

None

Questions

No.

Demo

No response

Reproduction

- Select any function say math/base/special
- Change the .c files to contain a newline at the end.
- Push the commit to the repo

Expected Results

No errors are to be expected.

Actual Results

Error is thrown, shown in the screenshot

Version

current version

Environments

Node.js

Browser Version

No response

Node.js / npm Version

No response

Platform

No response

Checklist

• Read and understood the Code of Conduct.
• Searched for existing issues and pull requests.

[Pratik772846]

I was facing this similar error with math/base/special/min package, but after this commit, it was fixed. A similar kind of change is also needed in the math/base/special/max package also.

[Pratik772846]

@kgryte PRs whose all tests have not been passed have been merged. I think we are getting these errors due to this reason.

[Shashankss1205]

I was facing this similar error with math/base/special/min package, but after this commit, it was fixed. A similar kind of change is also needed in the math/base/special/max package also.

Mine all tests passed as soon as I removed the extra newlines so I took that way out of this problem.

[Pranavchiku]

Everything works well for me, @Shashankss1205 you will have to add #include <stdlib.h> header in example.c created by you.

[Shashankss1205]

Everything works well for me, @Shashankss1205 you will have to add #include <stdlib.h> header in example.c created by you.

Okay thanks, I will add the header file and check the code once.

[Shashankss1205]

Hello @Pranavchiku , can you please guide me onto how can I remove the error:

I got inactive because I couldn't figure out how to remove this error as it peeked in each and every time.
Please help so that I can again start contributing.

[kgryte]

@Shashankss1205 Can you provide a reproducible example? Showing screenshots is not enough to help us debug. We need to be able to actually see the code you are trying to push. If you need to bypass Git hooks, append --no-verify when attempting git push.

[Shashankss1205]

@kgryte thank you for your response, I have finally debugged this problem and it wasn't actually a problem of the package but mine personal execution problem.

Thank you for your valuable feedback.

[kgryte]

@Shashankss1205 Thanks for the update. I'll go ahead and close this then.