about summary refs log tree commit diff
path: root/test/python/server_test_case.py
diff options
context:
space:
mode:
authorPjotr Prins <pjotr.public01@thebird.nl>2026-11-15 13:47:21 +0000
committerPjotr Prins <pjotr.public01@thebird.nl>2026-11-15 13:47:21 +0000
commit2bfb2187d14e2bec6532633277c642e67c33f56c (patch)
tree3ed58816930348282d8c42792d2a40841984f4ba /test/python/server_test_case.py
parent9bb67549beb69c294b70210c38ff70a676a261ec (diff)
downloadgenenetwork4-2bfb2187d14e2bec6532633277c642e67c33f56c.tar.gz
monitor: a check may decline to run, and the genotype plot follows the real flow
Two separate faults behind one red line. The check posted `{group, markers: []}`,
which is not this endpoint's request at all -- /plot/genotypes draws the numbers
it is sent (`marker`, `genotypes`, `values`), it looks nothing up -- and the
trait it picked (BXDPublish 10001, LOD 2.93) is *below* the fence that
/peak-genotypes enforces (LOD >= 3), so even a correct payload would earn a
422. So: checks can now build their body from earlier replies (`body` may be a
callable), and can decline with a reason (`Skip`) instead of going red --
calling a deliberately fenced endpoint's 422 a failure trains a reader to
ignore red. The check now walks the documented chain: a published trait whose
LRS is at least 14, its peak-genotypes calls, its values, then the plot.

Full monitor after: 38 ok, 0 failed, 1 skipped, 0 busy.
Diffstat (limited to 'test/python/server_test_case.py')
0 files changed, 0 insertions, 0 deletions