Rob Browning
Rob Browning
It was now causing pedantic? failures, and it looks like (presumbaly via the clj-parent update) we now pull in a new enough version. cf. da3c3642a1ae2e60517a2fb5a2b09e5631cdf50d
Without more potentially substantial changes to the query engine, we can't drop all the merging (e.g. the facts projection from the inventory endpoint) and switch to independent stable and volatile...
Reduce irrelevant error-related output (particularly unnecessarily/undesirably logged stacktraces)
Among other things, stop logging stacktraces for known errors (e.g. query/command parse errors, expected sql errrors, etc.).
In an attempt to decrease the steady-state Postgres write load PuppetDB currently stores each factset in two separate jsonb fragments, stable and volatile. Whenever a fact changes, the top-level subtree...
At the moment, benchmark generates two different flavors of an exported `resources` query when `--catalog-query-pct` is positive. Both of these filter on the resource `type`, without any consideration of the...
The current factset storage rests on the assumption that a nontrivial subset of top-level facts (including any subtree) will never change (though see #3956 for a promising, potential relaxation/improvement there)....
In an attempt to decrease the steady-state Postgres write load PuppetDB currently stores each factset in two separate jsonb fragments, stable and volatile[^1]. Whenever a fact changes, the top-level subtree...
As previously reported in https://github.com/akhudek/zip-visit/issues/8 PuppetDB crashes when fast-zip is upgraded to 0.7.0. In fact, the trouble actually started with the use of `.next` in core.cljc in 0.6.0. That's because...