augray
augray
There are a few places that do read-modify-write with runs: - resolver jobs - the server (for updating runs from external jobs) - the worker (for storing outputs/exceptions) - eventually...
When a resolution fails, the run objects are moved to the FAILED state, but the k8s jobs for them are not necessarily cleaned up. We should fix that and clean...
Resolver pods can get evicted for various reasons, and then replaced. These pods stick around for long-ish periods of time, so it would be good to have them be resilient...
There are some use cases for this, like adding tracking for Sematic executions in external systems by the Sematic run id.
We have one case where an env var is expected to set the server address without the http (`SEMATIC_SERVER_ADDRESS`) and one where it is expected to have it (`SEMATIC_API_ADDRESS`). `SEMATIC_WORKER_API_ADDRESS`...
It would be helpful if Sematic functions could have associated timeouts, such that if they take longer than a specified time the function automatically fails.
It would be nice to have support for the latest stable python version. We currently have some libraries that aren't playing well on 3.10 (I think eventlet, perhaps?).
If a pod can't be scheduled within 30 min (or some other appropriate number), fail out with a useful error message. The error message should ideally specify the message for...
Currently there is logic that attempts to cast dataclass values by progressively setting the field values. This casting logic runs even when none of the field values would *actually* be...
Many users expect `` to hide text from being displayed in Markdown, and Sematic accepts markdown for docstrings. However, comments of that format get displayed. We should suppress them.