Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Watson Openscale Components to manage models #950

Merged
merged 2 commits into from
Mar 15, 2019
Merged

Watson Openscale Components to manage models #950

merged 2 commits into from
Mar 15, 2019

Conversation

animeshsingh
Copy link
Contributor

@animeshsingh animeshsingh commented Mar 10, 2019

To be used in a subsequent pipeline being drafted. Enables fairness and quality monitoring


This change is Reviewable

@Tomcli
Copy link
Member

Tomcli commented Mar 12, 2019

/approve

@Tomcli
Copy link
Member

Tomcli commented Mar 12, 2019

/assign @Tomcli

@k8s-ci-robot
Copy link
Contributor

@Tomcli: GitHub didn't allow me to assign the following users: Tomcli.

Note that only kubeflow members and repo collaborators can be assigned and that issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

/assign @Tomcli

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

1 similar comment
@k8s-ci-robot
Copy link
Contributor

@Tomcli: GitHub didn't allow me to assign the following users: Tomcli.

Note that only kubeflow members and repo collaborators can be assigned and that issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

/assign @Tomcli

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@k8s-ci-robot
Copy link
Contributor

@animeshsingh: GitHub didn't allow me to assign the following users: Tomcli.

Note that only kubeflow members and repo collaborators can be assigned and that issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

/assign @Tomcli

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

1 similar comment
@k8s-ci-robot
Copy link
Contributor

@animeshsingh: GitHub didn't allow me to assign the following users: Tomcli.

Note that only kubeflow members and repo collaborators can be assigned and that issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

/assign @Tomcli

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@@ -0,0 +1,123 @@
import json
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This file is a program, but it's not fully obvious what exactly it is doing. If you prefix the name with a verb it would be easier to understand.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed in the latest push by @Tomcli

@Ark-kun
Copy link
Contributor

Ark-kun commented Mar 12, 2019

General comment:
Do these components provide outputs that can be consumed by downstream components?

@Ark-kun
Copy link
Contributor

Ark-kun commented Mar 12, 2019

It would be great if you've added component.yaml definitions so that the components can be easily loaded and so that all inputs/outputs can be easily seen at a glance.

@Ark-kun
Copy link
Contributor

Ark-kun commented Mar 12, 2019

Otherwise
/lgtm

@googlebot
Copy link
Collaborator

So there's good news and bad news.

👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there.

😕 The bad news is that it appears that one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that here in the pull request.

Note to project maintainer: This is a terminal state, meaning the cla/google commit status will not change from this state. It's up to you to confirm consent of all the commit author(s), set the cla label to yes (if enabled on your project), and then merge this pull request when appropriate.

ℹ️ Googlers: Go here for more info.

@Tomcli
Copy link
Member

Tomcli commented Mar 14, 2019

I agree with my commits being contributed to this project.
/cla yes

@animeshsingh
Copy link
Contributor Author

@Ark-kun your comments have been taken care of by @Tomcli, and has has consented to those. Please take a look

@vicaire
Copy link
Contributor

vicaire commented Mar 15, 2019

/lgtm
/approve

@k8s-ci-robot k8s-ci-robot assigned vicaire and unassigned vicaire Mar 15, 2019
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Tomcli, vicaire

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@vicaire vicaire merged commit cc3f214 into kubeflow:master Mar 15, 2019
implementation:
container:
image: docker.io/aipipeline/monitor_fairness:latest
args: [
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

General comment: To future-proof your component it's desirable to also specify the command-line (command:). Having the full command-line available allows adding some special wrappers to it.

@Ark-kun
Copy link
Contributor

Ark-kun commented Mar 15, 2019

Thanks for fixing all the issues.
/lgtm
/approve

cheyang pushed a commit to alibaba/pipelines that referenced this pull request Mar 28, 2019
* openscale componenets to manage models

* renamed component filename, updated with component.yaml (#1)
Linchin pushed a commit to Linchin/pipelines that referenced this pull request Apr 11, 2023
…ng/cloudprovider/aws (kubeflow#950)

Bumps [urllib3](https://github.com/urllib3/urllib3) from 1.26.4 to 1.26.5.
- [Release notes](https://github.com/urllib3/urllib3/releases)
- [Changelog](https://github.com/urllib3/urllib3/blob/main/CHANGES.rst)
- [Commits](urllib3/urllib3@1.26.4...1.26.5)

---
updated-dependencies:
- dependency-name: urllib3
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>

Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants