Skip to content
#

pipeline

Here are 2,192 public repositories matching this topic...

ImJasonH
ImJasonH commented Oct 14, 2020

Currently we run one replica of the webhook deployment, which makes it a single point of failure in the event of a node outage. The job doesn't do anything that requires running as a single replica, so we should investigate running multiple replicas.

We can crib from Knative Serving, which configures:

  • [a HorizontalPodAutoscaler (HPA) to run 1-5 replicas based on CPU usage](https://github.com
jx
mike-sirs
mike-sirs commented May 22, 2020

Summary

jx create addon istio doesn't work
since v 1.5 istio moved to operator so no folder install/kubernetes/helm/istio

Steps to reproduce the behavior

jx create addon istio

Output

Istio package already downloaded: /Users/msirs/.jx/cache/istio-1.6.0-osx.tar.gz
error: Could not find folder install/kubernetes/helm/istio inside istio clone at /Users/msirs/.jx/cache/istio

kedro
laisbsc
laisbsc commented Oct 14, 2020

Introduction

We need a section in the docs to describe how to migrate from the old-style dataset, e.g. ParquetS3DataSet to the new style e.g. kedro.extras.datasets.pandas.ParquetDataSet.

Suggestion

To migrate from ParquetS3DataSet to pandas.ParquetDataSet, the steps are the following:

In the catalog.yaml:

  • Change the type from ParquetS3DataSet to pandas.ParquetDataSet
fpnick
fpnick commented Sep 21, 2020

Describe the bug
Using a data source with umlauts in the column names leads to the Jupyter Notebook with which the suite can be edited throw an error on startup. The Notebook then doesn't load.
This might be a Jupyter Notebook bug, not sure?!

To Reproduce
Steps to reproduce the behavior:

  1. Initialize a suite with this xlsx file as a data source (nothing fancy: Just two columns, the
timbaileyjones
timbaileyjones commented Aug 12, 2019

While testing another PR, I found that mu pipeline logs command displays information from the pipelines, but also shows this error:

$ mu pipeline logs
[... normal, expected output ...]
func1 ▶ ERROR  ResourceNotFoundException: The specified log group does not exist.
	status code: 400, request id: f7260741-7f69-4772-b4cc-7c6a9c22d264

This error does not occur with the `-f

Improve this page

Add a description, image, and links to the pipeline 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 pipeline topic, visit your repo's landing page and select "manage topics."

Learn more

You can’t perform that action at this time.