@groob what is the significance of the error @wes reported here: https://github.com/osquery/osquery/issues/5698 is this something high-pri we should address before the next release?