Hi. What was the reason we put an upper bound for fsspec https://github.com/flyteorg/flytekit/commit/2a5fa355fdd790f525731b3634a96579e9f744e1#r136117081 ? This setting is now conflicting with other dependencies we have.

I tried to remove that, but some tests are failing

I tried https://github.com/flyteorg/flytekit/pull/2087

I think someone was working on fixing this: https://github.com/flyteorg/flytekit/pull/1925

oh, nice, thank you, will take a look

Does this make sense to have regardless https://github.com/flyteorg/flytekit/pull/2087 ?

+1, we could remove upper bound later in another PR.

Looks like that MR was closed due to windows issues(?) 😕 It would be nice to to be able to use newer aiobotocore/botocore than what s3fs 2023.9.2 allows.

If there is nothing else preventing us from going beyond the current upper bound, we can for sure remove it. One thing to note is that, pip-compiles legacy resolver has been having hard time resolving a correct match of the fsspec packages family, so internally we always take extra effort pining fsspec packages family to have better backward compatibility. I hope the legacy resolve is not used much anymore as it is going out.