Skip to content
#

pipeline

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

vdemeester
vdemeester commented Oct 1, 2020

Expected Behavior

OpenShift Pipelines 1.0.1 installed on OpenShift 4.4.17 is failing to run the below TaskRun in some specific namespaces. While it's working on some namespaces it's failing in specific with the following error reported in tekton-pipelines-controller:

{
  "level": "error",
  "logger": "tekton.taskrun-controller",
  "caller": "taskrun/taskrun.go:163",
  "msg": "
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
deepyaman
deepyaman commented Oct 2, 2020

Description

I'm always frustrated when I want to create a new data set... or is it dataset?

Context

  • As a contributor, I do my best to align to the prevailing style/convention.
  • As a user, I try to mimic Kedro convention when I create my own datasets.

In both cases, it bothers/confuses me to see inconsistencies. Maybe it's just me. 🤷‍♂️

List of Inconsistencies

  • All datase
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

samuell
samuell commented Aug 27, 2020

Analogous to how you can use basename to get only the filename of a path, like in:

p.SetOut("out1", "{i:in1|basename}.out.txt")

... it would be useful to also be able to extract only the directory, using dirname as a modifiers, so:

p.SetOut("out1", "{i:in1|dirname}/newfilename.txt")

This will also allow introducing another level of folders based on a previous

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.