[BUG] Local FlyteFile
whose name contains spaces fail in remote execution with "File Not Found" error
#5445
Closed
2 tasks done
Labels
bug
Something isn't working
flytekit
FlyteKit Python related issue
good first issue
Good for newcomers
Describe the bug
When a user runs a workflow with
pyflyte run --remote ...
where one of the input arguments is aFlyteFile
whose name contains space characters, the remote execution fails due to a mis-replacement of the space character.Expected behavior
The remote execution should succeed and the remote file's path should be consistent with what the expect expects.
What's happening under the hood is that the Flyte task receives the following path:
Whereas the actual file exists under the following (spaces are compatible with S3 paths)
Additional context to reproduce
Here is an example workflow
Step 1 - Stand up a flyte sandbox with
flytectl demo start
Step 2 - Create a local file whose name contains a space with
dd if=/dev/urandom of="foo bar" bs=1048576 count=5
Step 3 - Run
pyflyte run --remote get_file.py wf --f "foo bar"
Screenshots
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: