New RunLLM response generated: >>>*# Question* I ...
# runllm-flyte-trial
j
New RunLLM response generated: >>>*# Question* I have two question about flyte copilot. • Is my understanding correct that when using copilot, task inputs and outputs are not downloaded/uploaded using
fsspec
in python at all? • How much of a “first-class-citizen” is copilot? The “raw notes” in its readme sound a bit like its WIP. Thank you 🙏 # Answer It seems likely that when using Flyte Copilot, task inputs and outputs are managed by the copilot itself rather than being directly handled by
fsspec
in Python. Flyte Copilot operates in two modes: as a downloader and as a sidecar, managing data transfer and monitoring the main container's execution, as described in the Flyte Copilot README. Regarding the status of Flyte Copilot as a "first-class citizen," the raw notes in the README suggest that it might still be evolving, with some solutions being proposed and discussed. This could imply that while it is functional, there may be ongoing improvements and refinements. Would you like more detail on any specific aspect? Sources: - Flyte Copilot README Slack Link https://flyte.slack.com/archives/CP2HDHKE1/p1732290693.373909 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.