pipeline

We recently upgraded to ArgoCD v2.1.0+d0b2d55 and have noticed that when browsing the UI the history in Firefox gets really polluted when changing pages.

Steps to reproduce;

1. Open a new browser tab
2. Navigate to ArgoCD
3. Long-press back button on browser

Expected

• A single entry for ArgoCD

Actual

History contains 15 separate entries for the same URI, preventing the

The Adding New Types section under the DEVELOPMENT.md has a reference to alpha APIs instead of beta. We are now adding a new CRD to beta APIs. No changes being done in alpha APIs.

Please change this note:

Add go structs for the types in pkg/apis/pipeline/v1alpha1 e.g condition_types.go This should 

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

To allow for both contributions, I think we should specify the following in Contributing.md:

1. Contributors need to add their dataset to the the doctree: https://github.com/quantumblacklabs/kedro/blob/master/docs/source/15_api_docs/kedro.extras.datasets.rst
2. Contributors need to add their dataset to catalog json schema: https://github.com/quantumblacklabs/kedro/blob/master/sta

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

Java and Python provide logging frameworks for recording errors and stack traces. Logging can be configured to format those messages, such as by removing newlines from stack traces, adding timestamps, and putting a log level (INFO, WARN, ERROR) on the message. In the future, it may also include json structured logging. Using the logging framew

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