From f9adbcc3dc0ffe888b459503d39e113d36f780ab Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Esteban=20Zim=C3=A1nyi?= Date: Tue, 1 Sep 2026 16:45:36 +0200 Subject: [PATCH] Name the family the probe symbol belongs to The image check reads ts2cell_in, tposechain_in and temporal_merge out of the libmeos the image holds, and the sentence above it names the families a narrow build leaves out. The temporal pose chain is one of the types the POSE family builds, so POSE is the entry whose absence tposechain_in reports. --- .github/workflows/docker.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/docker.yml b/.github/workflows/docker.yml index 0df5d1c..621bb03 100644 --- a/.github/workflows/docker.yml +++ b/.github/workflows/docker.yml @@ -88,7 +88,7 @@ jobs: # A build that succeeds still proves nothing about WHICH library the image holds, # and a narrower one is the failure this guards: a libmeos configured without - # -DALL=ON carries no S2CELL and no POSECHAIN entry, while the jar generated from + # -DALL=ON carries no S2CELL and no POSE entry, while the jar generated from # the catalog of master names both. `temporal_merge` is the positive control — were # it missing too, the check would be reading the wrong file rather than a narrow # build. The jar assertion is the other half: the shaded jar carries JMEOS itself,