-
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
Set run model default timestamp to 0 #1140
Conversation
Without setting to 0, the finished at field could be null if the argo workflow is already evicted from the cluster. This result in errors parsing the table. Alternatively we can use sql.NullInt64 type to parse the sql but that's less elegant.
/assign @rileyjbauer |
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
/test kubeflow-pipeline-e2e-test |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: IronPan 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 |
1 similar comment
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: IronPan 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 |
* fix conditional in ONNX storage URI validation * unit tests for ONNXSpec.Validate
Without setting to 0, the finished at field could be null if the argo workflow is already evicted from the cluster.
This result in errors parsing the table.
Alternatively we can use sql.NullInt64 type to parse the sql but that's less elegant.
This change is