[BUG] Fail to Run the Workflow of FlyteFile Example Locally

[JiangJiaWei1103]

Describe the bug

Following the instruction of the FlyteFile example in User guide, I run the workflow locally without specifying the option --output_location. Then, an error is raised as shown in the following screenshot:

Expected behavior

The output csv file containing the normalized columns is stored to a random location.

Additional context to reproduce

1. Clone the Flytesnacks repo to the local machine.

git clone https://github.com/flyteorg/flytesnacks.git

2. Cd into the repo directory.

cd flytesnacks

3. Run the workflow locally. Both commands fail.

• Run with pyflyte:

pyflyte run examples/data_types_and_io/data_types_and_io/file.py normalize_csv_file --csv_url "https://people.sc.fsu.edu/~jburkardt/data/csv/biostats.csv" --column_names "[\"Name\", \"Sex\", \"Age\", \"Heights (in)\", \"Weight (lbs)\"]" --columns_to_normalize "[\"Age\"]"

• Run with python:

python examples/data_types_and_io/data_types_and_io/file.py

Screenshots

Other Observations

The error message of this bug is shown as follows:

If the workflow is run with --output_location specified, the output csv file is successfully generated and stored:

In addition, the workflow successfully finishes through a remote test:

Are you sure this issue hasn't been raised already?

• Yes

Have you read the Code of Conduct?

• Yes

[welcome]

Thank you for opening your first issue here! 🛠