Open Sovietaced opened 2 weeks ago
@Sovietaced , after https://github.com/flyteorg/flyte/pull/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
github is not cooperating, https://github.com/flyteorg/flyte/pull/5981/files#diff-36a9a91abc6f8873fbb6ca3e82f73a10f0cf99b69812a2715ea237b27bac1652R108-R109 doesn't render anything for me. Can you link to the file directly?
github is not cooperating, https://github.com/flyteorg/flyte/pull/5981/files#diff-36a9a91abc6f8873fbb6ca3e82f73a10f0cf99b69812a2715ea237b27bac1652R108-R109 doesn't render anything for me. Can you link to the file directly?
One of these two can still be nil it seems. https://github.com/flyteorg/flyte/blob/master/flyteadmin/pkg/manager/impl/util/resources.go#L108-L109
I can upstream a change I had.
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?