Contact

jvq.net would like to hear from:

• Anyone trying jvq in their pipeline. What it caught, what it missed, and what you used before.
• Anyone who got a verdict that looks wrong. A regression on a change that did nothing, or a slowdown it let through.
• Anyone who needs another benchmark format. Say which harness you use and paste a few lines of its output.
• Anyone who found jvqq printing something jq doesn’t. The filter and one input line are usually enough.

Write to info@jvq.net.

Bug reports are also welcome on GitHub, for jvq and for jvqq.

For jvq, it helps to include what jvq version prints, your operating system, the command you ran, and the JSON report (jvq run -json report.json). The JSON holds benchmark names and timings, nothing else from your code.

For jvqq, it helps to include what jvqq --version prints, the filter, a line of input that shows the problem with anything private taken out, and what jq 1.7.1 prints for the same.