-
Notifications
You must be signed in to change notification settings - Fork 187
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
libpromises/evalfunction: Do not crash w/o arguments #5630
Conversation
51f4289
to
8979788
Compare
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.
Great, thanks 🚀 You can easily fix the CodeQL alerts by adding
assert(fp != NULL);
in the top of the function block. Let me know if you want me to fix this for you.
In the mean while we can ask @cf-bottom to test this in Jenkins
@cf-bottom jenkins, please |
Alright, I triggered a build: Jenkins: https://ci.cfengine.com/job/pr-pipeline/11443/ Packages: http://buildcache.cfengine.com/packages/testing-pr/jenkins-pr-pipeline-11443/ |
Do not crash cf-promises if no argument is given for following functions: * readfile * iprange * isipinsubnet
8979788
to
e040d7f
Compare
@btriller Thank you for your contribution, merging. Your fixes will probably not make it into the releases we're working on now (3.24.1 and 3.21.6), but will be a part of the next ones (3.25.0, 3.24.2, and 3.21.7). |
Ping |
Do not crash cf-promises if no argument is given for following functions: