-
Notifications
You must be signed in to change notification settings - Fork 690
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Notebook task run as a AWS Map Task throw exception #3809
Comments
Same issue here. |
@eapolinario any update on this? |
@eapolinario did you take a look at this? |
Yes, I am open to contributing, if it's only flytekit needs some update (python code) @kumare3 |
Could you try not to pass the aws batch config to the notebook task? And update the task-plugin config for
|
I believe the config is already like this, but then the notebook task will run a normal python pod task if I don't pass the was config. @pingsutw |
this has been merged and works. closing |
Describe the bug
Tried to use AWS batch job to run the notebook task using the code example above, got an error:
When I looked at the batch job docker command:
["pyflyte-execute","--inputs","s3://fiolito-eks-cluster/metadata/propeller/liquidity-forecast-development-alg58fr86fmkgh9nqnf4/n0/data/inputs.pb","--output-prefix","s3://fiolito-eks-cluster/metadata/propeller/liquidity-forecast-development-alg58fr86fmkgh9nqnf4/n0/data/0/0","--raw-output-data-prefix","s3://fiolito-eks-cluster/99/alg58fr86fmkgh9nqnf4-n0-0","--resolver","flytekit.core.python_auto_container.default_task_resolver","--","task-module","flytekitplugins.papermill.task","task-name","_dummy_task_func"]
It seems that the _dummy_task_func is wrong which should be
test-notebook
and it comes from:https://github.com/flyteorg/flytekit/blob/master/plugins/flytekit-papermill/flytekitplugins/papermill/task.py#L145
Expected behavior
Notebook task can run as an AWS Map Task without throwing exception.
Additional context to reproduce
Python3.10
flytekit 1.7.0
flytekitplugin-awsbatch 1.7.0
flytekitplugin-papermil 1.7.0
Screenshots
in aws batch console:
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: