Expected Behavior

I am able to analyse where the time is spent during an execution of a task or pipeline.
I can break down the execution time into time spent reconciling logic, fetching resources, pulling images, running containers, and more.

Actual Behavior

Right now with opencensus metrics we have data about the overall duration but no breakdown view.

Additional Info

We could ins

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.

Summary

The Argo UI doesn't currently allow sorting by name or any other attribute such as last sync time.

Motivation

I would use this when scanning the list of available apps by name, sorting by deployment time, etc.

Proposal

Client-side sorting of the fields in memory.

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

We’ve been seeing a lot of great work to build and convey patterns for how to use Great Expectations across the primary cloud platforms, but we don’t currently have an implementation of the TupleStoreBackend for Microsoft Azure.

I believe an implementation of that backend would help many users, and would be directly analogous to the implementations of TupleGCSStoreBackend and `TupleS3StoreBa

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

Hi, would it be possible to make the user warnings display only when using pipes that actually depend on these imports? Or at least display them in a way that allows filtering out (with logging package perhaps)?

It's just a minor flaw on otherwise great package. Awesome work!