Skip to content
This repository has been archived by the owner on Feb 14, 2021. It is now read-only.

Inconsistency between check_failed and did_error #71

Open
bcomnes opened this issue May 7, 2016 · 2 comments
Open

Inconsistency between check_failed and did_error #71

bcomnes opened this issue May 7, 2016 · 2 comments

Comments

@bcomnes
Copy link
Contributor

bcomnes commented May 7, 2016

Is there a reason that when a ok check fails that it is handled with check_failed instead of did_error? They seem to serve a similar function.

@mattly mattly added the bug label Jan 26, 2018
@mattly mattly added this to the 0.11.1 release milestone Jan 27, 2018
@mattly
Copy link
Owner

mattly commented Jan 29, 2018

from what I can remember and what I can read, check_failed was created for the check type (which is basically a way of hooking arbitrary expressions into the ok system) and is only updated on status operations, which are performed during satisfy as well. did_error is meant to be used alongside did_install, did_upgrade, did_update and the like to determine if the satisfy (install | upgrade) operation failed. This could probably be better documented.

@mattly mattly modified the milestones: 0.11.1 release, 1.0 release Jan 29, 2018
@mattly mattly added documentation and removed bug labels Jan 29, 2018
@bcomnes
Copy link
Contributor Author

bcomnes commented Jan 29, 2018

👍 Feel free to close unless you want to keep the reminder to documnet. I've lost too much context to come up with a quick fix on this atm.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants