New RunLLM response generated: >>>*# Question* Hi, I have a container task whose output is a FlyteDirectory (an s3 path) and its somehow interpreting it as a single blob. see:

{
  "type": "single blob",
  "uri": "<s3://bucket_name/prefix/results>"
}

A subsequent task that uses this output as an input is erroring out:

Message:

    TypeTransformerFailedError: Error converting input 'results_master' at position 0:
  <s3://bucket_name/prefix/results> is not a directory.

# Answer The issue you're encountering is related to the handling of

FlyteDirectory

in

ContainerTask

. Currently, Flyte has limitations in supporting

FlyteDirectory

as inputs or outputs for

ContainerTask

, as it treats them as single blobs rather than directories. This is a known issue and is being tracked in Flyte's GitHub issue #3632. Would you like more details on possible workarounds or solutions for this issue? Sources: - Flyte GitHub Issue #3632 Slack Link https://.slack.com/archives/CP2HDHKE1/p1729883147.219529 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.