Skip to content
This repository has been archived by the owner on Mar 21, 2024. It is now read-only.

Create Environment "Locking" POC #726

Closed
peterhessey opened this issue May 19, 2022 · 0 comments · Fixed by #735
Closed

Create Environment "Locking" POC #726

peterhessey opened this issue May 19, 2022 · 0 comments · Fixed by #735
Assignees
@peterhessey
Labels
improvements Improve performance of InnerEye

Comments

@peterhessey
Copy link
Contributor

peterhessey commented May 19, 2022 •
edited
Loading

Currently, environments in all of InnerEye and hi-ml do not use environment locking. This means that if a new environment is built (or rebuilt), then secondary dependencies can change and result in inconsistent and even breaking behaviour between 2 deployments of the same code. Locking use poetry and conda-lock isn't an option, as AzureML can only consume files in the format of a conda environment.yml.
@peterhessey peterhessey self-assigned this May 19, 2022
@peterhessey peterhessey added the improvements Improve performance of InnerEye label May 19, 2022
@peterhessey peterhessey mentioned this issue May 30, 2022
Merged
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@peterhessey peterhessey

Labels
improvements Improve performance of InnerEye
Projects
InnerEye-OSS
Status: Done
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

ENH: Add Environment Locking microsoft/InnerEye-DeepLearning
1 participant
@peterhessey