@ancient-wolf-19325 can you debug, in flyte logs but the task completes successfully

/opt/conda/lib/python3.11/site-packages/fsspec/asyn.py:76 in sync            │
│                                                                              │
│ ❱   76 │   │   raise RuntimeError("Loop is not running") 
RuntimeError: Loop is not running

The error

RuntimeError: Loop is not running

from

fsspec.asyn.py

typically occurs when asynchronous file operations are attempted without an active event loop. However, if your Flyte task completes successfully despite this log, it means the error is likely being caught and handled internally, or it occurs in a non-critical code path. This warning can often be ignored if outputs are correct, but it may indicate a misconfiguration or a library version mismatch, especially with libraries like fsspec, s3fs, or gcsfs. According to Flyte GitHub Issue #5375, such errors have been observed when incompatible versions of fsspec and related libraries are installed. Would you like more detail on how to resolve or suppress this warning, or guidance on ensuring your environment is correctly configured? Sources: - Flyte GitHub Issue #5375 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.