You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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
pyflyte
:python
: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?
Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: