Skip to content

FORCE higher level: Staging step returns opaque JSON decode error when passed an invalid or nonexistent STAC catalog #22

@Hneuschmidt

Description

@Hneuschmidt

When running the staging part of the TSA workflow on a nonexistent STAC catalog, the error returned by the step (and the workflow)
is very generic (Could no parse JSON):

  File "/home/docker/.local/share/uv/python/cpython-3.13.12-linux-x86_64-gnu/lib/python3.13/json/decoder.py", line 363, in raw_decode
    raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)
INFO [job staging] Max memory used: 0MiB

This is likely a common failure node, as the STAC resources generated by FORCE level 2 are temporary and will expire at some point.
This error should be caught and a more helpful error raised.

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions