-
Notifications
You must be signed in to change notification settings - Fork 189
ENT-10184: Top down evaluation #5834
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
Conversation
51e4721
to
c255477
Compare
eccfbbf
to
29b776d
Compare
a66b123
to
5038b0c
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.
CodeQL found more than 20 potential problems in the proposed changes. Check the Files changed tab for more details.
a76ce54
to
1f0e9b7
Compare
1f0e9b7
to
b1b9bad
Compare
599311a
to
797bed8
Compare
@@ -1452,6 +1454,7 @@ | |||
} | |||
|
|||
SeqAppend(section->promises, pp); | |||
SeqAppend(section->parent_bundle->all_promises, pp); |
Check notice
Code scanning / CodeQL
Pointer argument is dereferenced without checking for NULL Note
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.
Looks good so far, please add some examples and tests so we can discuss and experiment with how it works :)
fd5b98b
to
cd37f33
Compare
cd37f33
to
1dcceca
Compare
@cf-bottom jenkins, please :) |
Alright, I triggered a build: Jenkins: https://ci.cfengine.com/job/pr-pipeline/12355/ Packages: http://buildcache.cfengine.com/packages/testing-pr/jenkins-pr-pipeline-12355/ |
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.
This is very cool @victormlg 🚀 Only some nitpicks, looking forward to try this!
tests/acceptance/15_control/01_common/top_down_evaluation_custom_promise_types.cf
Outdated
Show resolved
Hide resolved
tests/acceptance/15_control/01_common/top_down_evaluation_complex_policy.cf
Show resolved
Hide resolved
tests/acceptance/15_control/01_common/top_down_evaluation_long_policy.cf
Outdated
Show resolved
Hide resolved
1dcceca
to
7ec8ce5
Compare
@cf-bottom jenkins, please :) |
Alright, I triggered a build: Jenkins: https://ci.cfengine.com/job/pr-pipeline/12430/ Packages: http://buildcache.cfengine.com/packages/testing-pr/jenkins-pr-pipeline-12430/ |
@cf-bottom Jenkins please :) |
Alright, I triggered a build: Jenkins: https://ci.cfengine.com/job/pr-pipeline/12477/ Packages: http://buildcache.cfengine.com/packages/testing-pr/jenkins-pr-pipeline-12477/ |
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.
Can you move the custom promise types related tests to masterfiles/tests/acceptance/30_custom_promise_types ? Here we already have a copy of cfengine.py.
I don't see any copy of cfengine.py in masterfiles/tests/acceptance/30_custom_promise_types. I think it makes sense to keep the top_down evaluation tests together |
Ticket: ENT-10184 Signed-off-by: Victor Moene <[email protected]>
Signed-off-by: Victor Moene <[email protected]>
Signed-off-by: Victor Moene <[email protected]>
7ec8ce5
to
57a972a
Compare
It is in masterfiles/modules/promises/cfengine.py. I think it makes sense to put it in with the other custom promise types. If we release a new version of cfengine.py, we don't want to have to update it in many different repositories. |
57a972a
to
2a7390b
Compare
Signed-off-by: Victor Moene <[email protected]>
2a7390b
to
de6ce6a
Compare
Merge together:
cfengine/masterfiles#3029
#5834