Savin

@cndota123 this can happen if you are relying on the RC version of micromamba. To get around this issue, please nuke - `~/.metaflowconfig/micromamba/`, upgrade Metaflow to the latest version and...

@bryant1410 thanks for the PR! Is there any before/after analysis for this change?

> > @bryant1410 thanks for the PR! Is there any before/after analysis for this change? > > What do you mean? I am curious to see what is observed change...

Yeah, at the moment, exclusive CPU ownership doesn't happen by default on Kubernetes (I am not sure if it's even an option with AWS Batch—maybe @npow knows), so os.sched_getaffinity and...

@hasush the s3.xx_many calls are already parallelized behind the scenes so one shouldn't necessarily need parallel_map. regardless, the error that you highlighted looks like a bug that we will address.

@anozdryn-platnitski why isn't executing `python flow.py argo-workflows create` from CI an option?

> As mentioned in the opening issue here, resources become orphaned once flow.py changes; repeating myself here but, removing a cron schedule will not remove said cron schedule by running...

As a more explicit example - 1. deploying [this](https://docs.metaflow.org/production/scheduling-metaflow-flows/scheduling-with-argo-workflows#time-based-triggering) flow will generate a cron workflow 2. commenting out the `@schedule` decorator and deploying again will remove the cron workflow from...

thanks for highlighting. we have plans to refactor our tracing implementation. i should have updates shortly