I believe I am running into <this issue>. I have t...
# ask-metaflow
f
I believe I am running into this issue. I have to import metaflow in step with an
@conda
decorator. I think this means I can't access the fix until a new version is released. is that correct?
1
hmmm, i guess i could try updating the affected files in S3...
actually it seemed to have been sufficient to have the latest installed from git in my local env and then specify that version in the
@conda
decorator.
after i cleared cached envs both locally and on S3, actually.
a
Yes, we are going to ship this fix asap
b
shipping out a release this morning, should be out soon.
@fast-honey-9693 2.9.9 is out now which should fix this issue as you noted already. Out of interest, which S3 provider are you using? From my testing, the issue seemed to only affects users with S3 providers that do not implement the encryption headers, f.ex. MinIO. Making sure that my testing is not flawed 🙂
f
thank you so much for the fix! we're using aws s3 and the default encryption but don't have a bucket key specified