Note: the error when I received when I did not explicitly change the dimensionality looked like this (I could not launch and was not sure why)
Nastya Rusina
5 months ago
Hi Greg, thank you a lot for bringing it up 🙂 I will look from flyteconsole side, to understand what can be done to:
• Automatically change Dimensionality to
Multipart
in case if input type FlyteDirectory is used
Provide more descriptive error if possible
@Yee do we have any workflows in demo with blobDimensionality in use?
I was able to reproduce locally bug you mentioned, we have created a ticket to track the fix https://github.com/flyteorg/flyteconsole/issues/336 . However I don’t have an ETA yet, as we have some more pressuring changes in pipeline. We will notify the thread when fix would be done.Regarding “more descriptive errors” - the task https://github.com/flyteorg/flyteconsole/issues/337 was created. This one applies to a wider set of conditions, updates in this area won’t be brought up in this thread.
Both Issue #336 (Dimensionality) and issue #337 (more descriptive errors) are now fixed, and available from *FlyteConsole - v0.51.1* . Thanks a lot to
@eugene jahn for providing fixes 🎉