pipeline

Checklist:

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

Describe the bug

Values from an Application CRD values block that overrides values from value files are not visualized under the App Details -> Parameters -> Parameters section.

**To Repro

Currently, the Pipeline tutorial uses git and image PipelineResources for Task inputs/outputs see here. As there are beta-supported alternatives for both PipelineResources ([for git](https://github.com/tektoncd/pipeline/blob/master/docs/migrating-v1alpha1-to-v1beta1.md#replacing-a-git-resou

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.

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

Summary

When creating docker images for Java applications in the current setup in Jenkins-X the application and all dependencies are all placed in one jar file, meaning it will be in one layer in the docker image.

This means that when new versions of the application are created the unchanged dependencies can't be reused.

It would be a great enhancement if the application code where p

Tell us about the problem you're trying to solve

Today we are able to specify the log levels of logs emitted by Airbyte code via env vars.

We should probably also allow doing the same to some of the 3rd party libs we use that are essential to how Airbyte does [things](https://github.com/airb

async def sub(a, b):
  return a - b

See fridgerator/PyNode#25 for details.

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

As reported by @jonalv , it can be confusing what is happening when if the globber pattern does not catch any files.

The suggestion is to:

• Log when the globber starts, with the pattern used
• Issue a warning if the globber doesn't match any files at all