Files
secs-gem/apps
raphael c8e8e80735
tests / build-and-test (push) Successful in 2m7s
tests / thread-sanitizer (push) Successful in 2m33s
tests / tshark-dissector (push) Successful in 2m15s
tests / secs4j-interop (push) Failing after 1s
tests / libfuzzer (push) Successful in 3m7s
secs_server: relative-path defaults so the binary runs outside docker
Previously --config / --state-table / --pj-state-table /
--cj-state-table defaulted to /app/data/..., which only resolves
inside the docker image.  A host build run from the repo root
errored out unless every flag was passed explicitly.

Switch to data/equipment.yaml (and siblings) relative to CWD —
docker still works because WORKDIR=/app puts /app/data/... at the
same relative location, and host builds run from the repo root
resolve to <repo>/data/....  Existing callers that pass explicit
paths (the proof commands, tshark_validate.sh, secs4j_validate.sh,
docker compose) are unaffected.

Verified --validate-config under docker still finds all four YAMLs
and the tshark proof still passes (69 frames, 0 malformed).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-06-09 19:00:45 +02:00
..