augray

If the resolver pod cannot be started, a useful error message should be shown in the UI

2

If the resolver pod cannot be started after a certain amount of time, we should surface a useful message in the UI. One possible cause of this is if the...

Consider this test: ```python from enum import Enum, unique from sqlalchemy import Column, types # Sematic from sematic.db.models.run import Run from sematic.db.models.base import Base from sematic.db.tests.fixtures import persisted_run, run, test_db...

When you terminate a resolution, it only has a certain amount of time to clean up resources before the pod is force-killed by k8s. This might not be enough time...

We have docs that reference adding settings for specific plugins, ex: ``` sematic settings set -p sematic.plugins.publishing.slack.SlackPublisher SLACK_WEBHOOK_TOKEN XXX/YYY/ZZZ ``` But actually using `-p` gives: ``` ERROR: -p :: Unrecognized...

Nesting a pipeline under another can cause it to be omitted from the run page

1

To reproduce: - create a Sematic func at some path (ex: `foo.bar.baz`) - execute it as the root function - verify it now shows up on the pipelines page -...

This will allow access to the Sematic API from within Ray tasks

Currently the pipeline view only shows 10 pipelines at a time, and seeing more requires pushing a "next" button. The "next" button is small and hard to notice. The same...

Resolver logs are often useful for us to have, but it's hard to tell a user how to access them. Ideally we could have a button that they could push...