Summary

To make the onboarding experience better with ArgoCD and Helm chart I would like to suggest to improve the documentation page https://argo-cd.readthedocs.io/en/stable/user-guide/helm/ about how to work with Helm charts.

Motivation

I believe lot of people have questions when they first time try to deploy a simple Helm app (for example [nginx controller](https://kubernetes.githu

Description

We're running usability tests and would love for you to record walking through our tutorials. The idea for this ticket is that you do a screen capture walking through one of more of the following examples:

• Hello World! (15 minutes)
• [Iris Dataset](https://kedro.readthedocs.io/en/stable/02_get_started

YAML parsers take a YAML in a string and returns respective deserialized objects including Tasks, TaskRuns, Pipelines and PipelineRun - thank you @imjasonh 🎉

These parsers can help us simplify the many tests we have in [pipelinerun_test.go](https://github.com/tektoncd/pipeline/blob/302895b5a1ca45c02a85a9822201643c159fe0

Environment

Cloud

Current Behavior

When trying to open up developer tools to get a better understanding of an error, the connector set up page will not scroll when dev tools is open. (recording can be provided on request).

You can scroll the knowledge base on the page but not the connector set up.

Expected Behavior

Be able to scroll a page when dev tools is open.

Steps

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

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.

Not sure what the error is, but lint passes in the CI and locally even if exported structs dont have comments.
Most probably, it's an issue with the golangci yaml config we use.

Also we use revive instead of golint (which is deprecated), may be some setting in revive needs to be enabled?

If we check the goreport card, we can see the issues: https://goreportcard.com/report/github.com/jenkins

We have a stdlib, written by @qorrect , which provides some standard functions by using s-strings.

We could fill this out with some more standard functions — e.g. EXP, MOD, string functions, etc.

Possibly there is even a definition of these somewhere?

I have uploaded the metrics_visualization pipeline in the Kubeflow Console and when I invoke a run I am able to see the visualizations yet they are not seen in the run output

![image](https://user-images.githubusercontent.com/59866888/153585857-cda2921e-48b9-4528-b568-e8866fffb993.

We distinguish different types of terminals by judging process.stdout. On the default terminal, we use console to output logs, while on the TTY terminal, we use the ora. We have added a time prefix to Ttylogger, but this feature has not been implemented on the DefaultLogger.
Here is the DefaultLogger:
https://github.com/alibaba/pipcook/blob/main/packages/cli/src/utils/index.ts#L212

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