Skip to content
#

pipeline

Here are 3,026 public repositories matching this topic...

jannfis
jannfis commented Dec 19, 2021

Summary

The Argo CD core mode should allow the user to set a permanent path to a K8s client configuration file, instead of either using ~/.kube/config per default or having to specify --kubeconfig for each command.

Motivation

Some K8s distributions by default install a Kubernetes client CLI (kubectl) which uses a custom path for its configuration. For example, K3s uses `/etc/ran

Aylr
Aylr commented Dec 28, 2020

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
kedro
jx
ankitm123
ankitm123 commented Jan 5, 2022

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

Bobgy
Bobgy commented Dec 14, 2021

When a component gets input parameters, its input parameters may not exactly match the component input spec's requirements.

In such a case, we should consider adding auto type conversions for possible type mismatches.
Right now, string to other type conversions have been implemented at [code link](https://github.com/kubeflow/pipelines/blob/ca6e05591d922f6958a7681827aea25c41b94573/v2/driver/dri

timbaileyjones
timbaileyjones commented Aug 12, 2019

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

Improve this page

Add a description, image, and links to the pipeline topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the pipeline topic, visit your repo's landing page and select "manage topics."

Learn more