Expected Behavior

As per this doc https://github.com/tektoncd/dashboard/blob/master/docs/walkthrough/walkthrough-istio.md
Tekton pipelines should be up running with istio sidecar injected (manual/automatic).

Actual Behavior

Tekton pipeline pods(controller and webhook) are NOT coming up and are in CrashLoopBackOff status

Steps to Reproduce the Problem

1. istioctl kube-inject -f (

We are using font-awesome V4 and should migrate to font-awesome V5 which comes with its own vue.js module: https://github.com/FortAwesome/vue-fontawesome

Migration includes removing old font-awesome V4 module and changing all existing icons to new vue.js tag.

This is blocked until #114 is merged which comes with first initial integration.

Checklist:

• I've searched in the docs and FAQ for my answer: https://bit.ly/argocd-faq.
• I've included steps to reproduce the bug.
• I've pasted the output of argocd version.

Describe the bug

If an invalid token for a local user exists in argocd-secret, the API will refuse to process any request with an error message similar to:

FATA[0002] rpc error: code =

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

Description & context

Users can specify names for their nodes to identify them more easily. When a name is not explicitly specified, Kedro auto-generates a default name. You can see this in the name property on Node.
The current auto-generated name for a node looks something like this: func_name(inputs) -> outputs. (see implementation of __str__ method on the Node class)

This is

Describe the bug
This is basically one of the issues I called out in #1855:
When I run datasource new and exit the process at any point (e.g. ctrl+c), I still get a block for the credentials in config_variables.yml. However great_expectations.yml doesn't have the datasource entry. I would expect any kind of failure in the datasource creation process to not leave any artifacts.

**To Re

At Node.js, async function will not block the JavaScript thread, and sync does. So it's a best practice in somehow to use the async function instead of sync ones.

Feel free to open small PRs to help us to change the sync to async.

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