You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A task resource configuration that is not completely filled out will cause nil pointers in Flyte Admin because the code assumes every fields is present and complete.
The expected behavior is that Flyte Admin does not throw a nil pointer if only defaults or limits are specified in a task resource configuration.
One of the questions that needs to be answered is what is a valid task resource configuration? Once that is understood we can add some validation to the API which accepts this configuration.
Additional context to reproduce
project: flyteexamples
domain: development
limits:
cpu: "2"
memory: 450Mi
Screenshots
No response
Are you sure this issue hasn't been raised already?
Yes
Have you read the Code of Conduct?
Yes
The text was updated successfully, but these errors were encountered:
@Sovietaced , after #5981 you shouldn't be seeing a panic anymore. This question of whether these incomplete task resource configuration objects should be considered invalid is still pertinent, but can be tackled separately, right?
@Sovietaced , after #5981 you shouldn't be seeing a panic anymore. This question of whether these incomplete task resource configuration objects should be considered invalid is still pertinent, but can be tackled separately, right?
I took a look at that PR but I don't think it will solve the issue where GetDefaults() or GetLimits() is nil
Describe the bug
A task resource configuration that is not completely filled out will cause nil pointers in Flyte Admin because the code assumes every fields is present and complete.
Expected behavior
The expected behavior is that Flyte Admin does not throw a nil pointer if only defaults or limits are specified in a task resource configuration.
One of the questions that needs to be answered is what is a valid task resource configuration? Once that is understood we can add some validation to the API which accepts this configuration.
Additional context to reproduce
Screenshots
No response
Are you sure this issue hasn't been raised already?
Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: