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
When using datetime.date as a type hint in a task, flyte appears to lose the input file:
FileNotFoundError: Failed to convert inputs of task 'wf.hello_date':
[Errno 2] No such file or directory: '/var/folders/yv/l9q99njs4x35fp3x2_g8gykh0000gn/T/flyte-3c_0m7fn/raw/4f3290e595dcb84915aa481e45b92074/1f3c185c4a74647a397e5ca43ddcb5b3'
Expected behavior
Flyte should recognize the datetime.date object the same way it recognizes the datetime object.
pyflyte run --remote -p daniel date_bug/wf.py wf --date "2024-01-03"
This results in the error:
FileNotFoundError: Failed to convert inputs of task 'wf.hello_date':
[Errno 2] No such file or directory: '/var/folders/yv/l9q99njs4x35fp3x2_g8gykh0000gn/T/flyte-3c_0m7fn/raw/4f3290e595dcb84915aa481e45b92074/1f3c185c4a74647a397e5ca43ddcb5b3
Screenshots
No response
Are you sure this issue hasn't been raised already?
Yes
Have you read the Code of Conduct?
Yes
The text was updated successfully, but these errors were encountered:
Flyte currently does not support the datetime.date object for passing to or from tasks. According to this GitHub issue, the Flyte team is aware of the limitation and has discussed adding a type transformer to support datetime.date. As a workaround, you can use datetime.datetime or convert the date to a string.
Would you like more details on how to implement this workaround?
Describe the bug
When using
datetime.date
as a type hint in a task, flyte appears to lose the input file:Expected behavior
Flyte should recognize the
datetime.date
object the same way it recognizes thedatetime
object.Additional context to reproduce
Good example:
pyflyte run --remote -p daniel date_bug/wf.py wf --date "2024-01-03"
This has no errors and works as expected.
Bad example:
pyflyte run --remote -p daniel date_bug/wf.py wf --date "2024-01-03"
This results in the error:
Screenshots
No response
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: