-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
fix(backend): fixes "cannot save parameter" error message. Fixes #9678 #10459
fix(backend): fixes "cannot save parameter" error message. Fixes #9678 #10459
Conversation
Hi @hbelmiro. Thanks for your PR. I'm waiting for a kubeflow member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
/ok-to-test |
/retest |
The failing test is unrelated.
|
@chensun @connor-mccarthy @zijianjoy Can we ignore this failed test and just merge? |
/assign @chensun |
0fec2c2
to
53a2142
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
nit: Maybe we can have a simple unit test to make sure in all scenarios, it should always write down the outputs for conditions and iterationcount?
@Tomcli any ideas on how to do that? |
I don't think there's any test for the main.go. I'm thinking if you can implement a simple check file path exist function to make sure these files are exist after the test case. For the long term implementation, we may want to move this whole logic to use Argo's execution plugin. This way we don't have to spend extra time to create new pods and write files. The test case is just nice to have since the main.go can be implemented in a more efficient way in the future. |
@hbelmiro Can you redo your commits with git signoff? Kubeflow is moving to DCO CLA so all the commits from now on needed to be signed on git. |
Signed-off-by: hbelmiro <helber.belmiro@gmail.com>
53a2142
to
8c554a8
Compare
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Tomcli 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 |
@hbelmiro: The following test failed, say
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. I understand the commands that are listed here. |
@Tomcli tests added. I just had to do a small refactor in |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks @hbelmiro
/lgtm
…flow#9678 (kubeflow#10459) Signed-off-by: hbelmiro <helber.belmiro@gmail.com> (cherry picked from commit 1ae0a82)
fix(backend): fixes "cannot save parameter" error message. Fixes kubeflow#9678 (kubeflow#10459)
…flow#9678 (kubeflow#10459) Signed-off-by: hbelmiro <helber.belmiro@gmail.com>
…flow#9678 (kubeflow#10459) Signed-off-by: hbelmiro <helber.belmiro@gmail.com>
Fixes: #9678
Description of your changes:
I propose these changes as an initial solution, but I'm not sure it's the best one. So, feel free to recommend a better one and I'll be happy to implement it.
This PR modifies the driver so it creates the needed files with default values when
IterationCount
andCondition
arenil
.The errors happen because we return an
Execution
without settingIterationCount
andCondition
here:pipelines/backend/src/v2/driver/driver.go
Line 175 in 87db18e
pipelines/backend/src/v2/driver/driver.go
Line 343 in 87db18e
Which prevents it from creating the files here:
Checklist: