jackie-ob
jackie-ob
The primary change is implementing `AzureStorage` (analogous to existing `S3Storage`, `LocalStorage`). We are consciously deferring the decision of having first class "data tools" support for Azure. There are some necessary...
The general idea is to make `tag list` output script friendly.
The initial release of tag mutation will include the following methods: * A - `Run.(add|remove|replace)_tag` (singular) * B - `Run.(add|remove|replace)_tags` (plural). For internal backwards compatibility reasons, A methods accept iterables...
Tasks can be attempted multiple times, each attempt getting an attempt_id. Each attempt also associates a list of associated Metadata records (also called `Metadatum` in code), which get persisted to...
In deployments where UI static and UI backend services have different origins, preflight CORS checks fail. This is true if the deployment architecture does not include any HTTP level routing...
Scenario: * UI filters for runs with tag = A. * A run R gains A through tag mutation * UI run listing should immediately pick up R. Status quo...
Metaflow client API will enforce these rules: * Max size of any single tag * Max size of a tag set (e.g. when first initializing a tag set at start...
Right now, various Metaflow Ids (e.g. flow ids, run ids, etc.) are passed straight from client request to Postgres SQL query without any validation. With the advent of tag mutation...