Hey folks! 👋 I’m running into an issue where when I register a

NotebookTask

, subsequent tasks in the same project all get the container args from notebook task, even if it’s in a completely different workflow. For example, the task named

get_mean_agc_by_year_task

, the task sees the container args:

["pyflyte-fast-execute","--additional-distribution","<path redacted>","--dest-dir",".","--","pyflyte-execute","--inputs","{{.input}}","--output-prefix","{{.outputPrefix}}","--raw-output-data-prefix","{{.rawOutputDataPrefix}}","--checkpoint-path","{{.checkpointOutputPrefix}}","--prev-checkpoint","{{.prevCheckpointPrefix}}","--resolver","flytekit.core.python_auto_container.default_task_resolver","--","task-module","flyte.arr_yield_estimates.eligibility.supplemental.natural_forest","task-name","plot_natural_support_forest_results"]

Things look ok again when I remove the NotebookTask and re-register 🤔

This definitely sounds like a bug. Assuming

plot_natural_support_forest_results

is your notebook task? Are you getting any failures for the notebook task or other tasks? What does the behavior look like when you try to run?

cc @high-accountant-32689 did we ship something that maybe broken instances tasks?

Very interesting. Nothing jumps out immediately, let me take a look.

Daniel - yes plot_natural_support_forest_results is the name of my notebook task 👍 Using flytekit 1.11.0 (flytekitplugins-papermill and flytekitplugins-deck-standard are 1.11.0 too)