mlops

At the moment, from API there are two useful columns about tasks:

However, in tabs (views) there are possible columns tasks:created_at a

Describe the bug
data docs columns shrink to 1 character width with long query

To Reproduce
Steps to reproduce the behavior:

1. make a batch from a long query string
2. run validation
3. render result to data docs
4. See screenshot
   <img width="1525" alt="Data_documentation_compiled_by_Great_Expectations" src="https://user-images.githubusercontent.com/928247/103230647-30eca500-4

With a config like this

{
    "METAFLOW_DATASTORE_SYSROOT_S3": "s3://mf-test/metaflow/",
}

(note a slash after METAFLOW_DATASTORE_SYSROOT_S3)

metaflow.S3(run=self).put* produces double-slashes like here:

s3://mf-test/metaflow//data/DataLoader/1630978962283843/month=01/data.parquet

The trailing slash in the config shouldn't make a difference

Description

We're running usability tests and would love for you to record walking through our tutorials. The idea for this ticket is that you do a screen capture walking through one of more of the following examples:

• Hello World! (15 minutes)
• [Iris Dataset](https://kedro.readthedocs.io/en/stable/02_get_started

🚨🚨 Feature Request

• Related to an existing Issue
• A new implementation (Improvement, Extension)

If your feature will improve HUB

Need a way to check if a dataset already exists.

hub.empty throws an error if a dataset exists and hub.load throws an error if the dataset does not exist.

Need a way to check if a dataset already exists without throwing a

Use case

Polyaxon tracking can be used to automatically log all information generated by Ludwig.

We should probably think about adding support for Polyaxon's tracking module in Ludwig contrib.

For SC Operator it may be a good idea to generate CRD manifests from inside a docker container.
This should provide reproducible generation step and avoid "produces different output on my machine" issues.

Linter should also fail if generation of manifests produce diff with the commited version.

Is your feature request related to a problem? Please describe.
I have a framework that handles the offline store. It creates the tables, indexes, reads data from different data sources, does some transformations, and then inserts into the offline store. As a part of this, I can construct the entities, feature views, feature services, etc, a instance of the ParsedRepo class for Feast. What I n

When a component gets input parameters, its input parameters may not exactly match the component input spec's requirements.

In such a case, we should consider adding auto type conversions for possible type mismatches.
Right now, string to other type conversions have been implemented at [code link](https://github.com/kubeflow/pipelines/blob/ca6e05591d922f6958a7681827aea25c41b94573/v2/driver/dri

It consists of two tasks

• proofreading the Chinese version doc docs/cn/data_import.md
• translating this Chinese version to English, and named as docs/en/data_import.md

Proposed refactoring or deprecation

Output informative messages when run parameter cannot be set (i.e. type is not supported by storage)

Motivation

To give users clear error messages and improve onboarding experience.

Pitch

When setting run parameter of unsupported type I would like to get a precise error describing what was done wrong instead of generic Python exception (`No

Describe the issue

Currently we run the Linter CI for golang repos using the golang-ci-linter binary. But according to the documentation it is faster and better to use the github action.
https://golangci-lint.run/usage/install/

The UX of all the error highlighting is also better.

What if we do not do this?

Finding linter errors is troublesome as users have to parse through the cons

Contact Details [Optional]

support@zenml.io

Describe the feature you'd like

Currently our CLI offers a way to install the python packages that are required for a given integration. However, some of our integrations also have system requirements that are necessary to make them work (graphviz, kubectl, etc. ).
All system requirements should be listed on an integration level, just

The chrono crate should be completely removed from the codebase and replaced with time.

Since we changed the domain of the docs to docs.ploomber.io
We need to search in all of our repos: ploomber, soorgeon, soopervisor and projects:
Look for the ploomber.readthedocs.io address and replace it with docs.ploomber.io

Please follow the contribution guildelines for the docs.