-
Notifications
You must be signed in to change notification settings - Fork 190
ENT-9980: Properly handle promise locking with edit line #5815
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
5a945a1
to
dd79a5a
Compare
Thank you for submitting a pull request! Maybe @craigcomstock can review this? |
a88a0df
to
368096e
Compare
This file requires the definition of the enum `PromiseResult`. Signed-off-by: Lars Erik Wik <[email protected]>
This file requires the definition of the enum `PromiseResult`. Signed-off-by: Lars Erik Wik <[email protected]>
Signed-off-by: Lars Erik Wik <[email protected]>
Fixed bug causing rendered files can result in erroneously empty files as a result of promise locking. Ticket: ENT-9980 Changelog: Commit Signed-off-by: Lars Erik Wik <[email protected]>
@cf-bottom Jenkins please :) |
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.
Look good to me.
Sure, I triggered a build: Jenkins: https://ci.cfengine.com/job/pr-pipeline/12205/ Packages: http://buildcache.cfengine.com/packages/testing-pr/jenkins-pr-pipeline-12205/ |
@cf-bottom Jenkins please :) |
Alright, I triggered a build: Jenkins: https://ci.cfengine.com/job/pr-pipeline/12221/ Packages: http://buildcache.cfengine.com/packages/testing-pr/jenkins-pr-pipeline-12221/ |
Back-ported to: