Release - v1.10.3 New release published by eapolinario What's Changed • Flyin - Enhance code server installation based on system architecture by @jasonlai1218 in #2016 • changing permissions of /tmp by @pingsutw in #2026 • removes references to unused plugins by @cosmicBboy in #2025 • Separate agent from pyflyte serve by @chaohengstudent in #2019 • Flyin - vscode resume task by @troychiu in #2017 • Run databricks task locally by @pingsutw in #1951 • Fix flyin image by setting py to 3.10 by @ByronHsu in #2031 • Generate version with setuptools_scm and migrate to pyproject.toml by @thomasjpfan in #2028 • Fix Flyin Dockerfile by @Future-Outlier in #2040 • Flyin - fix vscode task path by @troychiu in #2042 • add monodocs ci build in flytekit by @cosmicBboy in #2035 • Support Databricks Agent API 2.1 and Console URL by @Future-Outlier in #1935 • Configures ruff to also run isort by @thomasjpfan in #2043 • Adds setuptools and wheel back in the CI for plugins by @thomasjpfan in #2044 • Add support failure node by @kumare3 in #840 • Add various executions phases which are available in flyteidl, but not in flytekit by @mdjong1 in #2022 • Flyin - VSCode default directory by @troychiu in #2046 • Monodocs dev build by @cosmicBboy in #2048 • Fix warnings in package building by @thomasjpfan in #2051 • Inject version into the build environment by @thomasjpfan in #2052 • Run commands in imageSpec by @pingsutw in #1909 • Add log_links to GetTaskResponse by @pingsutw in #2021 • feat: add

source code

deck by @jasonlai1218 in #2038 • Logger improvements by @kumare3 in #2053 • Preserve stacktrace by @RRap0so in #2056 • Update vscode decorator by @pingsutw in #2018 • Agent uploads input.pb even if task input is None by @pingsutw in #2054 • Fix Base Agent Bug by @Future-Outlier in #2057 • Plugins lazy module loading by @cosmicBboy in #2049 • Add support pandas 2 in flytekit by @pingsutw in #1818 • Enable the flytekit to be pluggable by @thomasjpfan in #2039 • async s3fs plugin by @troychiu in #1936 • Enable python 3.12 by @eapolinario in #2005 • Fixes type hint for configure_pyflyte_cli in plugin by @thomasjpfan in #2065 • Bump apache-airflow from 2.7.3 to 2.8.0 in /plugins/flytekit-airflow by @dependabot in #2066 • Fix: Handle SIGTERM in kubeflow pytorch elastic training plugin by @fg91 in #2064 • unpin envd and add

extra_path

to imagespec by @samhita-alla in #2063 • Change Flyin VScode Default Extensions by @Future-Outlier in #2058 • Allows Secret groups to be optional and configurable by @thomasjpfan in #2062 • [Core feature] Allow dictionaries to be passed to execute workflows that take dataclasses by @jasonlai1218 in #2013 • Flyin - fix the wrong usage of context. by @troychiu in #2070 • Error when multiple configuration plugins are installed by @thomasjpfan in #2069 • Fix Get the Secret Bug from OS Environment Variable by @Future-Outlier in #2077 • Generalized subproc_execute and added tests by @pryce-turner in #2072 • Improve error handling for local execution by @pingsutw in #2068 • Download specific files in FlyteDirectory by @pingsutw in #2059 • Constraint the full fsspec family by @honnix in #2087 • Update default template used by pyflyte init by @neverett in #2041 • Support PodTemplate in ArrayNode by @hamersaw in #2088 • Remove unnecessary newline in plugin README by @douenergy in #2090 • Fix file not found error by @austin362667 in #2079 • add monodocs redirect banner by @cosmicBboy in #2091 • Accelerator docs by @kumare3 in #2076 • Remote workflow & task execution by @kumare3 in #2094 • Print log links in local execution by @pingsutw in #2097 • Bump … flyteorg/flytekit

@high-accountant-32689 there was a breaking change going from v1.10.2 -> v1.10.3. Resources.storage was removed and only Resources.epehemeral_storage was allowed. This is an easy fix, but did break our CI unexpectedly this morning

That's a good callout, @rough-rose-81585. If you see the underlying issue,

storage

was not supported, so we removed it to decrease the confusion. I'm going to amend the release notes to emphasize this.

Good to know thanks! Guess we never checked to see if we were actually being given correct storage amount in k8s

Ohh sorry about that