munki/munki-facts

facts that trace cause munki-facts to trace

Closed this issue · 4 comments

if munki-facts has a script that has a python trace error, it will cause munki-facts to also fail.

Munki-facts should handle this and move on to the next fact, without losing the other conditions.

I would accept a PR that addresses this. Or if you aren't likely to provide one, could you at least provide a fact that fails?

https://gist.github.com/erikng/3246bed1ad1d87345ec38dddd2254fb8

This should trace at the loginwindow, due to a TypeError (ultimately caused by user being None). if you name it something like a_fact.py it will be one of the first facts ran.

365c45b should address this.