Skip to content
#

mlops

Here are 434 public repositories matching this topic...

Aylr
Aylr commented Dec 28, 2020

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
metaflow
tuulos
tuulos commented Sep 7, 2021

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

kedro
datajoely
datajoely commented Oct 6, 2021

Description

In Kedro Viz 3.14.0 we released the ability to automatically reload viz as the user types their code. The full PR for this can be seen here. Whilst this is documented on the kedro-viz github, it's not mentioned anywhere in the core documentation.

Possible Implementation

It would make sense to add the following g

RafalSkolasinski
RafalSkolasinski commented Feb 24, 2021

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.

benhyy
benhyy commented Aug 29, 2021

What steps did you take

Code gets stuck in infinite loop is SageMaker training job gets stopped (unhandled use case)

What happened:

https://github.com/kubeflow/pipelines/blob/master/components/aws/sagemaker/train/src/sagemaker_training_component.py#L57-L66

Above code only caters for training job status Completed or Failed, so if the training job status is marked as `Stopped

amommendes
amommendes commented Oct 12, 2021

Expected Behavior

Feature views should have the creation time (i.e., created_timestamp) at the first feast apply

Current Behavior

Features Views do not have creation time at feature view creation

Steps to reproduce

feast init fs
cd fs
feast apply
feast registry-dump
{
  "spec": {
    "name": "driver_id",
    "valueType": "INT64",
    "description": "driver 
flyte
evalsocket
evalsocket commented Oct 12, 2021

Describe the bug

flytectl register files command doesn't fail without --countinueOnError. It should fail with exit code 0.

Expected behavior

  • Flytectl register should fail if there is an error
  • Flytectl register should not fail if the user passes the --countinueOnError

Additional context to reproduce

No response

Screenshots

No response

Are

alberttorosyan
alberttorosyan commented Oct 16, 2021

In Aim Sequence is defined as a series of homogeneous values (for example, Metric is a series of floating point values).
It is assumed that for the same sequence Run.track() is called for the objects of a same type. However this is not enforced.

Need to enhance the track method to check object's type before writing it to db. The following to be taken into account:

  • tracking of a sequ

Improve this page

Add a description, image, and links to the mlops topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the mlops topic, visit your repo's landing page and select "manage topics."

Learn more